Claims Total Loss Specialist

We need to output HTML fragment with sections: About the team? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes "About The Team" (maybe treat as About the role). Then "What You Will Do" (Responsibilities). Then "Your profile" (Requirements/Qualifications/Skills). Then salary range (Pay). Then schedule (hybrid schedule). Then Benefits listed. Also there is other info like Turo description etc but we should not include boilerplate like EEO, legal, scam alert, AI policy, etc. Also we should not repeat job title. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate. We need to decide which headings to use. We have content: - About The Team: description of role handling higher complexity claims, investigations, etc. This is about the role. So we can use

About the role

with paragraph(s) containing that description. - What You Will Do: list of duties. Use

Responsibilities

with

• items. - Your profile: list of qualifications/skills. Could be split into Requirements, Qualifications, Skills. But we need to decide based on content. The "Your profile" includes: Investigative mindset..., Strong ability..., Ability to explain..., Strong organizational..., Proficient in reviewing..., Communicate clearly..., Strong proficiency..., Ability to multitask..., Proficiency with technology: macOS and Google Docs, Bonus if you have Bachelor's degree. This is a mix of skills and qualifications. We could put under

  Qualifications

  or

  Skills

  . Since we have both, maybe we can use

  Qualifications

  for the list, and maybe

  Skills

  not needed if overlapping. But we need to avoid thin sections. Better to combine into one section, maybe

  Qualifications and Skills

  but heading must be exactly one of the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create custom heading. So we need to map content to one of those. Could split: Requirements (maybe the investigative mindset etc) and Skills (proficiency with tech, Bachelor's). But we have to avoid thin sections. However we have enough content for both. Let's extract: Requirements (maybe mandatory): Investigative mindset to seek out information with the ability to analyze evidence and draw conclusions based on logical reasoning. Strong ability to exercise independent judgment and decision-making beyond established guidelines and processes. Ability to explain complex situations, using clear and concise language. Strong organizational skills, with an ability to independently manage a pending inventory of claims assigned to you. Proficient in reviewing and evaluating estimates, strong understanding of collision damage theory, to determine both causation and costs. Communicate clearly, professionally, and empathetically. Strong proficiency in verbal and written customer service communications. Ability to multitask across technical platforms. Skills (maybe): Proficiency with technology: macOS and Google Docs. Bonus if you have Bachelor's degree. We could also treat Bachelor's as Qualification. But we need to avoid filler like "Bonus if you have Bachelor's degree" is substantive. Thus we can have:

  Requirements

  with
  of the first set.

  Skills

  with
  of proficiency with macOS/Google Docs and Bachelor's degree. Now Pay: we have salary range: $50,000 - $65,000 annually. Also mention equity and benefits. So we can have

  Pay

  with paragraph containing that. Schedule: hybrid schedule: in-office 3 days per week on Mondays, Wednesdays, and Thursdays. Also mention Turo highly values in-office to foster collaborative environment. So we can put that. Benefits: list: Competitive salary, equity, benefits, and perks for all full-time employees; Employer-paid medical, dental, and vision insurance (Country specific); Retirement employer match; Learning & Development stipend; Turo host matching program; Turo travel credit; Cell phone and internet stipend; Paid time off; Paid holidays, volunteer time off, and parental leave; In-office lunch, office snacks, fun activities for those in office full-time or hybrid. We should not include boilerplate like "We are committed to building a diverse team..." etc. That's EEO/diversity, which is boilerplate to remove. Also remove "About Turo" description, equal opportunity, etc. Also remove scam alert, AI policy, etc. We must preserve all substantive information. The "About Turo" paragraph is descriptive of company; is that substantive? It's about the company, not the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Turo" is not exactly boilerplate but could be considered company overview; but it's not about the role. The instruction says preserve ALL substantive information; does company overview count as substantive? Possibly yes, but it's not about the role. However the sections we can output are limited to those headings; we could include a section like "About the role" but not "About Turo". The company overview might be considered filler; but it's not explicitly listed as boilerplate to remove. However typical job postings include "About the company" which might be considered not required. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit the company overview, are we removing substantive information? It's about Turo, not the role. The user might want to keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company overview. But the sections we can output are limited to those headings; we could add a section like "About the role" but not "About the company". There's no heading for company overview. So we likely should omit it because we cannot create a heading for it, and we shouldn't add random paragraphs outside headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must wrap everything in headings; we could have paragraphs outside headings? But earlier: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It didn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we could still have other headings but they'd be non-standard. Safer to stick to those. Thus we will omit company overview. Now we need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now construct HTML. We'll have:

  About the role

  The Total Loss Claims Specialist will handle claims involving higher complexity, requiring significant levels of understanding and interpretation of Turo’s operating policies and procedures. They will independently conduct investigations to understand causation, determine if coverage applies and exercise their judgment on matters of significant financial impact to Turo and Turo’s hosts.

  Responsibilities

  • Utilize their expertise and education to investigate claims with a high financial impact on Turo.
  • Interpret policies, determine appropriate methods of investigation, interview customers and assess credibility, analyze damages, and determine on behalf of Turo if a host is eligible for Protection.
  • Communicate with customers to gather information, explain protection and procedures, educate the hosts, explain why coverage is or is not applicable in certain circumstances and effectively negotiate claim resolutions.
  • Investigate and make recommendations, on behalf of Turo management, for requests for escalation or reconsideration from standard/fast track claims teams, including review of Fair Claims and presentation to arbitration as needed.
  • Apply your discretion and judgment to waive or make exceptions to process and policy to achieve the right outcome for our host, when warranted.
  • Participate in special projects, improvement actions or other business changes, including making recommendations on claims process improvements, objectives, and KPIs.
  • Attend meetings, huddles, 1x1 and training.
  • Performs other related duties as assigned.

  Requirements

  • Investigative mindset to seek out information with the ability to analyze evidence and draw conclusions based on logical reasoning.
  • Strong ability to exercise independent judgment and decision-making beyond established guidelines and processes.
  • Ability to explain complex situations, using clear and concise language.
  • Strong organizational skills, with an ability to independently manage a pending inventory of claims assigned to you.
  • Proficient in reviewing and evaluating estimates, strong understanding of collision damage theory, to determine both causation and costs.
  • Communicate clearly, professionally, and empathetically.
  • Strong proficiency in verbal and written customer service communications.
  • Ability to multitask across technical platforms.

  Skills

  • Proficiency with technology: macOS and Google Docs.
  • Bonus if you have Bachelor's degree.

  Pay

  For this role, the target base salary range in Phoenix is $50,000 - $65,000 annually. This role is also eligible for equity and benefits.

  Schedule

  Turo highly values having employees working in-office to foster a collaborative work environment and company culture. This role will be in-office on a hybrid schedule — Turists will be expected to work in the office 3 days per week on Mondays, Wednesdays, and Thursdays.

  Benefits

  • Competitive salary, equity, benefits, and perks for all full-time employees
  • Employer-paid medical, dental, and vision insurance (Country specific)
  • Retirement employer match
  • Learning & Development stipend to invest in your professional development
  • Turo host matching program
  • Turo travel credit
  • Cell phone and internet stipend
  • Paid time off to relax and recharge
  • Paid holidays, volunteer time off, and parental leave
  • For those who are in the office full-time or hybrid we have in-office lunch, office snacks, and fun activities
  Check for any leftover boilerplate: we removed EEO, scam alert, AI policy, etc. Also removed "About Turo" description. Also removed "We are committed to building a diverse team..." etc. Also removed "Even if you don't meet every qualification..." etc. Also removed "Your recruiter can share more information about the various in-office perks Turo offers." Actually we kept some of that in schedule? We mentioned "Turo highly values having employees working in-office..." which is from that sentence. That's okay. We also kept "Your recruiter can share more information about the various in-office perks Turo offers." We omitted that line; it's not essential. It's maybe filler but not boilerplate. Could keep but it's not needed. We omitted. Check for duplicated lines: none. Now ensure we didn't miss any substantive info: The "About The Team" paragraph we used. The "What You Will Do" we turned into responsibilities list. The "Your profile" we split into requirements and skills. The salary and