Skip to content
Atoms

Senior Program Manager, Vehicle Configuration

San Francisco, CA; San FranciscoUnited States
Senior · Transport - Engineering
POSTED 1 SEPTVERIFIED 7M AGO
Apply Ask
Role
75 days opentrue age
Past the 35d median close
Posted 1 Sept · n=67
Pay
$206k–$208kno pay posted
$181k$226k
Market p25–p75
$181k–$226k
Atoms p25–p75
$206k–$208kn=6
SF Bay Area · n=1228 · 365d to 15 Nov
CompanyAtoms →
346open roles
Opened · 30d
+68
Closed · 30d
−70
Signal
● Steady−2 net
14d of snapshots · 30d window
Market
17,075open · Senior Software engineering
Opened · 7d
+1,4238% of open
All software engineering
75,284open
All tracked boards · live 15 Nov · n=17,075

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 Senior Program Manager to own vehicle configuration and change control: the record of what hardware and software is on every R&D vehicle we operate, and the process governing how it changes. In this role, you will define the configuration data model, the capture path that keeps the record accurate against development assets, and the change processes that enable us to test quickly and effectively. The role spans multiple vehicle platforms with different hardware, compute, and software, and requires regular time in the garage and around vehicles.

What you’ll do

  • Configuration System of Record: Own the record of as-designed, as-built, and as-running configuration for every platform, covering hardware revision and serialization, harness and sensor set, compute generation, calibration state, and firmware and software versions. Define the configuration data model, including item and revision structure, effectivity rules, and the platform abstractions that hold across differing vehicle types.
  • Configuration Capture: Define how configuration data is captured at the point of work, so that build, modification, service, and software update events update the record through the tools technicians and engineers already use. Own record accuracy as a measured metric, including the audit methods used, and the cadence at which it runs.
  • Release and Campaign Eligibility: Establish how we determine which properties are eligible for a given software release, test campaign, or data collection mission, and the reason any vehicle is excluded.
  • Configuration and Data Provenance: Define how logged data and test results are tied to the configuration that produced them. Partner with software and data teams on how provenance is used in validation and training workflows.
  • Enterprise System Requirements: Define configuration requirements for PLM, ERP, MES, and inventory systems, own the integration design between those systems and the configuration record.
  • Cross-Functional Ownership: Partner with vehicle integration, manufacturing and technician teams, autonomy and software release, safety, supply chain, and operations, and resolve conflicting requirements across them.

What we’re looking for

  • Bachelor's degree in engineering, computer science, or a related technical field is required, with 6+ years in technical program management, technical product management, engineering program management, or a comparable role. Equivalent hands-on experience will be considered in place of the degree.
  • Demonstrated ownership of a technical program or internal system end to end, from requirements through delivery and sustained adoption by users who were not required to use it.
  • Experience in environments where physical asset state and software state must be kept reconciled, in autonomous vehicles, automotive, EV, robotics, or aerospace.
Source · AtomsFirst seen 2 NovOriginal ↗