Sr. Business Analyst

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting. Content: Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." Location: "Location: Location: Chicago, IL / NY / Atlanta, GA" (duplicate). We can include location maybe as a short paragraph? Not a heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So location can be a short

. Then "Job Description" heading? Not needed; we will create sections. Then bullet list of experience: "5 to 10 years of experience in the Insurance industry Strong background in: Insurance Consulting Business Analysis Project/Program Management Insurance Transformation Experience in one or more insurance functions: Underwriting Claims Policy Administration Billing Risk Management Experience working with Tier 1 insurance carriers Strong client-facing and stakeholder management skills MBA or equivalent degree from a reputed Tier 1 university" Then "Preferred Experience Billing Transformation programs Strategy and operating model transformation Process redesign and optimization Technology transformation initiatives Agile/Scrum delivery Experience with: Guidewire Duck Creek Majesco Billing Platforms Policy Administration Systems Distribution Management Systems" Then list of duties: "Advise insurance clients on business and technology transformation initiatives Define future-state operating models and transformation roadmaps Lead stakeholder workshops and design-thinking sessions Conduct business process assessments and identify improvement opportunities Manage end-to-end project delivery Gather and document business requirements, workflows, and use cases Collaborate with business, operations, data, and technology teams Present recommendations and project updates to senior leadership Support organizational change management and user adoption" Then compensation: "The base compensation range for this role in the posted location is: $80000 - $120000 / per annum." Then a paragraph about compensation range etc. We need to include Pay section only if posting actually states them. It does state base compensation range. So we should include a Pay section with that info. However we must not include filler like "commensurate with experience". The posting includes details about compensation range, plus explanation. We should include the substantive content: base compensation range $80,000 - $120,000 per annum. Also mention that it's base compensation range, may be subject to change, actual compensation may fall outside, etc. That is substantive. We should include all that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the compensation details as given, not summarizing away. However we must not include boilerplate like "Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws." That is still substantive? It's part of the posting. It's not boilerplate? It's a legal disclosure. Might be considered boilerplate but it's part of the posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This compensation disclosure might be considered legal boilerplate. But it's about compensation transparency law. Might be considered legal. However the instruction says remove legal boilerplate. So we should drop that sentence. Also the sentence about "This range may be subject to change as permitted by law." etc. That's also legal. Might be considered boilerplate. But we need to preserve substantive info: the base compensation range. The rest is legal disclosure; we can drop it. However we need to be careful not to remove all detail; we can keep the range and maybe a brief note that it's base compensation range. The instruction: "Prefer a few substantive sections over many thin ones." So we can have a Pay section with the range. Benefits: The posting includes a Benefits section: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include: Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) Life and disability insurance Employee assistance programs Other benefits as provided by local policy and eligibility" We should include Benefits section with that list. Schedule: Not mentioned. So we should not include Schedule section. About the role: Could be the introductory paragraph describing Capgemini and role? The "About the role" could be the intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career..." That's about the company and role. We'll put that in About the role. Responsibilities: The list of duties (advise clients, define future-state, lead workshops, conduct assessments, manage delivery, gather requirements, collaborate, present recommendations, support change management). That's responsibilities. Requirements: Could be the experience and qualifications: 5-10 years experience, strong background in insurance consulting etc., MBA or equivalent, etc. That's requirements. Qualifications: Might overlap with requirements; but we can separate: maybe "Qualifications" for education/degree, certifications? The posting mentions MBA or equivalent degree from a reputed Tier 1 university. That's qualification. Also experience working with Tier 1 insurance carriers, strong client-facing skills. Could be under Requirements. We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We have to avoid empty sections. We have content for: - About the role: intro paragraph. - Responsibilities: duties list. - Requirements: experience, background, years, insurance functions, Tier 1 carriers, client-facing skills. - Qualifications: MBA or equivalent degree from reputed Tier 1 university. - Skills: maybe list of specific skills: Insurance Consulting, Business Analysis, Project/Program Management, Insurance Transformation, Underwriting, Claims, Policy Administration, Billing, Risk Management, client-facing, stakeholder management, Agile/Scrum, Guidewire, Duck Creek, Majesco, Billing Platforms, Policy Administration Systems, Distribution Management Systems, etc. Also maybe "Strategy and operating model transformation, Process redesign and optimization, Technology transformation initiatives". Those could be skills. - Benefits: as above. - Pay: base compensation range. We must not repeat job title. No headings for Job ID etc. We must output only HTML fragment, no /, no markdown. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to ensure we don't create sections with filler text. Each heading must have real specific content. Let's extract content precisely. Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." We can put that in

  under About the role. Location: we can include a short

  maybe after About the role? Not required but could be included as metadata. The instruction: fold minor metadata into a short

  or drop it. So we can add a

  for location: "Location: Chicago, IL / NY / Atlanta, GA". However note duplicate "Location: Location:" we should correct to just "Location: Chicago, IL / NY / Atlanta, GA". We'll include that as a short paragraph. Now Responsibilities: list of duties: - Advise insurance clients on business and technology transformation initiatives - Define future-state operating models and transformation roadmaps - Lead stakeholder workshops and design-thinking sessions - Conduct business process assessments and identify improvement opportunities - Manage end-to-end project delivery - Gather and document business requirements, workflows, and use cases - Collaborate with business, operations, data, and technology teams - Present recommendations and project updates to senior leadership - Support organizational change management and user adoption We'll put these in

  • . Requirements: experience and background: - 5 to 10 years of experience in the Insurance industry - Strong background in: Insurance Consulting, Business Analysis, Project/Program Management, Insurance Transformation - Experience in one or more insurance functions: Underwriting, Claims, Policy Administration, Billing, Risk Management - Experience working with Tier 1 insurance carriers - Strong client-facing and stakeholder management skills We'll put as list. Qualifications: - MBA or equivalent degree from a reputed Tier 1 university Maybe also "Preferred Experience" items could be under Skills or Requirements? The "Preferred Experience" includes Billing Transformation programs, Strategy and operating model transformation, Process redesign and optimization, Technology transformation initiatives, Agile/Scrum delivery, Experience with: Guidewire, Duck Creek, Majesco, Billing Platforms, Policy Administration Systems, Distribution Management Systems. Those are more like preferred skills/experience. We could put them under Skills. Skills: list of specific skills/experience: - Billing Transformation programs - Strategy and operating model transformation - Process redesign and optimization - Technology transformation initiatives - Agile/Scrum delivery - Experience with Guidewire - Experience with Duck Creek - Experience with Majesco - Experience with Billing Platforms - Experience with Policy Administration Systems - Experience with Distribution Management Systems - (also maybe the earlier listed: Insurance Consulting, Business Analysis, Project/Program Management, Insurance Transformation, Underwriting, Claims, Policy Administration, Billing, Risk Management, client-facing, stakeholder management) But those are already in Requirements. To avoid duplication, we could keep Requirements as experience/background, and Skills as specific technical/methodology skills. However the instruction says preserve ALL substantive information; we must not omit any. If we put some items only under Skills and not under Requirements, we might lose some. But we can include them in both sections? That would duplicate content, which is not prohibited but maybe not ideal. Better to allocate each piece to one section logically. Let's categorize: - Experience/background (years, industry, functions) -> Requirements. - Educational qualification -> Qualifications. - Specific technical/methodology skills and tools -> Skills. Thus Skills list includes: Billing Transformation programs, Strategy and operating model transformation, Process redesign and optimization, Technology transformation initiatives, Agile/Scrum delivery, Guidewire, Duck Creek, Majesco, Billing Platforms, Policy Administration Systems, Distribution Management Systems. Also maybe "client-facing and stakeholder management skills" could be under Skills as well. But we already have stakeholder management in Requirements. Could move to Skills. Let's keep stakeholder management under Skills. But we need to ensure we don't miss any: The posting also mentions "Strong client-facing and stakeholder management skills" under Requirements originally. We'll move that to Skills. Thus Requirements: years, industry, background, functions, Tier 1 carriers. Skills: client-facing, stakeholder management, Insurance Consulting, Business Analysis, Project/Program Management, Insurance Transformation, Underwriting, Claims, Policy Administration, Billing, Risk Management, Billing Transformation programs, Strategy and operating model transformation, Process redesign and optimization, Technology transformation initiatives, Agile/Scrum delivery, Guidewire, Duck Creek, Majesco, Billing Platforms, Policy Administration Systems, Distribution Management Systems. That