Staff Developer Experience Engineer

Atoms•San Francisco, CA

5d•$224,000 - $275,000•Onsite

About The Position

Atoms is seeking a foundational Developer Experience Engineer to build scalable developer infrastructure powering their autonomous transport initiative. This role involves optimizing developer workflows across large-scale C++, Python, Go, Rust, and embedded firmware codebases. The engineer will focus on eliminating build friction, preventing dependency issues, and architecting secure Over-The-Air (OTA) update mechanisms for the edge vehicle fleet. The goal is to empower robotics, ML, and software teams with high-speed, reliable tooling to accelerate the delivery of safe, on-road autonomous transportation.

Requirements

8+ years of professional experience in Developer Experience, Build Engineering, or Infrastructure, specifically supporting large-scale engineering organizations.
Strong programming proficiency in Python, C++, Go, or similar.
Deep knowledge of modern build systems and package managers (e.g., Bazel, CMake, UV).
Hands-on experience scaling CI/CD systems, monorepo architectures, and automated testing pipelines for complex codebases.
Familiarity with embedded systems, firmware builds, or containerized IoT operating systems (such as Balena Linux or Yocto).
Foundational understanding of designing secure, fail-safe Over-The-Air (OTA) deployment pipelines for edge hardware or robotics.
Proven ability to reduce build/test cycle times, eliminate flaky tests, and untangle complex dependency graphs.
Exceptional communication skills and a passion for acting as an empathetic force multiplier for cross-functional software, hardware, and robotics teams.

Responsibilities

Own the build pipelines for Transport's repos, ensuring they are fast enough to minimize engineer context-switching.
Optimize build systems to reduce build times and ensure reproducibility, managing the build graph, caching, and dependency management.
Automate the building and testing of embedded firmware and the vehicle OS.
Design and build over-the-air updates for vehicles in the field, including staged rollouts, redundancy, and rollback mechanisms.
Determine repository architecture (monorepo vs. multi-repo), artifact versioning, storage, and dependency tracking.
Integrate Hardware-in-the-Loop (HIL) rigs and simulation into release validation to catch regressions before they reach vehicles.
Track build health, test flakiness, and time-to-deploy, fostering a data-informed culture to identify and fix problems.