Complex day at Samsara

Choose warnings drivers will carry for two weeks without updates

Published Nov 8, 2026

You’re the ai / ml engineer. Your team is in the room.

The setting

's combines devices and software to monitor safety in physical operations. Its dash cams, gateways, and sensors run AI that detects distracted driving and helps prevent collisions as they happen.

Today's firmware image commits disconnected drivers to two weeks of collision-warning behavior.

Additional dangerous approaches caught come with ordinary turns that sound urgent.

Who you’d be doing this for

“A driver called after his third warning on the same gravel bend. Tomorrow he's gone for two weeks, and he asked whether to trust the next one.”

Haruto Lim · Fleet Safety Manager · a character in this brief

Oversees drivers leaving connected depots for the 14-day routes and reviews their safety events after uploads arrive.

What is at stake

Tomorrow, 1,200 vehicles leave with collision warnings that cannot reliably change for 14 days. You must weigh additional hazards caught against nuisance warnings using evidence that cannot all be independently checked before departure.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • additional hazards caught vs driver attention spent
  • rare-event coverage vs confidence in sampled labels
  • warning timing vs constrained inference
  • known incumbent misses vs uncertain candidate behavior

Why Samsara

Collision warnings run on constrained dash cameras, so fleet connectivity and device memory limit how quickly a model decision can be reversed.

Written with these in mind

Edge ML engineersSafety-focused applied scientistsProduction ML engineers

Not your kind of problem? 43 more at Samsara, 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 Samsara. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Manager, Firmware Engineering (opens in a new tab)
    • These models detect distracted driving, prevent collisions, and keep workers safe, all in real time on constrained hardware.
    • Your work directly affects whether a driver gets a warning before a collision, not after.
  • Senior Manager, Safety AI (opens in a new tab)
    • Lead the transition from individual model deployments to a coherent, system-level platform — one that fuses camera, IMU, GPS, and vehicle telemetry data to detect, interpret, and surface safety events with high precision and low latency.
    • Own the technical direction for Samsara's on-device and cloud safety AI systems — making architectural decisions about what runs on constrained edge hardware vs. cloud, how models are packaged and deployed across more than 2M dashcams, and how the data flywheel is built to drive continuous improvement.
  • Staff Machine Learning Engineer - Edge AI (opens in a new tab)
    • You will work closely with ML Engineers and Scientists, as well as full-stack and firmware engineers to deliver core product features, services, and optimizations.
    • Partner across business units to explore and prototype new AI experiences and optimize the ML model performance on edge devices.

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.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on crossing a deadline that can't be undone.

The same setting, from another role

Each is set around Samsara’s Worker Safety, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to engineer security-critical controls whose correctness holds up even when carefully examined by skeptics.