Senior Manager, State Arbitration

We need to output HTML fragment with sections: About the role? Actually we have sections: About the role? The posting includes "A Little About Us", "A Little About You", "Position Overview", "What You’ll Do", "What You’ll Bring To Zelis", "Location and Workplace Flexibility", "Base Salary Range", benefits description. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings where appropriate. We should not repeat job title. We should not include metadata like Job ID. We should drop boilerplate: EEO, accessibility, disclaimer, etc. Also drop navigation/cookie etc. We need to preserve all substantive information. We need sections only when posting has real specific content. So we can have: - About the role (maybe from Position Overview) - Responsibilities (What You’ll Do) - Requirements / Qualifications (What You’ll Bring To Zelis) - Skills (maybe AI proficiency etc) - Benefits (description of benefits) - Pay (Base Salary Range) - Schedule? Not given; location and workplace flexibility maybe not schedule; but we could include Location and Workplace Flexibility under maybe "Schedule"? Not exactly. The instruction says use headings for those categories if content exists. There's no explicit schedule info, but there is location and workplace flexibility. Could we treat that as "Schedule"? Probably not. Better to omit Schedule section if no explicit schedule. Could include "Location" but not in list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. If no content for a heading, omit it. Thus we need: - About the role: from Position Overview paragraph. - Responsibilities: What You’ll Do bullet list. - Requirements: What You’ll Bring To Zelis (experience, education, etc). Could also include qualifications. - Qualifications: maybe overlapping; but we can combine? The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they are separate headings. Might be better to have Requirements (experience, education) and Qualifications (skills, AI proficiency). However we have limited content. Let's parse: "What You’ll Bring To Zelis" includes: - Typically has Bach. +12 yrs.; Masters +8 yrs. - Attends company training and regional training in area of expertise. - Presents own work to members of department and external consultants and external professional conferences, - Collaborates externally, Hosts external guests, visitors and consultants - Requires proficiency using AI tools skillfully with an understanding of how to develop/create intelligent prompts and/or agents. - Experience leading multiple teams or large-scale projects. - Strong strategic thinking and execution capabilities. - Ability to influence cross-functional stakeholders and drive alignment. - Advanced leadership and coaching skills. - Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future. (This is a restriction; maybe we keep as part of Requirements.) Thus we can put Requirements (education/experience) and Qualifications (skills). But we could also just have one "Requirements" section covering all. Since they prefer few sections, we could combine into Requirements. But we need to follow instruction: use those headings when content exists. It doesn't say we must use all; we can choose which. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. We need to extract benefits: The paragraph after Base Salary Range: "Zelis’ full-time associates are eligible for a highly competitive benefits package as well, which demonstrates our commitment to our employees’ health, well-being, and financial protection. The US-based benefits include a 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage." Thus Benefits section with list. Pay: Base Salary Range $95,000.00 - $120,650.00 plus description about base pay being part of Total Rewards. We should preserve that. We should exclude location and workplace flexibility? It's substantive but not in allowed headings. Could we treat as "Schedule"? Not really. Might be better to omit because not matching headings. However instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list. But they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings. But they didn't forbid other headings. However to be safe, we could include a section for "Location and Workplace Flexibility" using

