A safety model is acting on sensor data whose meaning changed after the app release.
Pausing risk features protects drivers from incorrect account review, while continuing them preserves coverage for genuine harsh driving.
Who you’d be doing this for
“I got flagged after a normal airport run, and now I’m worried every trip is counting against me.”
Sami Younis · Rideshare Driver
A driver whose ability to keep accepting trips is affected by safety notifications and account review.
What is at stake
Safety notifications are flagging ordinary trips after an app release changed incoming sensor signals. You must weigh immediate protection for drivers against losing coverage for genuinely unsafe driving.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- driver due process vs. safety coverage
- rapid containment vs. verified recalibration
- model output scale vs. human review capacity
- current sensor data vs. trusted historical behavior
Why Lyft
Driver safety notifications and account reviews depend on risk features produced from the mobile sensor signals behind trip execution.
Written with these in mind
Not your kind of problem? 70 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.