Field Test 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 Plan and run scenario cases at proving grounds: translate a case specification into a test procedure, set up instrumented targets and VUT’s, define approach conditions and tolerance bands, and execute enough valid runs to support a result. Run scenario cases on public roads with safety drivers, route and condition selection to actually encounter the target scenario, in-vehicle protocol, driver briefing, abort criteria, and disciplined recording of what occurred. Keep staged and opportunistic encounters clearly distinct, because they are not the same evidence. Own the risk assessment for the testing itself: site layout, personnel positions, exclusion zones, emergency stop provisions, weather and surface limits, and the conditions under which a test does not run. You hold the call to stop, and we expect you to use it. Own instrumentation and ground truth - ego positioning, target position and velocity, timing synchronisation, video and data acquisition. A run that cannot be reconstructed from its data did not produce evidence. Own tolerance bands, the number of valid runs a result requires, and the rejection of runs that fall outside them, with the reason recorded. Nobody downstream can audit this if you do not. Write test reports a safety case engineer can cite directly: what was run, under what conditions, against what criteria, with what outcome, and every deviation from the procedure. Write for someone who was not there and will be asked to defend the conclusion. Own proving ground scheduling, test equipment and its calibration, and third-party test service relationships, including the practical knowledge of what each venue can and cannot stage. Report what is not testable as specified,…