as well, as it's a heading. The examples are not exhaustive. So we can add that. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Location and Workplace Flexibility. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we need list. For Requirements we could list. For Benefits list. We need

  for prose. We must not repeat job title. Not include metadata like Job ID. We must remove boilerplate: EEO, Accessibility Support, Disclaimer, etc. Also remove "At Zelis we Get Stuff Done..." maybe that's fluff but it's part of About Us; we need to preserve substantive information. The "A Little About Us" paragraph is descriptive of company; we could include in About the role? Actually About the role should be about the role, not company. But we could incorporate some of that into About the role? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely should contain role overview. The "A Little About Us" is company description; maybe we could include it in About the role? But it's not about the role. However we could treat "About the role" as including company context? Might be okay. But we could also omit that fluff if not directly about role. However we need to preserve ALL substantive information; does company description count as substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it somewhere. Could we put it in a section like "About Zelis"? Not in allowed headings but we could still use

  for "About Zelis". The examples are not exclusive. So we could add a section "About Zelis". That would preserve that info. Thus sections: About Zelis, About the role (Position Overview), Responsibilities, Requirements, Benefits, Pay, Location and Workplace Flexibility. We need to ensure we don't create empty sections. Now craft HTML. We'll start with

  About Zelis

  then

  ...

  containing the "A Little About Us" paragraph(s). The paragraph: "At Zelis, we Get Stuff Done. So, let’s get to it! A Little About Us Zelis is modernizing the healthcare financial experience across payers, providers, and healthcare consumers. We serve more than 750 payers, including the top five national health plans, regional health plans, TPAs and millions of healthcare providers and consumers across our platform of solutions. Zelis sees across the system to identify, optimize, and solve problems holistically with technology built by healthcare experts – driving real, measurable results for clients. At Zelis, AI is woven into the fabric of how we work. Every associate is expected - and empowered - to partner with AI to challenge the status quo, accelerate innovation, and amplify their impact. This is a place for builders with a growth mindset who act with agility, embrace change, and use modern technology to shape smarter solutions, exceptional experiences, and the future of our industry for our clients, customers, and our culture." We need to keep that exactly? We can keep as is, maybe remove exclamation? Keep. Next

  About the role

  with Position Overview paragraph: "This role is responsible for overseeing multiple teams or a large, complex team within the claims negotiation function. This role focuses on driving operational excellence, implementing strategic initiatives, and ensuring compliance across all claims processes. This role partners with leadership to set goals, monitor performance, and lead process improvement efforts that enhance efficiency and customer satisfaction." Then

  Responsibilities

  with
  • items from "What You’ll Do". List each sentence as separate li. Sentences: - Lead and manage multiple teams of negotiators, ensuring alignment with organizational objectives. - Develop and implement departmental strategies to optimize claims resolution outcomes. - Oversee high-value and complex claims negotiations, providing guidance and approval as needed. - Monitor performance metrics and drive continuous improvement initiatives. - Collaborate with senior leadership to establish policies, procedures, and best practices. - Analyze claims data to identify trends and recommend strategic improvements. - Build and maintain strong relationships with internal and external stakeholders. - Ensure compliance with regulatory requirements and company standards. - Provide training, support, and development opportunities to team members to ensure high performance and engagement. - Conduct regular performance reviews, provide feedback, and identify opportunities for professional development. Make each
  • . Then

    Requirements

    with list from "What You’ll Bring To Zelis". Items: - Typically has Bach. +12 yrs.; Masters +8 yrs. - Attends company training and regional training in area of expertise. - Presents own work to members of department and external consultants and external professional conferences. - Collaborates externally, Hosts external guests, visitors and consultants. - Requires proficiency using AI tools skillfully with an understanding of how to develop/create intelligent prompts and/or agents. - Experience leading multiple teams or large-scale projects. - Strong strategic thinking and execution capabilities. - Ability to influence cross-functional stakeholders and drive alignment. - Advanced leadership and coaching skills. - Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future. Make each
  • . Then

    Benefits

    with
    • items from benefits paragraph: "The US-based benefits include a 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage." We could split each benefit: 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, health benefits including medical, dental, vision, and prescription drug coverage. Make list. Then

      Pay

      with

      containing base salary range and description: "Base Salary Range $95,000.00 - $120,650.00 At Zelis we are committed to providing fair and equitable compensation packages. The base salary range allows us to make an offer that considers multiple individualized factors, including experience, education, qualifications, as well as job-related and industry-related knowledge and skills, etc. Base pay is just one part of our Total Rewards package, which may also include discretionary bonus plans, commissions, or other incentives depending on the role." We could keep as paragraph. Then

      Location and Workplace Flexibility

      with

      containing that paragraph: "Zelis is headquartered in the U.S., with multiple locations across the country and in Hyderabad, India. Check out our locations to learn more about our offices.