Staff Infrastructure Engineer, Robotic Systems

About The Role:

What You’ll Do:

• Own the build system for a 40-package monorepo that targets three architectures: hermetic builds, honest lockfiles, change detection, and a shared remote cache keyed on real inputs.


• Own CI/CD end to end, including rollback. Measure push-to-green, queue depth, and fetch error rate. Drive the numbers down and show the result.


• Design and operate the fleet deployment path: immutable artifacts, staged rollout, version handshake, drift detection, and an abort path that does not depend on the deploy script.


• Define the production signals and thresholds for pipeline health, and the runbook an on-call engineer can run without you. Turn runbook steps into pipeline checks and auto-remediation where it pays back.


• Own build-runner security as a blast-radius problem: short-lived credentials, scoped IAM, rotation as a mechanism, secret scanning in CI.


• Work with IT on the GitLab, network, and identity boundaries. Ask where the boundary is instead of assuming it.


• Remove toil with a number attached: what engineers did by hand before, how often, and what they do by hand now.


• Drive adoption across teams that do not report to you. Make the new way the default and the old way slower.


• Raise reliability standards without blocking delivery. Encode what you learn from incidents into systems, not reminders.

What You’ll Need:

• Ownership of a build system for a repository with many packages and more than one build target, including what was wrong with it and what you changed.


• Ownership of a CI/CD system end to end, including rollback, with an opinion on what made deployments safer over time.


• Deep fundamentals in build reproducibility and caching: why a test passes locally and fails in CI, what belongs in a cache key, and how a correct key can still serve a wrong artifact.


• Deep fundamentals in fleet deployment: why mutable tags cause drift, how to deploy by digest, and how a node that has been offline rejoins production safely.


• Experience designing failure paths that are concrete: what times out, what safe state is left behind, and what the next engineer sees.


• A record of production incidents you diagnosed to root cause, with a mechanism, a measurement, and a fix.


• A record of getting other engineers to adopt infrastructure you built, and the lever you used.


• Candor about what you are not good at, and ownership of outcomes, including the ones that went wrong.


• Fluency with AI tools in your daily engineering work, while owning the decisions, code, and results you accept.


• Ability to work onsite five days per week

Bonus Points For:

• 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 a growth phase from tens to thousands of endpoints.