Technical Lead, Simulation

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 We are seeking a Technical Lead for Simulation to own the architecture of our simulation platform and the validation that gates autonomy releases. In this role, you will take simulation from log replay, to scenario suites running in continuous integration, to the pre-vehicle gates a release passes. This role will span across programs, and you will own the build-versus-buy decisions for the platform and the tooling around it. It's a hands-on role designing the simulation platform, setting the team's engineering practices, and hiring and mentoring new engineers. What you’ll do Platform architecture. Own the design of the simulation platform, including simulation clock and step control, run identity, determinism and reproducibility, batch execution, and log storage and indexing. Results must be reproducible and traceable to a software version. Log replay. Own the pipeline that converts recorded logs into replayable test cases, open-loop scoring of perception and localization against ground truth, and closed-loop replay. Scenario execution and coverage. Own the scenario schema and library, coverage definitions, and the structure of commit, nightly, regression, and release-validation suites. Release gating. Define what a release must pass before it reaches a bench, a proving ground, or a site. Own pass criteria, reporting, and the path from a failing scenario to a resolution. Build versus buy. Evaluate commercial simulation platforms against in-house development, make a recommendation with cost, lead time, coverage, and maintenance attached, and own the resulting vendor relationships and service levels. Simulation fidelity. Measure where simulation and vehicle behavior agree and where they…