Senior Property Claims Adjuster (Complex, Large Loss Claims)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting has "Role Overview" which is similar to "About the role". So we can use About the role
and put the prose.
- Key Responsibilities -> Responsibilities
with list.
- What You Bring -> could be Requirements/Qualifications/Skills. The instruction: we can have sections Requirements, Qualifications, Skills. We need to decide which to use. The content includes education, experience, license, communication skills, organizational, etc. Could split into Requirements (education, experience, license) and Skills (communication, organizational, problem-solving, etc.) But we can also combine into one section "Requirements". However instruction: prefer a few substantive sections over many thin ones. So maybe we combine into one Requirements
with list.
- What We Offer -> Benefits. So Benefits
with list.
- Pay and Schedule: not mentioned explicitly. No salary numbers, just "Competitive salary". That's vague but still mentions salary. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive salary and comprehensive benefit package". That's a statement about salary being competitive but no specifics. Is that enough to include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive salary". That's a statement about pay, albeit vague. Should we include Pay? The instruction also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive salary" is somewhat vague but not exactly placeholder like "commensurate with experience". It's a qualitative statement. I'd say we can include Pay section with that statement. However we already have Benefits section that includes "competitive salary and comprehensive benefit package". Might be redundant. Better to put salary within Benefits? But Benefits already includes comprehensive benefit package. The phrase "Competitive salary and comprehensive benefit package" could be split: Pay: Competitive salary; Benefits: comprehensive benefit package etc. However we have a Benefits section already; we could keep Benefits and not add Pay to avoid duplication. The instruction: prefer a few substantive sections over many thin ones. So maybe we omit Pay and just include Benefits covering both salary and benefits. But the Benefits section currently lists many items; we could add "Competitive salary" as a bullet.
- Schedule: not mentioned. No schedule info. So omit.
- Also there is location and employment type etc. That could be considered metadata; we can fold into a short
at top maybe. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short paragraph with location, employment type, maybe requisition dates? Those are metadata. We'll include a short
after the heading? Actually we should not have a heading for metadata. Just a
containing location, employment type, maybe requisition dates. - Also there is a disclaimer and EEO etc which we must remove (boilerplate). So we ignore those. - Also "About Us" section maybe could be considered "About the role"? Actually it's about the company. Could be considered "About the role"? Not exactly. The instruction: use headings for sections like About the role, Responsibilities, etc. The "About Us" is company description; could be considered part of "About the role"? Might be extra but we could include as a separate section? Not in the list of allowed headings. The allowed headings are those examples; we could still use other headings? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but likely we should stick to those. The "About Us" is not one of those; maybe we can incorporate into About the role? Or we could drop it as boilerplate? It's not boilerplate; it's company description. Might be considered relevant. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the "About Us" content. Where to put it? Could be a section "About the company" but not in allowed headings. However we could treat it as part of "About the role"? Might be a stretch. Perhaps we can add a heading "About the company" even though not listed; but the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings and incorporate the About Us content into About the role section (since it's about the company and role). We'll add a paragraph after the role overview.
Thus final HTML:
About the role
About the role
Location: Remote (MA, GA, MS, UT, AL, FL, IN, IA, LA, MO, NC, OK, PA, TX, WI) / Hybrid (in Troy, MI). Employment Type: Full-Time. Requisition Begin Date: 07/28/2026. Requisition End Date: 10/28/2026 (posting may close earlier if filled or business needs change.)
We are seeking a Senior Property Claims Adjuster to manage complex, multi-line first party claims with a high degree of autonomy and technical expertise. In this role, you will handle claims from initial investigation through resolution, applying advanced coverage knowledge and strong analytical judgment to deliver fair, timely outcomes while providing exceptional service to our insureds and partners. Tokio Marine HCC - Public Risk Group, a member of the Tokio Marine group of companies, is a market leader in providing specialized insurance products for municipal entities. We cover counties, cities, townships, villages, police departments, prisons, fire departments and more. We serve the growing insurance and risk management needs of medium and large governmental entities and provide property and casualty insurance coverages in multiple states.
But we need to avoid duplication: The role overview paragraph already includes some of that. We'll combine. Better:About the role
We are seeking a Senior Property Claims Adjuster to manage complex, multi-line first party claims with a high degree of autonomy and technical expertise. In this role, you will handle claims from initial investigation through resolution, applying advanced coverage knowledge and strong analytical judgment to deliver fair, timely outcomes while providing exceptional service to our insureds and partners. Tokio Marine HCC - Public Risk Group, a member of the Tokio Marine group of companies, is a market leader in providing specialized insurance products for municipal entities. We cover counties, cities, townships, villages, police departments, prisons, fire departments and more. We serve the growing insurance and risk management needs of medium and large governmental entities and provide property and casualty insurance coverages in multiple states.
Location: Remote (MA, GA, MS, UT, AL, FL, IN, IA, LA, MO, NC, OK, PA, TX, WI) / Hybrid (in Troy, MI). Employment Type: Full-Time. Requisition Begin Date: 07/28/2026. Requisition End Date: 10/28/2026 (posting may close earlier if filled or business needs change.)
But we should avoid using maybe not needed; just plain text. Now Responsibilities: list each bullet. We need to extract from "Key Responsibilities" block: - Analyze coverage issues, conduct investigations, and evaluate damages and liability to determine validity of complex property claims. - Formulate and issue coverage position letters, seeking appropriate authority from management. - Communicate with insureds and agents and provide customer service to the high standards of the company. - Investigate claims by conducting interviews, assigning an Independent Adjuster to complete an on-site scene investigation, and preparing written correspondence to insureds, agents, and claimants. - Ability to analyze an estimate of structural damage written with Xactimate software. - Review contractor estimates, independent adjuster reports, appraiser reports, and engineering reports to determine extent of damages. - Recommend reserves and settlements that are in excess of the defined authority limit. - Recommend and present proposed settlement terms for claims that are in excess of the defined authority limit. - Negotiate claim settlements with insureds, contractors, and other parties in the claims process within defined authority limits. - Maintain claim files and documents in accordance with company policy and procedures. - Travel for meditations and other business/ company meetings. Note: "Travel for meditations" maybe typo for mediations. Keep as is. We'll put each as and then - for lists,
for prose.
We need to ensure no extra whitespace? It's fine.
Let's craft.
First, maybe a short
for metadata (location, employment type, requisition dates). Then
About the role
with prose.
Then Responsibilities
with .
Then Requirements
with .
Then Benefits
with .
We'll not include Pay or Schedule.
Check that we haven't missed any substantive info: The "What You Bring" includes "Strong interpersonal and negotiation skills." included. Good.
Now ensure we didn't include any filler like "commensurate with experience
for prose. We need to ensure no extra whitespace? It's fine. Let's craft. First, maybe a short
for metadata (location, employment type, requisition dates). Then
About the role
with prose. ThenResponsibilities
with- .
Then
Requirements
with- .
Then
Benefits
with- .
We'll not include Pay or Schedule.
Check that we haven't missed any substantive info: The "What You Bring" includes "Strong interpersonal and negotiation skills." included. Good.
Now ensure we didn't include any filler like "commensurate with experience