The fastest explanation for a rider failure is not always the one engineers can trust.
On-call needs a shorter path to a cause, while engineers still need evidence strong enough to justify a production fix.
Who you’d be doing this for
“My driver was supposed to be on the way, then the app just stopped updating while I was outside.”
Selorm Camara · Rideshare Passenger
A rider trying to request and track an on-demand trip through the rider app.
What is at stake
Rider-app failures keep reaching on-call without a clear chain back to their cause. You must weigh faster investigation against evidence an engineer can trust before shipping a fix.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster diagnosis vs. evidence engineers can verify
- ranked AI causes vs. human release accountability
- reusable traces vs. bounded service access
- on-call speed vs. operational reliability
Why Lyft
Rider-app request and pickup flows depend on backend services that must stay reliable while riders are arranging time-sensitive 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.