The completed-trip history must become one record without rewriting rider outcomes incorrectly.
Analytics needs continuity across the retiring event contract, while data science needs historical records it can trust.
Who you’d be doing this for
“My ride ended hours ago, and now I’m being asked why it’s missing from my history.”
Slawomir Ionescu · Rideshare Passenger
A frequent rider whose completed trips feed the histories used to assess request, match, and trip outcomes.
What is at stake
Two trip histories disagree while the old event contract has five days left. You must weigh a durable canonical record against the risk of permanently rewriting uncertain history.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- event retirement vs historical completeness
- metric continuity vs canonical truth
- model stability vs data correction
- producer reliability vs downstream migration
Why Lyft
The rider app depends on completed-trip history to measure whether ride requests turn into finished trips.
Written with these in mind
Not your kind of problem? 66 more at Lyft, or browse every organization.
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.