Jobs · Wyoming

Field Property Claims Adjuster

Liberty Mutual Insurance · Cheyenne, WY · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "About Us" maybe? Actually "About Us" includes pay philosophy and benefits info. We need to extract relevant content. Let's parse the description: - Intro: "Join us as a Field Property Claims Adjuster where you’ll be responsible for helping our customers navigate the claims process and get back on their feet following damage to the homeowner’s property. This is a role where people who love every day to be new, different and exciting, can thrive – you’ll be traveling on the road to meet customers in person, providing hands-on assessment of damage and empathetic support. The Field Property Claims Adjuster will be traveling locally to insured homes within Cheyenne, WY (82001) and surrounding areas. To be successful within the role, candidates should live within or near this area. Sign-On Bonus Available! We’re offering a sign-on bonus for experienced and actively licensed new hires." - "What You’ll Do" list: bullet points (we need to convert to
  • ). - "Position details" includes: Territory-based work..., Training & support..., Mileage Reimbursement... - "Qualifications" list: bullet points. - "About Us" includes Pay Philosophy, benefits, etc. We need sections: About the role (maybe intro), Responsibilities (What You'll Do), Requirements (maybe qualifications?), Qualifications (maybe same as Requirements?), Skills (maybe derived from qualifications?), Benefits, Pay, Schedule. We must not create sections with placeholder text. So we need to see if we have actual content for each. - About the role: we have intro paragraph describing role. Good. - Responsibilities: we have "What You’ll Do" bullet list. Good. - Requirements: maybe the qualifications list? But we also have a separate "Qualifications" heading in the posting. The instructions say we can have sections like Requirements, Qualifications, Skills. We need to decide what to put where. Likely "Qualifications" section corresponds to the bullet list under "Qualifications". "Requirements" maybe could be similar but we might not have separate content; we could combine? But we must not create empty sections. So we should only include sections where we have specific content. The posting has a "Qualifications" list. It also has "About Us" with pay philosophy and benefits. It also mentions "Sign-On Bonus Available!" and "Mileage Reimbursement". Those could go under Benefits or Pay. We need to extract Pay: The posting includes "Pay Philosophy: The typical starting salary range for this role is determined by a number of factors...". That's vague but it's actual content about pay philosophy. It says typical starting salary range determined by factors, full salary range reflects competitive labor market value, some roles have commission/bonus earnings. That's substantive but not a specific number. However the instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay philosophy, though it's not a specific number but it's still stating something about pay. Is that considered filler? It's not "commensurate with experience" but it's a description. I'd say it's substantive enough to include a Pay section. Benefits: The posting mentions "Sign-On Bonus Available!", "Mileage Reimbursement: This role offers mileage reimbursement. You may qualify for a company-provided vehicle once mileage requirements are met." Also later: "We value your hard work... offering you benefits that support your life and well-being. To learn more about our benefit offerings please visit: https://...". That's generic but we have specific benefits: sign-on bonus, mileage reimbursement, possible company-provided vehicle. Also mention of comprehensive benefits, workplace flexibility, professional development opportunities, Employee Resource Groups. Those are benefits. So we can include Benefits section with those specifics. Schedule: The posting does not mention schedule specifics (e.g., full-time, hours). It mentions traveling locally, but not schedule. So we should not create Schedule section. Now we need to decide on sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We have content for About the role (intro). Responsibilities (What You'll Do). Qualifications (the bullet list under Qualifications). Requirements maybe we could extract from the intro: "To be successful within the role, candidates should live within or near this area." Also "Sign-On Bonus Available! We’re offering a sign-on bonus for experienced and actively licensed new hires." That's more about bonus than requirement. Also "Working knowledge of claims handling procedures and operations." etc are in Qualifications. So Requirements may be redundant. Could we treat Requirements as the same as Qualifications? But we need to avoid duplication. Perhaps we can put Requirements as the bullet list under "Qualifications" and rename? But the instruction says we can use those headings if we have real specific content. We have content for Qualifications (the bullet list). We could also have Requirements as the bullet list under "What You'll Do"? No that's responsibilities. So maybe we skip Requirements section to avoid duplication. But we need to see if any content fits Requirements distinct from Qualifications: The posting includes "To be successful within the role, candidates should live within or near this area." That's a requirement (location). Also "Sign-On Bonus Available! We’re offering a sign-on bonus for experienced and actively licensed new hires." That's not a requirement but a bonus. Also "Ability to obtain proper licensing as required." That's in qualifications. So we could make a Requirements section with location requirement and maybe licensing requirement? But licensing is also in qualifications. Might duplicate. Better to follow the posting's headings: They have "Qualifications". They don't have a separate "Requirements". So we can omit Requirements section to avoid thin content. However the instruction says we can include sections only when posting has real specific content for it. It doesn't require us to use all possible headings. So we can include About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Skills? The qualifications list includes skills like communication, negotiation, computer skills, etc. Could we extract a Skills section? But that would duplicate Qualifications. Better to keep Qualifications as the section that includes both knowledge, skills, abilities. So we skip Skills. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Now we need to format: - About the role:

    About the role

    then

    with the intro paragraph(s). Should we split into multiple paragraphs? Could combine into one

    but we can have multiple

    for readability. We'll keep as one

    containing the intro text (maybe two sentences). Ensure we preserve all substantive info: include mention of traveling locally to Cheyenne, WY (82001) and surrounding areas, candidates should live within or near this area, sign-on bonus available for experienced and actively licensed new hires. - Responsibilities:

    Responsibilities

    then
    • items from "What You’ll Do". Need to capture each bullet exactly. Let's list them: 1. Investigate and evaluate onsite to resolve complex coverage and damage issues to include preparing complete estimates of repair for the covered damages. This may include accessing roofs by ladder, inspecting attics, crawl spaces and basements in search of damage. 2. Handle moderate to complex claims independently while managing your workload, from first notice of loss to final closure. 3. Be expected to work in a vehicle in the field daily while occasionally handling assignments from the desk. 4. Explain coverage of loss, assist policyholders with itemization of damages, emergency repairs and additional living arrangements. 5. Work with and coordinate a few vendor services such as contractors, emergency repair, cleaning services and various replacement services. 6. May be called upon for catastrophe duty. We need to preserve the exact wording. Ensure no extra or missing punctuation. - Qualifications:

      Qualifications

      then
      • items from the Qualifications bullet list. List them: - Working knowledge of claims handling procedures and operations. - Proven ability to provide exceptional customer service. - Effective negotiation skills. - Ability to effectively and independently manage workload while exhibiting good judgment. - Strong written/oral communication and interpersonal skills. - Computer skills with the ability to work with multi-faceted systems. - The capabilities, skills and knowledge required through a bachelor’s degree or equivalent experience and at least 1 year of directly related experience. - Ability to obtain proper licensing as required. - The ability to handle multiple competing priorities and organize your day. - Strong time management and organizational skills. - Demonstrated understanding of building construction principles. Check if any duplicates: okay. - Benefits:

        Benefits

        then
        • items: Sign-On Bonus Available! (maybe phrase as "Sign-on bonus for experienced and actively licensed new hires"), Mileage reimbursement (role offers mileage reimbursement; may qualify for company-provided vehicle once mileage requirements are met), Comprehensive benefits, workplace flexibility, professional development opportunities, Employee Resource Groups. Also mention of benefits supporting life and well-being (maybe generic). We need to preserve all substantive info; we should not invent. So we list exactly what is stated. Let's extract benefits sentences: From intro: "Sign-On Bonus Available! We’re offering a sign-on bonus for experienced and actively licensed new hires." From Position details: "Mileage Reimbursement: This role offers mileage reimbursement. You may qualify for a company-provided vehicle once mileage requirements are met." From About Us: "We value your hard work, integrity and commitment to make things better, and we put people first by offering you benefits that support your life and well-being. To learn more about our benefit offerings please visit: https://www.libertymutualgroup.com/about-lm/careers/benefits" Also: "At Liberty Mutual, our goal is to create a workplace where everyone feels valued, supported, and can thrive. We build an environment that welcomes a wide range of perspectives and experiences, with inclusion embedded in every aspect of our culture and reflected in everyday interactions. This comes to life through comprehensive benefits, workplace flexibility, professional development opportunities, and a host of opportunities provided through our Employee Resource Groups." Thus benefits include: comprehensive benefits, workplace flexibility, professional development opportunities, Employee Resource Groups, sign-on bonus, mileage reimbursement, potential company-provided vehicle, benefits supporting life and well-being (maybe we can keep as "benefits that support your life and well-being"). We should not include the link to learn more (that's application instruction? It's not exactly application instruction but it's a link for more info; maybe we can keep as part of benefits? It's not a benefit itself but a pointer. The instruction says remove application instructions. This link is not an application instruction but a link to learn more about benefits. Might be considered boilerplate? It's not navigation/legal/EEO. It's a link to benefits page. Could be considered part of benefits info. However it's a URL; we could keep it as part of benefits? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a link to benefits page; maybe we keep it as part of benefits? But it's not a benefit itself; it's a reference. Safer to omit the link, as it's not a benefit detail. We'll keep the descriptive text. Thus Benefits
            items: - Sign-on bonus for experienced and actively licensed new hires. -

Similar jobs