Infrastructure Engineer

Foundry Robotics•San Francisco, CA

65d•Onsite

About The Position

Foundry Robotics is building an AI-native robotics manufacturing company focused on deploying advanced assembly and production capability for leading robotics companies and national-security-critical hardware. Basically, we’re building robots that build robots. Factory OS is building software that runs factories. Our platform spans cloud backends, on-prem services, and edge devices deployed on the factory floor. The operators, supervisors, and managers who use our tools need interfaces that are fast, reliable, and intuitive—even when network conditions aren’t perfect and the environment is demanding. The Role You will work on the infrastructure that our services, our factory-floor software, and our ML training run on: AWS, Kubernetes, the network boundary between them, the deployment pipeline, GPU workload scheduling, and the monitoring that tells us when something is wrong. This is a unique position with huge scope, spanning traditional containerized software platforms, as well as robotics, networking and AI infrastructure. Unlike an internet company, you will work on capabilities that support real hardware, and unlike traditional robotics, this platform also orchestrates the manufacturing process and the continued operation of the robots themselves. It is a small team with a lot of surface area. Expect to move between infrastructure as code, cluster operations, GPU scheduling, and edge-device support in the same week.

Requirements

3+ years running production infrastructure with hands-on Kubernetes.
Fluent in Terraform and GitOps.
Worked in infrastructure CI/CD where merge means apply and know how to make that safe.
Solid networking fundamentals: VPCs, routing, VPN, DNS, TLS, overlay networks, and the ability to debug a routing problem with a packet capture.
Comfortable in Go or Python for tooling and glue, and able to read production service code well enough to debug it.
Experience operating an observability stack and a track record of making alerts trustworthy.
Security-minded by default: least-privilege access, no public endpoints, secrets from config, and the reflexes to catch a committed credential.

Nice To Haves

Experience running Kubernetes on-prem.
Edge or fleet experience: arm64 Linux devices, over-the-air rollout, offline-tolerant design.
WireGuard-based overlay networks at organization scale.
Time spent near robots or industrial hardware.
Experience in an ITAR or CMMC environment.

Responsibilities

Work on the infrastructure that our services, our factory-floor software, and our ML training run on: AWS, Kubernetes, the network boundary between them, the deployment pipeline, GPU workload scheduling, and the monitoring that tells us when something is wrong.
Move between infrastructure as code, cluster operations, GPU scheduling, and edge-device support in the same week.