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.
Saved vehicle changes preserve customer effort but retain yesterday's pricing version.
Refreshing a draft protects premium consistency, while preserving its contents avoids another round of vehicle entry.
Who you’d be doing this for
“I came back with the VIN, and the price changed on the last screen. Now I'm checking every answer again.”
Miroslav Pokorny · Policyholder adding a second vehicle · a character in this brief
Saved a vehicle addition while finding the vehicle identification number, then returned after a pricing update.
What is at stake
Eighteen policyholders saw different premiums while resuming a vehicle addition yesterday. You weigh preserving their saved details against the simpler option of restarting every affected draft.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- saved customer effort vs simpler platform behavior
- narrow refresh logic vs broader invalidation
- premium clarity vs an uninterrupted confirmation flow
Why Root Insurance
Pricing Platform System publishes the pricing configuration that customer-facing vehicle changes must reflect at confirmation.
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)
- You will work closely with researchers on problems including feature pipelines and feature stores, reproducible model training and orchestration, model registries and versioning, automated validation, model serving, production observability, and tooling that ensures consistency between research and production.
- You will also explore how emerging LLM technology can revolutionize the data science workflow, improving the way models are developed, tested, deployed, and maintained, with the goal of dramatically reducing the time and effort required to turn new research into production pricing models.
- Product Manager II, Policyholder Platform & Experience · no longer posted
- 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
- Detail-obsessed: You catch gaps in logic, misaligned assumptions, and unclear handoffs before they become production issues.
- 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
- Analytical & data-native: You use data to drive decisions, test hypotheses, and calibrate strategy.
- 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.
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.