Intermediate Level Modeler
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings but likely they want those headings. But we must map content to those headings. The posting includes many sections: About Us, Who We Are, What We Do, Job Description Summary, Responsibilities, Qualifications, Preferred Qualifications, Working Conditions, Compensation, What We Offer, Inclusion & Diversity, Giving Back, Parent Company. However the instruction says to prefer a few substantive sections over many thin ones. So we may combine some.
We need to include sections only when posting has real, specific content. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does have Compensation (salary range) and Benefits (What We Offer). So we can have Pay section for compensation, Benefits section for benefits. Schedule? There's Working Conditions includes hybrid schedule (Tuesday, Wednesday, Thursday). That's schedule info. So we can include Schedule section.
We need to use for section headings. So we could have:
About the role
(maybe combine About Us, Who We Are, What We Do, Job Description Summary). But "About the role" is generic; we can put the job description summary and maybe overview.
Better: Use headings: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule, Inclusion & Diversity (maybe as Skills? but not required). However instruction says we can use those examples but not limited. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can also add other headings like "Working Conditions" but maybe better to map to Schedule.
We must not repeat job title as heading. So no heading for job title.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: legal statements, immigration sponsorship, accommodation request, etc. Also remove duplicated lines.
We need to preserve all substantive information: job description summary, responsibilities, qualifications, preferred qualifications, working conditions (hybrid schedule, locations), compensation (salary range), benefits (list), inclusion & diversity info, giving back, parent company info maybe? But we may combine some.
We need to decide what to keep. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info. That's a lot. But we can keep it within sections, not summarizing.
We must not create sections with filler like "commensurate with experience". We have salary range specific.
We must not include application instructions (like "Applicants must possess legal authorization...") Actually that is substantive? It's about eligibility. Might be considered boilerplate? It's a requirement for applicants. Might be considered part of Qualifications? Could be included under Qualifications as a requirement. But it's about immigration sponsorship. Might be considered legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line about legal authorization is somewhat legal but also a requirement. Might be considered boilerplate? Not sure. Safer to keep it as part of Qualifications? But it's about work authorization. Could be considered a requirement. I'd keep it under Qualifications.
We also need to remove duplicated lines. There may be duplicates like "Transamerica employs nearly 7,000 people." appears maybe once. Not duplicate.
We need to output only HTML fragment.
Let's structure:
About the role
for section headings. So we could have:
About the role
(maybe combine About Us, Who We Are, What We Do, Job Description Summary). But "About the role" is generic; we can put the job description summary and maybe overview.
Better: Use headings: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule, Inclusion & Diversity (maybe as Skills? but not required). However instruction says we can use those examples but not limited. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can also add other headings like "Working Conditions" but maybe better to map to Schedule.
We must not repeat job title as heading. So no heading for job title.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: legal statements, immigration sponsorship, accommodation request, etc. Also remove duplicated lines.
We need to preserve all substantive information: job description summary, responsibilities, qualifications, preferred qualifications, working conditions (hybrid schedule, locations), compensation (salary range), benefits (list), inclusion & diversity info, giving back, parent company info maybe? But we may combine some.
We need to decide what to keep. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all substantive info. That's a lot. But we can keep it within sections, not summarizing.
We must not create sections with filler like "commensurate with experience". We have salary range specific.
We must not include application instructions (like "Applicants must possess legal authorization...") Actually that is substantive? It's about eligibility. Might be considered boilerplate? It's a requirement for applicants. Might be considered part of Qualifications? Could be included under Qualifications as a requirement. But it's about immigration sponsorship. Might be considered legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line about legal authorization is somewhat legal but also a requirement. Might be considered boilerplate? Not sure. Safer to keep it as part of Qualifications? But it's about work authorization. Could be considered a requirement. I'd keep it under Qualifications.
We also need to remove duplicated lines. There may be duplicates like "Transamerica employs nearly 7,000 people." appears maybe once. Not duplicate.
We need to output only HTML fragment.
Let's structure:
About the role
About the role
Job Description Summary: Build and analyze sophisticated models for insurance products, investments and/or portfolios to increase company risk adjusted returns. Leverage advanced knowledge of actuarial, financial, statistical, data science and/or balance sheet modeling analytics to develop, test and validate models for various functions within the company.
Maybe also include About Us, Who We Are, What We Do as part of About the role? Could be separate sections but we want few sections. Could combine them into About the role paragraph. But we must preserve all substantive info; combining is okay as long as we don't lose detail. We'll include all that info in the paragraph. Then Responsibilities:Responsibilities
- ... each responsibility.
Qualifications
- ... each.
Preferred Qualifications
list. Preferred Qualifications block: "Advanced degreeInsurance or asset/derivatives modeling experienceActuarial Science backgroundExperience with database design and usageProgramming experience in C++/C#/Python or other advanced languageMoSes/AXIS/ALFA or other actuarial softwareQRM or similar asset liability software experienceSAS, R, SPSS or other statistical software experience" Split items: - Advanced degree - Insurance or asset/derivatives modeling experience - Actuarial Science background - Experience with database design and usage - Programming experience in C++/C#/Python or other advanced language - MoSes/AXIS/ALFA or other actuarial software - QRM or similar asset liability software experience - SAS, R, SPSS or other statistical software experience Working Conditions: we have "Office EnvironmentHybrid office environment (Tuesday, Wednesday, Thursday)Locations: Denver, Cedar Rapids, Baltimore". Also maybe other details. We'll create Schedule section for hybrid days and location maybe as part of Working Conditions. But instruction says use Schedule heading if posting actually states them. It does state hybrid office environment (Tuesday, Wednesday, Thursday). So we can have Schedule section. We also have Locations: Denver, Cedar Rapids, Baltimore. Could be part of Schedule or maybe a separate section "Location". Not in examples but we could add as a paragraph under Schedule or separate heading "Location". Since we want few sections, we can include location in Schedule paragraph. Thus Schedule:Schedule
Hybrid office environment (required in‑office Tuesday, Wednesday, Thursday). Locations: Denver, Cedar Rapids, Baltimore.
Compensation:Pay
The salary for this position generally ranges between $88,000‑$105,000 annually. (Note: original text had a typo "$88,000-105,00n". We'll correct to $88,000‑$105,000.) Actual starting pay is determined by qualifications, experience, geography, work location designation (in‑office, hybrid, remote) and operational needs. Salary may vary above and below the stated amounts as permitted by applicable law.
We must preserve all substantive info; we corrected typo but that's not inventing; we just fix obvious typo. Probably okay. Benefits:Benefits
- ... list.