Multi-Line Claim Adjuster - (Municipal/Public Works)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. Let's parse the posting. Overview: Municipal Liability Claims Adjuster Location: Albuquerque, New Mexico Schedule: Full-Time | Hybrid | Flexible Start Time Salary Range: $75,000 - $85,000 annually Then "Build Your Career With Purpose at CCMSI" paragraph. Then "Job Summary" paragraph. Then "Responsibilities" bullet list. Then "Required Qualifications" bullet list. Then "Nice To Have" bullet list. Then "How We Measure Success" bullet list. Then "Why You’ll Love Working Here" bullet list (benefits etc.) Then "Compensation & Compliance" paragraph. Then "Visa Sponsorship", "ADA Accommodations", "Equal Opportunity Employer" (these are boilerplate to remove). Then "Our Core Values" paragraph. Then hashtags. We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. - About the role: Could include overview, job summary, maybe location, schedule? But schedule is separate section. Pay separate. Benefits separate. - Responsibilities: list of duties. - Requirements: maybe required qualifications. - Qualifications: maybe nice to have? Or could combine required and nice? But we have both Requirements and Qualifications sections. Could treat Requirements as required qualifications, Qualifications as nice-to-have or additional qualifications. Or we could treat Requirements as required qualifications, Qualifications as nice-to-have. - Skills: maybe skills like analytical, negotiation, organization, communication, etc. Could be extracted from required qualifications. - Benefits: from "Why You’ll Love Working Here" includes PTO, holidays, medical/dental/vision/life/disability insurance, retirement plans (401k, ESOP), career growth, culture. - Pay: salary range $75,000 - $85,000 annually, plus mention of bonuses etc. - Schedule: Full-Time | Hybrid | Flexible Start Time. We must not create sections with filler. Ensure each section has real specific content. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate: Visa Sponsorship, ADA Accommodations, Equal Opportunity Employer, Our Core Values maybe? Core values could be considered substantive? It's about culture but maybe considered boilerplate? It's not explicitly listed as boilerplate but could be considered fluff. However it's specific to CCMSI values. Might be okay to include under About the role or Benefits? But we have no section for values. Could incorporate into About the role paragraph. We must not include duplicated lines. We must not include application instructions (none present besides maybe "If that sounds like your kind of workplace, we’d love to meet you." That's not application instruction but could be considered fluff. Might be okay to keep in About the role. We must not include hashtags. Now produce HTML. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

(nice-to-have)

Skills

• ...
...

(maybe analytical, negotiation, organization, communication)

Benefits

• ...
...

Pay

...

Schedule

...

Check each section for real content. About the role: Could combine overview paragraph, job summary, location, maybe core values. Let's draft: "CCMSI is seeking a Municipal Liability Claims Adjuster to investigate, evaluate, negotiate, and resolve complex municipal liability claims. This role handles liability exposures involving public entities, municipalities, utilities, and related organizations across New Mexico and Texas. The ideal candidate possesses strong knowledge of liability law, auto liability, property damage claims, and civil rights exposures while delivering high-quality claims service to clients and stakeholders. CCMSI partners with global clients to solve complex risk management challenges, delivering measurable results through advanced technology, collaborative problem-solving, and an unwavering commitment to their success. As the largest privately-owned Third Party Administrator (TPA), CCMSI delivers customized claim solutions that help clients protect their employees, assets, and reputations. We are a certified Great Place to Work®, and our employee-owners are empowered to grow, collaborate, and make meaningful contributions every day." That seems substantive. Responsibilities: list from posting: - Investigate, evaluate, and adjust municipal liability claims in accordance with established claims handling standards. - Analyze liability exposures, damages, coverage issues, and available defenses. - Manage litigation-related claim activities and collaborate with defense counsel as needed. - Negotiate settlements within delegated authority and client guidelines. - Maintain accurate documentation, reserves, and claim reporting throughout the life of each claim. - Communicate effectively with clients, claimants, attorneys, vendors, and business partners. - Provide responsive customer service while maintaining compliance with jurisdictional requirements. - Support client service objectives across multiple public entity and municipal accounts. That's 8 items. Requirements: Required Qualifications bullet list: - Experience handling liability claims. - Working knowledge of liability law. - Experience with auto liability claims investigations and evaluation. - Experience handling property damage claims. - Knowledge of civil rights exposures and claim issues. - New Mexico adjuster license. - Texas adjuster license. - Strong analytical, negotiation, organization, and communication skills. That's 8 items. Qualifications: Nice To Have: - Estimating experience. - Experience handling municipal, public entity, utility, or governmental claims. - Bilingual (Spanish) proficiency — highly valued for communicating with claimants, employers, or vendors, but not required. That's 3 items. Skills: Could extract from required qualifications: Strong analytical, negotiation, organization, and communication skills. Also maybe "strong knowledge of liability law" etc. But we might duplicate. Better to list skills: Analytical thinking, negotiation, organization, communication, liability law knowledge, auto liability claims investigation, property damage claims handling, civil rights exposures understanding. But that may be too much. However we need to avoid duplication with Requirements. Could still include but ensure not repeating same phrasing. Could list: Analytical thinking, negotiation, organization, effective communication, knowledge of liability law, auto liability claims investigation, property damage claims handling, civil rights exposures understanding. But we already have those in Requirements. Might be okay to have Skills section summarizing those skills. The instruction: Prefer a few substantive sections over many thin ones. Having Skills may be thin if it's just a repeat. Could combine Skills into Requirements? But we have both sections; maybe we can omit Skills if not enough distinct content. However we need to follow the instruction: include a section ONLY when posting has real, specific content for it. Does the posting have specific content for Skills? It mentions "Strong analytical, negotiation, organization, and communication skills." That's a skill set. Could be considered Skills section. But we already have that in Requirements. However we could still make a Skills section with those skills, but it would be duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited explicitly, but we should avoid redundancy? Not explicitly forbidden. However they said "Prefer a few substantive sections over many thin ones." Having Skills section may be thin if it's just a repeat of one line. Could combine into Requirements and omit Skills. Let's see if we can find other skills: maybe "estimating experience" is a skill but it's in Nice To Have. Could treat Skills as combination of analytical, negotiation, organization, communication, estimating, bilingual? But bilingual is nice to have. Better to omit Skills section and incorporate those skills into Requirements or Qualifications. However we have both Requirements and Qualifications sections; we can put the skill line in Requirements. Then we don't need Skills. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each. About the role: we have paragraph. Responsibilities: list. Requirements: list (including skill line). Qualifications: nice-to-have list. Benefits: from Why You’ll Love Working Here: 4 weeks PTO + 10 paid holidays first year; comprehensive benefits: Medical, Dental, Vision, Life, and Disability Insurance; Retirement plans: 401(k) and Employee Stock Ownership Plan (ESOP); Career growth: Internal training and advancement opportunities; Culture: A supportive, team-based work environment. Also maybe "This is where we shine, and we hire adjusters who want to shine with us." That's fluff. Pay: Salary Range: $75,000 - $85,000 annually. Also mention "The posted salary reflects CCMSI’s good-faith estimate in accordance with applicable pay transparency laws. Actual compensation will be based on qualifications, experience, geographic location, and internal equity. This role may also qualify for bonuses or additional forms of pay." That's substantive. Schedule: Full-Time | Hybrid | Flexible Start Time. Now ensure we removed boilerplate: Visa Sponsorship, ADA Accommodations, Equal Opportunity Employer, Our Core Values, hashtags. Also remove duplicated lines: The "Build Your Career With Purpose at CCMSI" paragraph maybe duplicated? Not exactly. We'll include in About the role. Now produce HTML. We must not include or . Just fragment. Let's craft. About the role paragraph: combine overview and job summary and maybe core values? We'll keep concise but preserve all substantive info. Must not lose any substantive info. Let's list all substantive info from overview and job summary: Overview: Municipal Liability Claims Adjuster Location: Albuquerque, New Mexico Schedule: Full-Time | Hybrid | Flexible Start Time Salary Range: $75,000 - $85,000 annually But schedule and salary go to their sections. Overview also includes: "Build Your Career With Purpose at CCMSI At CCMSI, we partner with global clients to solve their most complex risk management challenges, delivering measurable results through advanced technology, collaborative problem-solving, and an unwavering commitment to their success. We don’t just process claims—we support people. As the largest privately-owned Third Party Administrator (TPA), CCMSI delivers customized claim solutions that help our clients protect their employees, assets, and reputations. We are a certified Great Place to Work®, and our employee-owners are empowered to grow, collaborate, and make meaningful contributions every day." Job Summary: "CCMSI is seeking a Municipal Liability Claims Adjuster to investigate, evaluate, negotiate, and resolve complex municipal liability claims. This is a claims adjuster role responsible for handling liability exposures involving public entities, municipalities, utilities, and related organizations across New Mexico and Texas. The ideal candidate will possess strong knowledge of liability law, auto liability, property damage claims, and civil rights exposures while delivering high-quality claims service to clients and stakeholders." We must preserve all that. So About the role should include all of that except schedule and salary (which go elsewhere). Also location maybe we can mention location in About the role? Could be but location is not a heading; we could include location in About the role paragraph. However location is part of overview; we could keep it there. But we have Schedule section separate; location not schedule. It's fine to include location