Staff Infrastructure Engineer, Robotic Systems

Atomic Machines•Santa Clara, CA

1d•$180,000 - $230,000•Onsite

About The Position

Atomic Machines is hiring a Staff Infrastructure Engineer to own the infrastructure that builds, releases, and deploys software to the Matter Compiler fleet of nodes controlling real-world equipment. The role spans a 40-package, multi-architecture monorepo build system; end-to-end CI/CD; artifact storage and shared caching; and deployment to roughly 80 nodes today, with a planned expansion to thousands of devices across several metro areas by 2027. The engineer will design, build, operate, and improve this infrastructure; set automation and manual-operation boundaries; limit the blast radius of bad builds; establish early-warning signals for CI health; and drive adoption across teams. The role calls for decomposing ambiguous system failures, reasoning across abstraction layers, and owning problems that cross team and organizational boundaries. Hardware experience is not required. The position requires working onsite five days per week. Compensation includes equity and benefits.

Requirements

Ownership of a build system for a repository with many packages and more than one build target, including experience identifying and changing what was wrong with it.
Ownership of an end-to-end CI/CD system, including rollback, and an informed perspective on how deployments became safer.
Deep understanding of build reproducibility and caching, including local-versus-CI test differences, cache-key design, and cases where a correct key can still serve a wrong artifact.
Deep understanding of fleet deployment, including risks of mutable tags, deployment by digest, and safe rejoining of offline nodes.
Experience designing concrete failure paths, including timeouts, safe resulting states, and what information the next engineer sees.
A record of diagnosing production incidents to root cause and implementing a mechanism, measurement, and fix.
A record of getting other engineers to adopt built infrastructure and knowing which adoption levers were used.
Candor about areas of weakness and ownership of outcomes, including failures.
Fluency with AI tools in daily engineering work, while taking ownership of decisions, code, and accepted results.
Ability to work onsite five days per week.

Nice To Haves

Experience deploying software to distributed nodes that control physical equipment.
Experience with GitLab CI, Ansible, OIDC/STS-based credential flows, and artifact stores at scale.
Experience operating infrastructure through growth from tens to thousands of endpoints.

Responsibilities

Own the build system for a 40-package monorepo targeting three architectures, including hermetic builds, lockfiles, change detection, and a shared remote cache keyed on real inputs.
Own CI/CD end to end, including rollback; measure push-to-green time, queue depth, and fetch error rate, and improve those measures.
Design and operate the fleet deployment path, including immutable artifacts, staged rollouts, version handshakes, drift detection, and an abort path independent of the deploy script.
Define production signals and thresholds for pipeline health, and create runbooks that on-call engineers can use independently.
Turn runbook steps into pipeline checks and automated remediation where worthwhile.
Own build-runner security as a blast-radius problem, using short-lived credentials, scoped IAM, credential rotation, and CI secret scanning.
Work with IT on GitLab, network, and identity boundaries.
Measure toil and reduce it, documenting what engineers did manually before and after changes and how often.
Drive adoption of infrastructure across teams that do not report to the role, making the new approach the default.
Improve reliability standards without blocking delivery, and encode incident learnings into systems.
Diagnose production incidents to root cause and implement mechanisms, measurements, and fixes.
Use AI tools in daily engineering work while owning accepted decisions, code, and results.