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 (the page already shows it) and 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. We need to decide which sections to include based on content. We have: - Who We Are (company description) – maybe not needed? It's not a required heading; but we could include as a short paragraph maybe under "About the company"? Not listed as allowed heading but we could still include as

  without heading? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Probably we should stick to those headings where applicable. The "Who We Are" could be considered "About the company" but not required. Could embed as a

  before sections. - Who You'll Work With: description of team – could be part of About the role? Might be included as a paragraph. - About The Role: description of duties list (1)-(5). That's substantive. - Responsibilities: list of responsibilities bullet points. - Skills & Qualifications: list. - Compensation: salary range, bonus, benefits mention. - Location: location info, travel minimal. - Why Corebridge? Benefits description. We need to avoid boilerplate like EEO etc. Remove that. We need to include Pay section only if posting actually states them. It does: salary range $85,000 to $95,000, discretionary bonus, benefits. So we can have Pay section. Benefits section: we have benefits description under "Why Corebridge?" and also mention benefits in compensation. So we can have Benefits section. Schedule: not mentioned; travel minimal but not schedule. So we should not create Schedule section. Requirements/Qualifications: we have Skills & Qualifications; could combine as Qualifications. But we have separate Skills & Qualifications heading. We could output a Skills section (or Qualifications). The instruction list includes Skills, Qualifications. We can choose one. Probably combine into Skills & Qualifications as one section heading

  Skills & Qualifications

  . Or we could have two sections: Skills and Qualifications. But they said prefer a few substantive sections over many thin ones. So combine. Thus sections: About the role (maybe include who you'll work with), Responsibilities, Skills & Qualifications, Pay, Benefits, Location (maybe not a standard heading but we could include as

  without heading? Not in list. Could treat as part of About the role? But location is substantive. Could add a

  Location

  though not in the list but maybe allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Safer to stick to those examples. Location not in list; maybe we can incorporate location into About the role or Responsibilities? Probably better to add a

  after sections without heading. But they said use

  for section headings (e.g ...). It doesn't forbid other headings but suggests using those for those sections. I'd include Location as a

  paragraph. We need to preserve all substantive information. So we need to include details: Who We Are description, Who You'll Work With description, About The Role duties (1)-(5), Responsibilities bullet points, Skills & Qualifications bullet points, Compensation details (salary range, bonus, benefits mention), Benefits details (health, wellness, retirement, EAP, matching donations, volunteer time off, PTO), Location details (Jersey City, NJ; Wilmington, DE; Houston, TX; remote considered; minimal travel). Also maybe note Functional Area UW - Underwriting, Estimated Travel Percentage (%): Up to 25%, Relocation Provided: No, American General Life Insurance Company. Those are metadata; we can fold into a short

  or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph for metadata like "Functional Area: UW - Underwriting; Estimated Travel: Up to 25%; Relocation: Not provided; Employer: American General Life Insurance Company." That's minor metadata. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  Who We Are: At Corebridge Financial, we believe action is everything...

  Maybe combine Who We Are and Who You'll Work With into an intro. But we need to preserve all substantive information; we can't lose details. So we need to include the Who We Are paragraph exactly (or paraphrased? Must preserve all substantive information; we can't invent or summarize away detail. We can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details, but we can rephrase? Safer to copy the text verbatim (or close) as a paragraph. However, we need to avoid boilerplate; the Who We Are is not boilerplate. So we can include it as a

  . Similarly Who You'll Work With paragraph. Then About The Role heading

  About the role

  then paragraph describing the role and then maybe a
  • list of duties (1)-(5). The posting says: "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 need to preserve that exactly. We'll put each duty as
  • . Then Responsibilities heading

    Responsibilities

    then a
    • list of responsibilities bullet points from the "Responsibilities" section. Let's extract those bullet points: - 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 each as
    • . Then Skills & Qualifications heading

      Skills & Qualifications

      then list. Extract bullet points: - 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 put each as
    • . Then Pay heading

      Pay

      then paragraph with compensation details. Compensation text: "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. Corebridge also offers a range of competitive benefits as part of the total compensation package, as detailed below." We need to preserve that. Note there is a space in "$95, 000" (typo). We'll keep as is. Then Benefits heading

      Benefits

      then list of benefits from "Why Corebridge?" and also maybe the earlier mention of benefits. We'll include the bullet points: - Health and Wellness: We offer a range of medical, dental and vision insurance plans, as well as mental health support and wellness initiatives to promote overall well-being. - Retirement Savings: We offer retirement benefits options, which vary by location. In the U.S., our 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 are available to all employees. - 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 to support activities that enhance and serve communities where employees live and work. - Paid Time Off: Eligible employees start off with at least 24 Paid Time Off (PTO) days so they can take time off for themselves and their families when they need it. We'll put each as
    • . Then Location heading? Not in list but we could add

      Location

      but maybe better to incorporate as a

      after Benefits. However location is substantive; we should include it. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for those sections. I'd add Location as