The setting
is 's personal car insurance. Its price is set mainly from smartphone data on how a person drives, and the service also handles claims for damaged vehicles and injuries.
A displayed deductible and an issued policy promise different protection after accidents have already happened.
Broad amendments protect drivers with missing purchase evidence, while narrower amendments protect the priced exposure.
Who you’d be doing this for
“The repair shop asked for a thousand dollars today. I saved the screen because it said five hundred.”
Jiri Krejci · Policyholder with a recently reported collision · a character in this brief
Purchased through the affected integration and budgeted for the deductible displayed at purchase.
What is at stake
620 drivers bought policies with conflicting deductibles, and some have already reported accidents. You must weigh broader coverage commitments against excluding drivers whose purchase evidence is missing.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- purchase expectations vs priced coverage
- equal treatment vs individual evidence
- immediate repair decisions vs uncertain exposure
- distribution continuity vs coverage consistency
Why Root Insurance
Embedded purchases connect partner screens, Pricing Platform System, policy records, and claims decisions that must describe the same coverage.
Written with these in mind
Not your kind of problem? 15 more at Root Insurance, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Root Insurance. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Staff Product Manager, Pricing (opens in a new tab)
- Pricing is one of Root’s core strategic advantages, and this role will shape the systems that determine how quickly we turn data and models into market-leading pricing decisions.
- Partner closely with Engineering, Data Science, and Actuarial to identify platform needs, prioritize investments, and define a roadmap that reduces friction from data readiness through model development, deployment, diagnostics, and monitoring
- Product Manager II, Policyholder Platform & Experience · no longer posted
- Fast learner in complex domains: You can quickly build a mental model of new systems, teams, and constraints, and start contributing meaningfully in a short amount of time.
- Your job is not just to “move work forward,” but to create clarity, make decisions, and drive outcomes in areas where ambiguity and dependencies would otherwise slow the team down.
- Product Manager, Partnerships · no longer posted
- As the Product Manager for Partnerships, you will drive execution across our embedded and distribution partnerships by translating business opportunities into clear, build-ready product work.
- Requirements-driven: You turn ambiguous partner asks into structured requirements, define multiple viable solution options, and clearly articulate tradeoffs to drive decisions internally.
- Manager II, Product Management · no longer posted
- This is a high-leverage role for a hands-on product leader who knows how to drive clarity and ship fast.
- Product Manager II, Underwriting · no longer posted
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on committing to a deal before it checks out.
Lapses rose 15% after payment records became inconsistent with policy records.
You have to weigh timely guidance against the risk of telling a policyholder something the carrier data cannot yet prove.
The same setting, from another role
Each is set around Root Insurance’s Root Auto Insurance, written for a different role. They’re separate briefs, not the same scenario.
Drivers entering through comparison sites are seeing quote explanations change between an agent and the direct flow.
You must weigh partner speed against disclosures that remain clear across state rules.
Payment and settlement records conflict across 60 closed bodily injury files.
You must weigh settlement finality against the risk that claimants or regulators find an unresolved payment first.
Washington claimants who dispute virtual valuations are missing documented inspection decisions within five business days.
You have to weigh a clear compliance trigger against keeping routine repair claims moving.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make an ambitious commitment financially and operationally sound enough to hold up under later scrutiny.
Two weeks before the committed control date, 14% of export events in scope cannot be classified either way.
You have to weigh broken analytics against the promise you made to a regulator and a customer.
A signed contract exposes up to $4.8M in annual service credits, and the reserve is due before the customer goes live.
You weigh machine-generated evidence against a wider scenario range, and the terms hold for the year.
Fourteen of 180 reviewed benefit-change contacts did not match the current eligibility record.
You have to weigh a four-week go-live against an architecture that cannot cheaply be reversed.
