Skip to content
Atoms

Field Test Engineer

San Francisco, CA; San FranciscoUnited States
Transport - Engineering
POSTED 14 SEPTVERIFIED 50M AGO
Apply Ask
Role
62 days opentrue age
Past the 35d median close
Posted 14 Sept · n=68
Pay
$135k–$200kno pay posted
Market p25–p75
$135k–$200k
SF Bay Area · n=100 · 365d to 15 Nov
CompanyAtoms →
346open roles
Opened · 30d
+69
Closed · 30d
−71
Signal
● Steady−2 net
15d of snapshots · 30d window
Market
3,006open · QA / Test
Opened · 7d
+29210% of open
All qa / test
5,591open
All tracked boards · live 16 Nov · n=3,006

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, what needed adaptation to run at all, and what no available venue can stage. A case definition nobody can execute is a defect in the definition, and you find it first.
  • Use AI tooling to remove the drudgery: first-draft procedures generated from case specifications, automated validity checking of runs against tolerance bands so invalid runs are caught at the track rather than in analysis a week later, and report drafting from acquisition data.

What we’re looking for

  • 5+ years hands-on vehicle test engineering, ADAS or AV testing, proving ground operations, or OEM and Tier 1 vehicle test. Time actually running tests, not planning them for other people.
  • Hands-on with the equipment: instrumented targets including soft cars and pedestrian and cyclist targets, driving robots, RTK or GNSS ground truth, timing synchronisation and data acquisition. Tell us what you have run, on what, and what went wrong with it.
  • Experience executing published test procedures, Euro NCAP or NHTSA crash-avoidance procedures or equivalent, and the judgment to see where a procedure written for a human-driven vehicle needs adaptation.
Source · AtomsFirst seen 2 NovOriginal ↗