Functional Safety

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.

About the role

This role owns the functional safety analysis of our automated vehicle platform and its sensor suite: what can fail, how it manifests, what the system does about it, and whether that response is good enough. You will do the analysis yourself, and your assessment informs releases.

It also owns something that often goes unowned — determining the safety impact of change. We move constantly, and someone has to be able to say quickly and credibly what a given change does to the safety argument. That is this role.

The third part is leverage. The safety case engineers work from your method: the analysis structures they adapt to their own scope, the library of platform-level safety items they reference instead of re-deriving, and the traceability they query. The job is not finished when your analysis is correct — it is finished when the method is executable by someone who is not you.

What you’ll do

• Own hazard analysis and risk assessment for the platform — derive safety goals and requirements, drive them into the architecture, and maintain the traceability from hazard to requirement to verification evidence.
• Lead fault and failure analysis across the platform — compute, power and actuation interfaces — and across the sensor suite, covering both hard faults and degraded modes.
• Own sensor suite safety: sensing sufficiency and degradation — what coverage exists, how it erodes under adverse conditions, and how faults are detected and handled.