Head of Claims
Sola Insurance · Atlanta, GA · 1 mo ago
On-siteBusiness Development$190k–$240k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We need to extract content.
First, remove boilerplate: "Atlanta, GA (on-site)" maybe location but not needed as heading. The TLDR checklist lines are bullet points; they are part of description. We'll treat as part of About the role or maybe a summary.
We need to preserve all substantive info.
Let's parse:
- Intro: "Claims is not a cost center at Sola. It's the product." etc.
- TLDR Checklist bullet points: list of perks.
- "We're an Atlanta-based insurtech MGA. Today we sell standalone wind and hail parametric insurance to homeowners through independent agent partners."
- "The opportunity This is a builder role, plain and simple. You'll walk into a live parametric claims operation for our existing product and a TPA selection already underway for the new homeowners product, and from there you'll build a single unified claims function to serve both."
- Then bullet list of responsibilities (starting with "Build the operation" etc). Those are responsibilities.
- Then "Run it right" bullet list.
- Then "Be the voice of claims" bullet list.
- Then "What We're Looking For" bullet list (requirements/qualifications/skills).
- Then "What Makes This Role Different" paragraph.
- Then "Benefits" list: $190k-$240k + bonus + meaningful early-stage equity, 100% paid medical, dental, vision, catered lunch daily, 401(k), Paid parking, One Medical membership.
- Then "Compensation Range: $190K - $240K" (duplicate of benefits). We'll include in Pay maybe.
We need sections: About the role (intro + TLDR + maybe description of company). Responsibilities (the bullet lists under Build the operation, Run it right, Be the voice of claims). Requirements (What We're Looking For). Qualifications maybe overlapping; but we can combine Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About the role: intro paragraph, TLDR checklist, company description, opportunity description.
- Responsibilities: the bullet points under Build the operation, Run it right, Be the voice of claims.
- Requirements: maybe the "What We're Looking For" list (experience, etc). Could also include license requirement.
- Qualifications: maybe overlapping; but we could treat Requirements as experience, Qualifications as skills/knowledge? However we have a separate "Skills" heading possible. The "What We're Looking For" includes both experience and skills. Could split: Requirements = experience (10+ years, owned lifecycle, managed TPAs, built/scaled operation, CAT response, claims economics fluently, fraud indicators, player-coach, adjuster license). Qualifications = maybe MGA experience helps but not required, curiosity about parametric and indemnity, ability to reason from first principles. Skills = maybe knowledge of claims economics, fraud indicators, etc. But we can keep simple: Requirements = the bullet list; Qualifications = maybe not needed; Skills = maybe not needed; but we should only include sections with real content. If we include Qualifications and Skills but they'd be empty or filler, we must not include them. So we will include only sections we have substantive content for: About the role, Responsibilities, Requirements, Benefits, Pay (maybe). Schedule: not mentioned, so omit.
Pay: we have compensation range $190k-$240k + bonus + equity. That's pay. Benefits: we have list.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We must not repeat job title as heading.
Now format: Use for each section heading. Use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like EEO etc. Already removed.
We need to include the TLDR checklist as part of About the role maybe as a
.
Let's craft About the role content:
Paragraph: "Claims is not a cost center at Sola. It's the product." plus maybe the TLDR checklist as list.
Then: "We're an Atlanta-based insurtech MGA. Today we sell standalone wind and hail parametric insurance to homeowners through independent agent partners."
Then: "The opportunity This is a builder role, plain and simple. You'll walk into a live parametric claims operation for our existing product and a TPA selection already underway for the new homeowners product, and from there you'll build a single unified claims function to serve both."
We'll combine into paragraphs.
Now Responsibilities: we have three groups: Build the operation, Run it right, Be the voice of claims. Each group has bullet points. We'll combine all into a single maybe with subheadings? But we cannot add extra headings besides the specified ones. We could keep as a single list; that's fine.
List items:
- Own the full claims lifecycle end to end across both products: FNOL through payment, subrogation, and closure. You're accountable for cycle time, loss adjustment expense, leakage, litigation rate, and customer satisfaction across the whole book
- Bring our parametric and indemnity claims processes together into one experience, including how the two interact when a payout and an indemnity claim come from the same loss event
- Lead TPA selection for the new homeowners product end to end, from RFP through contract negotiation, then run that TPA like they're your own team: real SLAs, audits, file reviews
- Stand up internal FNOL from scratch, serving both products: staffing, scripts, escalation paths
- Own CAT response strategy for a book concentrated in wind and hail
- Decide what stays with the TPA and what comes in-house, and build that migration roadmap yourself
- Set the tone for customer-centric claims: fast, fair, and accurate communication at the worst moment of someone's year, and the judgment to know generous from undisciplined
- Operate inside our carrier delegated authority and know it cold. Protecting and growing that authority is one of the core measures of success in this role
- Build claims reserving practices from the ground up with our Head of Insurance
- Bring real claims technology into the mix: imagery, weather data, AI-assisted triage, fraud analytics
- Partner with underwriting and product on coverage language and loss trends
- Represent claims to carriers, reinsurers, and regulators, and own our DOI complaint responses and market conduct readiness
- Build the vendor panel beyond the TPA: engineers, defense counsel, mitigation and restoration partners
- Partner with legal on coverage disputes and litigated files
Now Requirements: from "What We're Looking For" list:
- 10+ years of property claims experience, with deep homeowners and wind/hail chops
- You've owned a claims lifecycle end to end, not just one piece of it
- You've managed or audited TPAs and actually moved the needle on their performance, and ideally you've run an RFP and negotiated the contract yourself
- You've built or scaled a claims operation before: workflows, guidelines, hiring, QA
- CAT response experience, ideally leading field response for wind/hail events
- You can talk claims economics fluently: LAE ratios, severity trends, cycle time drivers, leakage
- Working knowledge of fraud indicators and SIU practices, enough to know if the team investigating your files is any good
- You're comfortable as a player-coach at a startup. Write the playbook Monday, present to the board Wednesday
- MGA experience helps but isn't required. What matters more is genuine curiosity about how parametric and indemnity claims fit together, and the ability to reason from first principles about trigger design and basis risk
- You'll need an adjuster license across our operating states, or be willing to get one shortly after you start
We could split some into Requirements and Qualifications but we only have Requirements heading. We'll put all as list.
Now Benefits: list:
- $190k-$240k + bonus + meaningful early-stage equity
- 100% paid medical, dental, and vision for you, your spouse, and your children
- Catered lunch daily
- 401(k)
- Paid parking
- One Medical membership, so you've got a concierge doctor in your corner
Now Pay: maybe we just include compensation range again? But we already have compensation in Benefits. However Pay section could contain the salary range and bonus/equity. Since Benefits already includes that, we might avoid duplication. But instruction: include a section ONLY when the posting has real, specific content for it. Pay is present: compensation range. Benefits also present. We could keep both but ensure not duplicate same content. We could put Pay: "$190k-$240k base + bonus + meaningful early-stage equity". Benefits: other benefits (medical, dental, vision, catered lunch, 401(k), paid parking, One Medical). That splits.
Thus Pay section: base salary range + bonus + equity.
Benefits section: medical/dental/vision, catered lunch, 401(k), paid parking, One Medical membership.
Now Schedule: not mentioned, omit.
Now produce HTML.
We must not include or . Just fragment.
Let's craft.
Be careful to not include any markdown fences.
We'll output:
About the role
Claims is not a cost center at Sola. It's the product.
- In person. Nice West Midtown Atlanta office with skyline views + daily catering + snacks
- Startup environment. 23 employees, ground floor opportunity with equity.
- Hyper growth. 400%+ since May
- Flat structure. No layers upon layers of management. Work directly with leadership
- Long-term vision. This is the founder's life's work; we're building for decades
We're an Atlanta-based insurtech MGA. Today we sell standalone wind and hail parametric insurance to homeowners through independent agent partners.
The opportunity This is a builder role, plain and simple. You'll walk into a live parametric claims operation for our existing product and a TPA selection already underway for the new homeowners product, and from there you'll build a single unified claims function to serve both.
Responsibilities
- Own the full claims lifecycle end to end across both products: FNOL through payment, subrogation, and closure. You're accountable for cycle time, loss adjustment expense, leakage, litigation rate, and customer satisfaction across the whole book
- Bring our parametric and indemnity claims processes together into one experience, including how the two interact when a payout and an indemnity claim come from the same loss event
- Lead TPA selection for the new homeowners product end to end, from RFP through contract negotiation, then run that TPA like they're your own team: real SLAs, audits, file reviews
- Stand up internal FNOL from scratch, serving both products: staffing, scripts, escalation paths
- Own CAT response strategy for a book concentrated in wind and hail
- Decide what stays with the TPA and what comes in-house, and build that migration roadmap yourself
- Set the tone for customer-centric claims: fast, fair, and accurate communication at the worst moment of someone's year, and the judgment to know generous from undisciplined
- Operate inside our carrier delegated authority and know it cold. Protecting and growing that authority is one of the core
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like EEO etc. Already removed. We need to include the TLDR checklist as part of About the role maybe as a
- .
Let's craft About the role content:
Paragraph: "Claims is not a cost center at Sola. It's the product." plus maybe the TLDR checklist as list.
Then: "We're an Atlanta-based insurtech MGA. Today we sell standalone wind and hail parametric insurance to homeowners through independent agent partners."
Then: "The opportunity This is a builder role, plain and simple. You'll walk into a live parametric claims operation for our existing product and a TPA selection already underway for the new homeowners product, and from there you'll build a single unified claims function to serve both."
We'll combine into paragraphs.
Now Responsibilities: we have three groups: Build the operation, Run it right, Be the voice of claims. Each group has bullet points. We'll combine all into a single
- In person. Nice West Midtown Atlanta office with skyline views + daily catering + snacks
- Startup environment. 23 employees, ground floor opportunity with equity.
- Hyper growth. 400%+ since May
- Flat structure. No layers upon layers of management. Work directly with leadership
- Long-term vision. This is the founder's life's work; we're building for decades
- Own the full claims lifecycle end to end across both products: FNOL through payment, subrogation, and closure. You're accountable for cycle time, loss adjustment expense, leakage, litigation rate, and customer satisfaction across the whole book
- Bring our parametric and indemnity claims processes together into one experience, including how the two interact when a payout and an indemnity claim come from the same loss event
- Lead TPA selection for the new homeowners product end to end, from RFP through contract negotiation, then run that TPA like they're your own team: real SLAs, audits, file reviews
- Stand up internal FNOL from scratch, serving both products: staffing, scripts, escalation paths
- Own CAT response strategy for a book concentrated in wind and hail
- Decide what stays with the TPA and what comes in-house, and build that migration roadmap yourself
- Set the tone for customer-centric claims: fast, fair, and accurate communication at the worst moment of someone's year, and the judgment to know generous from undisciplined
- Operate inside our carrier delegated authority and know it cold. Protecting and growing that authority is one of the core
- maybe with subheadings? But we cannot add extra headings besides the specified ones. We could keep as a single list; that's fine.
List items:
- Own the full claims lifecycle end to end across both products: FNOL through payment, subrogation, and closure. You're accountable for cycle time, loss adjustment expense, leakage, litigation rate, and customer satisfaction across the whole book
- Bring our parametric and indemnity claims processes together into one experience, including how the two interact when a payout and an indemnity claim come from the same loss event
- Lead TPA selection for the new homeowners product end to end, from RFP through contract negotiation, then run that TPA like they're your own team: real SLAs, audits, file reviews
- Stand up internal FNOL from scratch, serving both products: staffing, scripts, escalation paths
- Own CAT response strategy for a book concentrated in wind and hail
- Decide what stays with the TPA and what comes in-house, and build that migration roadmap yourself
- Set the tone for customer-centric claims: fast, fair, and accurate communication at the worst moment of someone's year, and the judgment to know generous from undisciplined
- Operate inside our carrier delegated authority and know it cold. Protecting and growing that authority is one of the core measures of success in this role
- Build claims reserving practices from the ground up with our Head of Insurance
- Bring real claims technology into the mix: imagery, weather data, AI-assisted triage, fraud analytics
- Partner with underwriting and product on coverage language and loss trends
- Represent claims to carriers, reinsurers, and regulators, and own our DOI complaint responses and market conduct readiness
- Build the vendor panel beyond the TPA: engineers, defense counsel, mitigation and restoration partners
- Partner with legal on coverage disputes and litigated files
Now Requirements: from "What We're Looking For" list:
- 10+ years of property claims experience, with deep homeowners and wind/hail chops
- You've owned a claims lifecycle end to end, not just one piece of it
- You've managed or audited TPAs and actually moved the needle on their performance, and ideally you've run an RFP and negotiated the contract yourself
- You've built or scaled a claims operation before: workflows, guidelines, hiring, QA
- CAT response experience, ideally leading field response for wind/hail events
- You can talk claims economics fluently: LAE ratios, severity trends, cycle time drivers, leakage
- Working knowledge of fraud indicators and SIU practices, enough to know if the team investigating your files is any good
- You're comfortable as a player-coach at a startup. Write the playbook Monday, present to the board Wednesday
- MGA experience helps but isn't required. What matters more is genuine curiosity about how parametric and indemnity claims fit together, and the ability to reason from first principles about trigger design and basis risk
- You'll need an adjuster license across our operating states, or be willing to get one shortly after you start
We could split some into Requirements and Qualifications but we only have Requirements heading. We'll put all as list.
Now Benefits: list:
- $190k-$240k + bonus + meaningful early-stage equity
- 100% paid medical, dental, and vision for you, your spouse, and your children
- Catered lunch daily
- 401(k)
- Paid parking
- One Medical membership, so you've got a concierge doctor in your corner
Now Pay: maybe we just include compensation range again? But we already have compensation in Benefits. However Pay section could contain the salary range and bonus/equity. Since Benefits already includes that, we might avoid duplication. But instruction: include a section ONLY when the posting has real, specific content for it. Pay is present: compensation range. Benefits also present. We could keep both but ensure not duplicate same content. We could put Pay: "$190k-$240k base + bonus + meaningful early-stage equity". Benefits: other benefits (medical, dental, vision, catered lunch, 401(k), paid parking, One Medical). That splits.
Thus Pay section: base salary range + bonus + equity.
Benefits section: medical/dental/vision, catered lunch, 401(k), paid parking, One Medical membership.
Now Schedule: not mentioned, omit.
Now produce HTML.
We must not include or . Just fragment.
Let's craft.
Be careful to not include any markdown fences.
We'll output:
About the role
Claims is not a cost center at Sola. It's the product.
We're an Atlanta-based insurtech MGA. Today we sell standalone wind and hail parametric insurance to homeowners through independent agent partners.
The opportunity This is a builder role, plain and simple. You'll walk into a live parametric claims operation for our existing product and a TPA selection already underway for the new homeowners product, and from there you'll build a single unified claims function to serve both.