The completed-trip table is counting some finished rides twice.
Daily reporting needs a fast correction, while downstream consumers need the trip lineage to remain stable.
Who you’d be doing this for
“I took one ride home, but the receipt history looked like I’d been charged twice.”
Chitra Choudhury · Rideshare Passenger
A rider whose completed trip contributes to the data used to understand whether the app reliably gets people where they need to go.
What is at stake
A completed-trip table is counting 3.1% of a subset of rides twice. You have to restore accurate counts without breaking the downstream tables that rely on the same pipeline.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- daily reporting speed vs durable source correction
- event contract stability vs duplicate prevention
- feature continuity vs historical accuracy
Why Lyft
The rider app depends on completed-trip data to measure whether requests become rides and to supply reliable inputs for marketplace decisions.
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.