Pension (Risk Transfer) Actuary, Administrator, Paralegal

We need to output HTML fragment with sections: About the role, Responsibilities, Skills & Qualifications (maybe Skills), Compensation (Pay), Benefits, Location? The rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content. Let's parse the posting: - Who We Are: description of Corebridge Financial. Might be considered "About the company" but not required. Could be omitted? The instruction: include a section ONLY when posting has real, specific content for it. The "Who We Are" is generic but maybe we can include as a paragraph? However they said prefer a few substantive sections over many thin ones. Could include "About the company" but not listed as allowed heading. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. We have: About The Role: paragraph describing need for actuarial or defined benefit pension plan expertise, duties list (1)-(5). That's substantive. Responsibilities: list of responsibilities (bulleted). Good. Skills & Qualifications: list of qualifications. Compensation: salary range, bonus, benefits mention. Benefits: list of benefit offerings. Location: location info and travel. Schedule? Not mentioned. We should not include sections like Requirements separate if covered in Skills & Qualifications. Could combine. We need to output HTML with

  headings and appropriate

  or

  • . We must not repeat job title. Not needed. We must not include boilerplate like EEO etc. Remove. We must preserve all substantive information. Let's extract each piece. **About The Role** text: "As our business continues to grow, the US pension underwriting team is looking to hire a professional with actuarial or defined benefit pension plan expertise. Depending on the candidate’s background, the successful candidate will perform one or multiple of the following duties: (1) underwrite, assess pension risks, perform actuarial calculations, and assemble commitment agreements in technical aspects; (2) act as internal project manager in all technical aspects of onboarding new business across internal functions; (3) act as pension specialist to support call center through managing defined benefit pension plan’s benefit calculations, modeling, and testing; (4) act as pension specialist in drafting and reviewing defined benefit pension provisions in contracts from the actuarial modeling and pension administration perspectives before documents are utilized by call center, are delivered to individuals or are filed with state regulators; and/or (5) lead inforce governance and special projects assisting internal functions." We'll put that in

    maybe with

    • for duties? The duties are enumerated; we could make a list. The rule: Use
      • for any list of duties/requirements/benefits. So we should convert duties to list. Thus About the role: maybe a brief intro paragraph then list. **Responsibilities** list: - Explain technical actuarial and/or pension topics to Head of US PRT in New Jersey - Be viewed as the defined benefit pension plan expert within the company - Assess pension risks, calculate premiums, and customized contract terms affecting premiums or operations - Guide onboarding and lead cross function collaboration - Design or implement governance, controls, process, and procedures - Review actuarial calculations and actuarial methodology in a controlled environment - Execute actuarial model risk management framework including model development and testing - Apply technical expertise to support Operations and Valuation teams and ensure successful implementation of new business leading to accurate and reliable financial reporting - Think creatively and exercise sound judgment in leading projects We'll put as
        • . **Skills & Qualifications** list: - Defined benefit pension plan experience - Ability to interpret and implement complex pension plan benefit provisions as well as drafting of documents - At least one of Pricing, Valuation, Actuarial Modeling, Pension Administration or Contract experience - Pension benefit calculation modeling, testing, or production experience - Project management experience - Self-Starter who is comfortable dealing with both complexity and ambiguity, with ability to explore multiple solutions to a problem - Awareness of governance best practice and controls required - Competence in using Microsoft Office programs; familiarity with Copilot and VBA coding a plus - Ability to work and thrive in a dynamic team environment, possess excellent interpersonal, written and oral communication skills and having a comfort with explaining complex materials in a clear, focused, and concise manner - Bachelors degree in Actuarial Science, Mathematics, Statistics, or related field - Pursue or obtained one of the Society of Actuaries, the Enrolled Actuaries, or the American Society of Pension Professionals & Actuaries certification We'll list. **Compensation** (Pay) section: "The anticipated salary range for this position is $85,000 to $95, 000 at the commencement of employment. Not all candidates will be eligible for the upper end of the salary range. The actual compensation offered will ultimately be dependent on multiple factors, which may include the candidate’s geographic location, skills, experience and other qualifications. In addition, the position is eligible for a discretionary bonus in accordance with the terms of the applicable incentive plan." We should note the typo "$95, 000" but preserve as is. We could also mention benefits but they have separate Benefits section. **Benefits** section: List: - Health and Wellness: medical, dental and vision insurance plans, mental health support and wellness initiatives. - Retirement Savings: competitive 401(k) Plan offers a generous dollar-for-dollar Company matching contribution of up to 6% of eligible pay and a Company contribution equal to 3% of eligible pay (subject to annual IRS limits and Plan terms). These Company contributions vest immediately. - Employee Assistance Program: Confidential counseling services and resources. - Matching charitable donations: Corebridge matches donations to tax-exempt organizations 1:1, up to $5,000. - Volunteer Time Off: Employees may use up to 16 volunteer hours annually. - Paid Time Off: Eligible employees start off with at least 24 Paid Time Off (PTO) days. We'll put as list. **Location** section: Not an allowed heading but we could incorporate into a short paragraph maybe under "About the role"? But we have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location not listed. However we could treat location as part of "About the role" or maybe we can omit? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It didn't say we cannot add other headings; it gave examples of section headings. It says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should not create a Location heading. We could incorporate location info into a paragraph under About the role or maybe under Responsibilities? Probably better to add a brief paragraph after About the role but without a heading? The instruction says output only HTML fragment; we can include

          for prose anywhere. So we can add a

          with location details without a heading. That seems acceptable. Similarly, "Estimated Travel Minimal travel." and "Estimated Travel Percentage (%): Up to 25%" maybe we can include in same paragraph. We should not include "Functional Area UW - Underwriting" etc. That's metadata; we can drop. We should not include "Relocation Provided: No". Could drop. We should not include "American General Life Insurance Company". That's maybe boilerplate; drop. We should not include EEO etc. Now produce HTML. Structure:

          About the role

          As our business continues to grow, the US pension underwriting team is looking to hire a professional with actuarial or defined benefit pension plan expertise. Depending on the candidate’s background, the successful candidate will perform one or multiple of the following duties:

          • underwrite, assess pension risks, perform actuarial calculations, and assemble commitment agreements in technical aspects
          • act as internal project manager in all technical aspects of onboarding new business across internal functions
          • act as pension specialist to support call center through managing defined benefit pension plan’s benefit calculations, modeling, and testing
          • act as pension specialist in drafting and reviewing defined benefit pension provisions in contracts from the actuarial modeling and pension administration perspectives before documents are utilized by call center, are delivered to individuals or are filed with state regulators
          • lead inforce governance and special projects assisting internal functions
          Then maybe a paragraph for location/travel:

          This position is primarily located in Jersey City, NJ and Wilmington, DE, Houston, TX, or other remote locations will also be considered. Estimated travel is minimal (up to 25%).

          Then Responsibilities:

          Responsibilities

          ...
          Then Skills & Qualifications: maybe combine as Skills? The allowed headings include Skills and Qualifications separate. We could do Skills and Qualifications as one heading? The rule: use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have both Skills and Qualifications headings. But we have content that mixes both. Could split: Skills heading for skill-based items, Qualifications heading for education/certification. But we prefer few substantive sections over many thin ones. So maybe combine into one heading "Skills & Qualifications". That's not exactly in the list but close; they gave Skills as example. Could we use "Skills" heading and include qualifications within? Might be okay. But they said "e.g." not exhaustive. However to be safe, we could use "Skills" heading and put all skill/qualification items there. Or we could use two headings: Skills and Qualifications. That would be thin but still substantive. The instruction: Prefer a few substantive sections over many thin ones. So better to combine. Thus:

          Skills & Qualifications

          ...
          Then Pay:

          Pay

          The anticipated salary range for this position is $85,000 to $95, 000 at the commencement of employment. Not all candidates will be eligible for the upper end of the salary range. The actual compensation offered will ultimately be dependent on multiple factors, which may include the candidate’s geographic location, skills, experience and other qualifications. In addition, the position is eligible for a discretionary bonus in accordance with the terms of the applicable incentive plan.

          Then Benefits:

          Benefits

          ...
          We should not include Schedule as not present. Check for any duplicated lines: we removed boilerplate. Make sure we preserve all substantive information: we captured duties, responsibilities, skills/qualifications, compensation, benefits, location/travel. We omitted "Who We Are