Safety Case Engineer

Who we are Atoms is building the machines that power the next era of progress. Over the last decade, software has transformed the digital world. But the physical world, where food is made, minerals are mined, goods are moved, and industries are run, remains far less intelligent, far less efficient, and far more constrained. We’re changing that. Atoms builds Physical AI— real-world robots for the industries that move civilization forward, starting with food, mining, and transport. Our systems are designed to understand, predict, and control the real world with precision, turning complex physical operations into something more reliable, more scalable, and more productive. This work requires more than robotics. It requires deep integration across hardware, software, AI, operations, manufacturing, and real estate. We don’t just build machines in a lab. We deploy them into real environments, operate them, learn from them, and improve them until they work at scale. We are roboticists, engineers, operators, and builders. We believe the next great technology companies will not only transform information, but the physical systems that shape everyday life. If you want to work on hard problems with real-world impact, join us. What you’ll do Own a defined scope of the safety case end to end, from first draft to signed, including its upkeep afterward when something it depends on is revised. Author of record means the argument is yours to defend. Define what your argument covers and what it explicitly does not: the conditions it assumes, the exclusions and why they hold, and the hazards that cannot arise within the scope. Judge evidence sufficiency: how much operating experience there is and how it was counted, coverage against each case, and where the evidence came from. Working closely with the functional safety, scenario validation and fleet operations leads to obtaining the evidence. Write the claim-argument-evidence map. So it's clear when it holds and when it doesn't. Convene review when the work is ready and not before, carry reviewer comments to documented resolution, and serve as independent reviewer on scopes you do not own. Be a demanding customer of the shared method and tooling built by the functional safety, scenario validation and fleet operations leads. When a rule is missing or ambiguous, or a tool makes the wrong thing easy, say so loudly — a local workaround does not stay local. Use AI tooling as part of the work: drafting from a template, generating and stress-testing candidate hazard sets, cross-checking coverage against the scenario library, tracing hazard to test to evidence, and finding where an upstream revision has invalidated something already written. What we’re looking for 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…