Safety Case Engineer

7+ years across functional safety, autonomy behaviour and fleet operations, with real hands-on depth in at least two and working fluency in the third. We will test all three; specialists in one who intend to learn the rest on the job are not a fit for these seats.

You have authored a structured safety argument, not reviewed one — GSN or an equivalent claim-argument-evidence structure, on a real system, defended to someone who pushed back hard. Be ready to walk through one you wrote and the parts you would now write differently.

Demonstrated hazard analysis ownership (HARA, FMEA, FTA or equivalent) and demonstrated scenario-based validation ownership. The combination is the requirement, not either half.

Rigour about provenance. You instinctively distinguish a measurement from an estimate from a placeholder, and label them as such rather than letting a number acquire authority by being written down.

The willingness to speak up. Some of this will be commercially inconvenient to leave unsigned, and we need people who can say an argument is not ready, say exactly what would make it ready, and what are the consequences not.

Standards fluency across ISO 26262, ISO 21448 (SOTIF), UL 4600, and SAE J3016, with the judgment to apply them proportionately to a scoped argument rather than reproducing a full-program process at small scale.

Comfort with the statistics of exposure, rare events and coverage, and with surrogate safety measures and their limits. A kinematic proximity metric measures proximity dynamics and not harm, and should never carry a claim alone.

Programming ability in Python or similar, sufficient to work with fleet data, build your own tooling and work fluently with an AI coding assistant — with the boundary held firmly: a generated hazard list is a hypothesis to verify, and a generated argument map is a draft, never a signed argument.

Exceptional written precision. More than any other role on this team the deliverable is a document that has to stand up without you in the room; vague writing here is not a style problem, it is a safety problem.

The disposition three interchangeable seats need: focused enough to go deep on what you own, flexible enough to pick up a colleague's, and generous enough to make peer review genuinely useful rather than ceremonial.

At Atoms, you’ll work on one of the defining challenges of our time—bringing automation into the physical world to drive real, lasting impact. We exist to uncover valuable unknown truths and turn them into progress, which means constantly pushing beyond what’s known and building what doesn’t yet exist. The work is ambitious and often challenging, but it’s grounded in a shared sense of purpose and a team committed to seeing it through together. Our work only matters if it serves others, and we know that meaningful progress depends on the trust of the people we serve and the strength of our team—so we invest in both, creating an environment where you can do your best work and grow.

This role is based in our San Francisco office. Atoms is a company driven by invention and continuous change - we are constantly reimagining our industries, building new products, and refining how we operate. We do our best work together. That’s why all of our office-based teams work onsite, five days a week.

The base salary range for this role is $149,000 - $188,000 per year.

Actual compensation will be determined on an individual basis and may vary depending on experience, skills, and qualifications.

Base salary is just one part of your total rewards package. You may also be eligible for equity awards.

#LI-Onsite