The company is a Series A startup with over $37M in funding and 9-figure revenue. It builds an Agent Cloud and the infrastructure behind AI labs and widely used consumer and enterprise agents.
The team includes original authors of Firecracker, the AWS microVM technology behind Lambda, plus alumni of Cognition, JetBrains, Zapier and Wish.
The company has started billions of Firecracker sandboxes across Google Cloud, AWS and Azure regions for customers whose products stop when those sandboxes stop. Its hardest incident fixes land in code rather than configuration.
You will define what healthy means for the platform, build the observability and automation that keep it healthy, and make new capabilities run reliably in production. You will work with the infrastructure and systems engineers who build the platform, and with the sandbox team in Prague.
Responsibilities
Define SLOs and error budgets for core paths such as sandbox start, resume and connect, and use them to drive alerting, releases and priorities
Build observability and alerting that shows platform problems before customers notice them
Take new platform capabilities from first release to reliable production operation
Automate operational work, from release checks to routine fleet operations
Build security and trust layers the platform depends on, such as service-to-service mutual TLS
Make private cloud and enterprise deployments as reliable as the company's own regions
Lead incident response and improve handling so a class of failure does not recur
Take part in on-call and help shape the rotation for the wider platform team
Take high ownership: write code and design docs for the hardest changes in your area, and ship every day
If SLOs, error budgets, eBPF, Kubernetes, multi-region operation or the noisy neighbor problem appeal to you, the team wants to hear from you
Requirements
Experience running large-scale distributed systems in production across regions and making their reliability measurable
Strong Go; Rust or C/C++ also welcome. You take ownership of the services you build and fix problems across the codebase, including services you did not write
Reliability engineering experience: you have defined SLOs and error budgets for a production service and held it to them
Incident response experience: you have been on call, fixed what paged you, and written post-incident reviews that led to lasting fixes
Production experience operating Kubernetes
Infrastructure as code and GitOps, such as Terraform and Argo CD, with deep experience on at least one of GCP, AWS or Azure. The company uses all three, but you do not need all of them
Solid Linux and networking fundamentals, enough to debug a host under load and reason about DNS, TCP and L4/L7 load balancing
Production experience operating relational databases and caches, including diagnosing performance problems
Comfortable with the company's code and infrastructure being public
Around 5+ years of relevant work is typical, but the depth of what you have built matters more than the number of years
Conditions
Work in person from the San Francisco office
Hybrid schedule: 4 days on-site and 1 day working from home
Offices in San Francisco and Prague, Czech Republic