The emergency fallback must protect road users without turning clear routes into remote-assistance events.
Late safe-stop behavior threatens responder safety, while earlier intervention consumes the operational capacity needed for driverless service.
Who you’d be doing this for
“I need to tell the operator what happens near a fire truck, not send them three traces that disagree.”
Hanne Lund · Autonomy Program Manager
Owns launch readiness for a fleet operator integrating the driverless system into its first service market.
What is at stake
Some emergency-scene cases enter safe-stop too late, while others create avoidable remote-assistance calls. You must weigh responder safety against a fallback behavior that could constrain planned driverless operations.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- responder safety vs. driverless availability
- simulation evidence vs. vehicle telemetry
- earlier fallback vs. remote-assistance capacity
- release timing vs. irreversible onboard change
Why Nuro
Nuro Driver depends on onboard autonomy behavior that can safely handle emergency scenes across vehicle platforms before commercial robotaxi deployment.
Written with these in mind
Not your kind of problem? 26 more at Nuro, 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.