The setting
is a transportation platform that connects riders with rideshare, bikes, scooters and other ways to get around. gives the drivers who provide those rides tools for earnings, payments, safety and support.
An earlier question could make an appeal reviewable or make it harder to submit.
Reviewers need specific context, while drivers need room to explain events without being steered toward an expected answer.
Who you’d be doing this for
“I wrote everything out last night, and this morning they asked which trip I meant.”
Mawuli Adeyemi · Rideshare driver · a character in this brief
Has submitted an account appeal and is waiting for a reviewer to assess it.
What is at stake
Drivers needed another exchange in 82 of 240 sampled account appeals. You weigh useful questions before submission against extra friction and answers shaped by the model.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- useful context vs submission friction
- tailored questions vs consistent requirements
- historical labels vs reviewer bias
- specific prompts vs unsteered answers
Why Lyft
LangGraph support flows already connect drivers to help, but an account appeal must preserve the driver's own account rather than optimize for a quick resolution.
Written with these in mind
Not your kind of problem? 76 more at Lyft, 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 Lyft. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Machine Learning Engineer, Safety and Customer Care AI (opens in a new tab)
- As a Machine Learning Engineer on the SCC team, you will fine-tune and align models and build AI Agents that power how riders and drivers get help.
- Turn interaction feedback into training data and learning signals, closing the data flywheel that continuously improves the models.
- Data Scientist - Algorithms, Mapping (opens in a new tab)
- Drive scientific excellence by introducing modern techniques in ML, optimization, reinforcement learning, or graph-based methods to unlock new product capabilities
- Own the complete lifecycle of algorithmic solutions from problem formulation, data exploration, and feature engineering to deployment, monitoring, and iteration
- Senior Software Engineer, Forecasting & Real-Time Optimization (opens in a new tab)
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.
Similar problems at other organizations
Like this one, each of these turns on deciding on evidence that's still thin.
Similar reporting requests are spending five business days in clarification because their definitions and sources are unclear.
You decide where the AI's trace from a request's wording to a metric definition and dbt model stops and an engineer's confirmation of that definition takes over.
Engineers keep rebuilding the same deployment, trace and feature-flag context each time a rule-matching failure comes back.
You have to decide at which step the AI's brief ends and an engineer's own reading of the traces and flag history begins.
Renewal analysis links telematics-driven premium changes to higher lapse among price-sensitive policyholders.
You must weigh a useful retention signal against the risk of acting on an unproven prediction.
The same setting, from another role
Each is set around Lyft’s Lyft for Drivers, written for a different role. They’re separate briefs, not the same scenario.
Airport wait-time guidance is staying stale after airport communication changes, sending drivers into queues that no longer match the app.
You must decide what the system can rank automatically and what engineers must verify before acting.
Drivers are opening completed trips and still contacting support to ask what changed their pay.
You have to weigh a useful explanation against the stability and confidentiality of earnings configurations.
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.