Senior Analyst, Portfolio Analytics and Planning
CLM Dallas Chapter · Columbus, OH · 4 wk ago
FinanceFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
Let's parse the posting.
Position Company: Liberty Mutual Insurance
Location: Columbus, Ohio
Posted On: 9/22/2026
Description: "Join the Personal Lines AutoProgram Delivery & Enhancements (PDE)Build team our brand-new, high-visibility team shaping next-generation auto rating programs and the core frameworks PDE relies on to deliver efficiently and with precision. In this role, you'llsupport portfolio planning and operational analyticsacross the delivery value stream. You'll bring analytical rigor to rollout scheduling, capacity forecasting, and performance metrics building the tools, schedules, and views that help the team sequence work, balance capacity, make informed trade-offs, and optimize in market value for the organization. You'll help turn a complex, multi-state, multi-program landscape into a clear, visible, data-driven plan. You'll partner with State Management, etc."
Then "What You'll Do" bullet list.
Then "Skills and experience that will lead to success in the role" bullet list.
Then "What You'll Gain" bullet list.
Then "Qualifications" bullet list.
Then "About Us Pay Philosophy:" paragraph.
Then benefits mention: "We value your hard work... benefits that support your life and well-being. To learn more about our benefit offerings please visit: https://www.libertymutualgroup.com/about-lm/careers/benefits"
Then equal opportunity etc.
We need sections: About the role (maybe description), Responsibilities (What You'll Do), Requirements (maybe Skills and experience that will lead to success?), Qualifications (Qualifications), Skills (maybe separate?), Benefits (maybe mention benefits link), Pay (Pay Philosophy), Schedule (maybe mention in-office requirements? The posting says: "This position may have in-office requirements depending on candidate location." That's schedule info. Also "The level of position offered will be based on skills and experience at manager discretion." Not schedule.
We must not create sections with filler like "commensurate with experience". We have actual content for Pay Philosophy (salary range description). So we can include Pay section with that paragraph.
Schedule: we have "This position may have in-office requirements depending on candidate location." That's schedule info. So we can include Schedule section with that sentence.
Benefits: we have mention of benefits and link. So we can include Benefits section with that sentence.
Now we need to decide which sections to include: About the role (description paragraph), Responsibilities (What You'll Do), Requirements (maybe Skills and experience that will lead to success?), Qualifications (Qualifications), Skills (maybe separate? but we already have Skills and experience that will lead to success; could be Skills). However we have also a separate "Skills and experience that will lead to success in the role" which is essentially skills. Could map to Skills section. Requirements could be Qualifications? Actually Qualifications section often includes education, experience, etc. The posting has Qualifications bullet list. So we can put that under Qualifications.
We also have "What You'll Gain" which could be considered Benefits? But we already have Benefits. Could also be "What You'll Gain" as a separate section like "What You'll Gain" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those.
Thus:
- About the role: description paragraph (the initial description).
- Responsibilities: "What You'll Do" bullet list.
- Requirements: maybe "Skills and experience that will lead to success in the role" (these are requirements). Or we could put that under Skills. But we need both Skills and Requirements sections. Let's assign:
- Requirements: the bullet list under "Skills and experience that will lead to success in the role" (these are required skills/experience).
- Skills: maybe we could extract a separate list of skills? But we don't have separate distinct skills list besides that. Could we split? The posting also has "Experience in analytics, portfolio/program planning, forecasting, operations, or a related area" etc. That's basically skills. Could we put that under Skills and leave Requirements empty? But we must not create empty sections. So we need to decide which to include.
We have Qualifications (education, experience, etc). We have Skills and experience that will lead to success (maybe that's Skills). We have Requirements maybe could be "What You'll Do"? No that's responsibilities.
Better mapping:
- About the role: description.
- Responsibilities: What You'll Do.
- Requirements: Qualifications (education, experience, etc). But Qualifications is also a heading. Hmm.
We have both Requirements and Qualifications headings allowed. We could put:
- Requirements: the bullet list under "Skills and experience that will lead to success in the role" (these are required skills/experience).
- Qualifications: the bullet list under "Qualifications" (education, experience, etc).
- Skills: maybe we could extract a separate list of technical tools? But not needed; we could omit Skills section if no distinct content. However we have "Experience with data, reporting, and app-building tools (e.g., Power BI, Power Apps, Excel)" etc. That's part of skills. Could we put that under Skills? But we already used that content in Requirements. Could split: Requirements could be the soft skills/experience (analytical, quantitative, etc) and Skills could be the tools. But we need to avoid duplication and ensure we preserve all info.
Let's examine the "Skills and experience that will lead to success in the role" bullet list:
- Experience in analytics, portfolio/program planning, forecasting, operations, or a related area
- Strong analytical and quantitative skills comfortable building custom logic, forecasts, and performance metrics from data
- Experience with data, reporting, and app-building tools (e.g., Power BI, Power Apps, Excel)
- Curiosity about how to apply AI and automation to streamline planning and reporting
- Detail oriented and a strong steward of quality outcomes
- Strong organizational skills, with the ability to turn ambiguity into structure
- Clear written and verbal communication able to translate complex data and plans into concise recommendations
- Comfort working across multiple teams and managing several priorities at once
These are a mix of experience, skills, abilities.
Qualifications bullet list:
- Bachelor's degree in Mathematics, Statistics, Finance, Economics or Insurance preferred; or equivalent experience
- Approx 5 or more years related work experience
- Knowledge of insurance principles and concepts required
- Advanced analytical/problem solving and research skills
- Effective communication skills for writing reports/proposals and making presentations
- Ability to work independently and lead others during projects
- Knowledge of the business practices and processes
- Proficiency with spreadsheets and data base software
There's overlap.
We could assign:
- Requirements: the "Skills and experience that will lead to success in the role" (these are required skills/experience).
- Qualifications: the "Qualifications" bullet list (education, experience, etc).
- Skills: maybe we could omit because it's covered. But we need to decide if we should include Skills section with some content not already covered. Could we extract a subset like "Experience with data, reporting, and app-building tools (e.g., Power BI, Power Apps, Excel)" and "Curiosity about how to apply AI and automation" etc as Skills? But that would duplicate.
Given the instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So maybe we include only About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Omit Skills as it's covered.
Thus sections:
- About the role: description paragraph.
- Responsibilities: What You'll Do bullet list.
- Requirements: Skills and experience that will lead to success bullet list.
- Qualifications: Qualifications bullet list.
- Benefits: benefits paragraph (including link).
- Pay: Pay Philosophy paragraph.
- Schedule: in-office requirements sentence.
We must not include boilerplate like equal opportunity, etc.
Now we need to format: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
Let's parse the posting.
Position Company: Liberty Mutual Insurance
Location: Columbus, Ohio
Posted On: 9/22/2026
Description: "Join the Personal Lines AutoProgram Delivery & Enhancements (PDE)Build team our brand-new, high-visibility team shaping next-generation auto rating programs and the core frameworks PDE relies on to deliver efficiently and with precision. In this role, you'llsupport portfolio planning and operational analyticsacross the delivery value stream. You'll bring analytical rigor to rollout scheduling, capacity forecasting, and performance metrics building the tools, schedules, and views that help the team sequence work, balance capacity, make informed trade-offs, and optimize in market value for the organization. You'll help turn a complex, multi-state, multi-program landscape into a clear, visible, data-driven plan. You'll partner with State Management, etc."
Then "What You'll Do" bullet list.
Then "Skills and experience that will lead to success in the role" bullet list.
Then "What You'll Gain" bullet list.
Then "Qualifications" bullet list.
Then "About Us Pay Philosophy:" paragraph.
Then benefits mention: "We value your hard work... benefits that support your life and well-being. To learn more about our benefit offerings please visit: https://www.libertymutualgroup.com/about-lm/careers/benefits"
Then equal opportunity etc.
We need sections: About the role (maybe description), Responsibilities (What You'll Do), Requirements (maybe Skills and experience that will lead to success?), Qualifications (Qualifications), Skills (maybe separate?), Benefits (maybe mention benefits link), Pay (Pay Philosophy), Schedule (maybe mention in-office requirements? The posting says: "This position may have in-office requirements depending on candidate location." That's schedule info. Also "The level of position offered will be based on skills and experience at manager discretion." Not schedule.
We must not create sections with filler like "commensurate with experience". We have actual content for Pay Philosophy (salary range description). So we can include Pay section with that paragraph.
Schedule: we have "This position may have in-office requirements depending on candidate location." That's schedule info. So we can include Schedule section with that sentence.
Benefits: we have mention of benefits and link. So we can include Benefits section with that sentence.
Now we need to decide which sections to include: About the role (description paragraph), Responsibilities (What You'll Do), Requirements (maybe Skills and experience that will lead to success?), Qualifications (Qualifications), Skills (maybe separate? but we already have Skills and experience that will lead to success; could be Skills). However we have also a separate "Skills and experience that will lead to success in the role" which is essentially skills. Could map to Skills section. Requirements could be Qualifications? Actually Qualifications section often includes education, experience, etc. The posting has Qualifications bullet list. So we can put that under Qualifications.
We also have "What You'll Gain" which could be considered Benefits? But we already have Benefits. Could also be "What You'll Gain" as a separate section like "What You'll Gain" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those.
Thus:
- About the role: description paragraph (the initial description).
- Responsibilities: "What You'll Do" bullet list.
- Requirements: maybe "Skills and experience that will lead to success in the role" (these are requirements). Or we could put that under Skills. But we need both Skills and Requirements sections. Let's assign:
- Requirements: the bullet list under "Skills and experience that will lead to success in the role" (these are required skills/experience).
- Skills: maybe we could extract a separate list of skills? But we don't have separate distinct skills list besides that. Could we split? The posting also has "Experience in analytics, portfolio/program planning, forecasting, operations, or a related area" etc. That's basically skills. Could we put that under Skills and leave Requirements empty? But we must not create empty sections. So we need to decide which to include.
We have Qualifications (education, experience, etc). We have Skills and experience that will lead to success (maybe that's Skills). We have Requirements maybe could be "What You'll Do"? No that's responsibilities.
Better mapping:
- About the role: description.
- Responsibilities: What You'll Do.
- Requirements: Qualifications (education, experience, etc). But Qualifications is also a heading. Hmm.
We have both Requirements and Qualifications headings allowed. We could put:
- Requirements: the bullet list under "Skills and experience that will lead to success in the role" (these are required skills/experience).
- Qualifications: the bullet list under "Qualifications" (education, experience, etc).
- Skills: maybe we could extract a separate list of technical tools? But not needed; we could omit Skills section if no distinct content. However we have "Experience with data, reporting, and app-building tools (e.g., Power BI, Power Apps, Excel)" etc. That's part of skills. Could we put that under Skills? But we already used that content in Requirements. Could split: Requirements could be the soft skills/experience (analytical, quantitative, etc) and Skills could be the tools. But we need to avoid duplication and ensure we preserve all info.
Let's examine the "Skills and experience that will lead to success in the role" bullet list:
- Experience in analytics, portfolio/program planning, forecasting, operations, or a related area
- Strong analytical and quantitative skills comfortable building custom logic, forecasts, and performance metrics from data
- Experience with data, reporting, and app-building tools (e.g., Power BI, Power Apps, Excel)
- Curiosity about how to apply AI and automation to streamline planning and reporting
- Detail oriented and a strong steward of quality outcomes
- Strong organizational skills, with the ability to turn ambiguity into structure
- Clear written and verbal communication able to translate complex data and plans into concise recommendations
- Comfort working across multiple teams and managing several priorities at once
These are a mix of experience, skills, abilities.
Qualifications bullet list:
- Bachelor's degree in Mathematics, Statistics, Finance, Economics or Insurance preferred; or equivalent experience
- Approx 5 or more years related work experience
- Knowledge of insurance principles and concepts required
- Advanced analytical/problem solving and research skills
- Effective communication skills for writing reports/proposals and making presentations
- Ability to work independently and lead others during projects
- Knowledge of the business practices and processes
- Proficiency with spreadsheets and data base software
There's overlap.
We could assign:
- Requirements: the "Skills and experience that will lead to success in the role" (these are required skills/experience).
- Qualifications: the "Qualifications" bullet list (education, experience, etc).
- Skills: maybe we could omit because it's covered. But we need to decide if we should include Skills section with some content not already covered. Could we extract a subset like "Experience with data, reporting, and app-building tools (e.g., Power BI, Power Apps, Excel)" and "Curiosity about how to apply AI and automation" etc as Skills? But that would duplicate.
Given the instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So maybe we include only About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Omit Skills as it's covered.
Thus sections:
- About the role: description paragraph.
- Responsibilities: What You'll Do bullet list.
- Requirements: Skills and experience that will lead to success bullet list.
- Qualifications: Qualifications bullet list.
- Benefits: benefits paragraph (including link).
- Pay: Pay Philosophy paragraph.
- Schedule: in-office requirements sentence.
We must not include boilerplate like equal opportunity, etc.
Now we need to format: Use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
Thus each section:
Section Name
then either ... or
- ...
.
We must preserve all substantive information. Ensure we don't lose any detail.
Let's extract the description paragraph exactly as given, but we need to clean up formatting.
Original description:
"Join the Personal Lines AutoProgram Delivery & Enhancements (PDE)Build team our brand-new, high-visibility team shaping next-generation auto rating programs and the core frameworks PDE relies on to deliver efficiently and with precision. In this role, you'llsupport portfolio planning and operational analyticsacross the delivery value stream. You'll bring analytical rigor to rollout scheduling, capacity forecasting, and performance metrics building the tools, schedules, and views that help the team sequence work, balance capacity, make informed trade-offs, and optimize in market value for the organization. You'll help turn a complex, multi-state, multi-program landscape into a clear, visible, data-driven plan. You'll partner with State Management, Program Management, Data Science, Tech, and other teams across the Delivery value stream to keep our roadmap realistic, visible, and on track. This is a ground-floor opportunity to help shape how we plan and pace delivery with exposure to senior leadership. This position may have in-office requirements depending on candidate location. The level of position offered will be based on skills and experience at manager discretion."
Note there are some missing spaces: "AutoProgram Delivery & Enhancements (PDE)Build team" should be "AutoProgram Delivery & Enhancements (PDE) Build team". Also "you'llsupport" missing space. We should preserve the text as is? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't require us to fix typos. We can keep as is, but maybe we should keep original wording exactly. However we can add spaces for readability? That might be considered inventing? Safer to keep exactly as given, but we could correct obvious missing spaces as they are likely formatting errors. The instruction says do not invent or summarize away detail; correcting typos is not inventing new info, just fixing formatting. Might be okay. I'd keep as is but maybe add spaces where missing to make readable. I'd keep the substance but fix obvious spacing issues.
Let's rewrite description with proper spacing:
"Join the Personal Lines AutoProgram Delivery & Enhancements (PDE) Build team our brand-new, high-visibility team shaping next-generation auto rating programs and the core frameworks PDE relies on to deliver efficiently and with precision. In this role, you'll support portfolio planning and operational analytics across the delivery value stream. You'll bring analytical rigor to rollout scheduling, capacity forecasting, and performance metrics building the tools, schedules, and views that help the team sequence work, balance capacity, make informed trade-offs, and optimize in market value for the organization. You'll help turn a complex, multi-state, multi-program landscape into a clear, visible, data-driven plan. You'll partner with State Management, Program Management, Data Science, Tech, and other teams across the Delivery value stream to keep our roadmap realistic, visible, and on track. This is a ground-floor opportunity to help shape how we plan and pace delivery with exposure to senior leadership. This position may have in-office requirements depending on candidate location. The level of position offered will be based on skills and experience at manager discretion."
Now Responsibilities: "What You'll Do" bullet list. Let's extract each bullet:
- Analyze & recommend:Investigate planning and capacity questions, conduct scenario analysis, and synthesize your findings into clear, actionable recommendations that drive rollout schedules and cadence.
- Support portfolio planning:Help maintain an integrated view of program rollouts across states and programs including rollout sequencing, dependencies, milestones, and cad
- for any list of duties/requirements/benefits, and
for prose. Thus each section:
Section Name
then either... or
- ...