SRE/Infrastructure Engineer
E2B
About E2B
E2B is a fast-growing Series A startup with over $37M in funding and 8-figure revenue. We are building the Agent Cloud and power the infrastructure behind AI labs and some of the most widely used consumer and enterprise agents, including Manus, Genspark, Lindy, ClickUp, Groq, and Black Forest Labs. Our team includes original authors of Firecracker, the AWS microVM technology powering Lambda, along with alumni of Cognition, JetBrains, Zapier, and Wish.
About the role
You will own the Terraform, Kubernetes, and cloud plumbing that lets E2B run millions of sandboxes.
Today our infrastructure runs on Nomad and Terraform across Google Cloud, with multi-cloud expansion in flight. You'll help migrate us to Kubernetes, builds reusable Terraform components, and harden our self-hosted and BYOC deployments.
This role owns BYOC deployments end-to-end, which means you'll work directly with our enterprise customers. You'll join technical pre-sales conversations, run the deployments, and be the point of contact through rollout and operations. You're comfortable in front of a customer, not just in a terminal.
Your job will be:
Making our BYOC offering ready for AWS, Google Cloud, and Azure marketplaces Owning and extending our Terraform footprint across Google Cloud, AWS, and Azure
Building reusable Terraform components (networking, IAM, secrets)
Wiring up observability and tightening the loop between infra change and production behavior
Making BYOC and self-hosted deployments fast and repeatable for our largest customers
Working directly with enterprise customers through deployment and operations - pre-sales, rollout, and ongoing support
We're looking for an infrastructure engineer who actually wants to live in Terraform and Kubernetes every day, and who reaches for modern AI tooling to move faster.
A note on scope: you own how BYOC is deployed, operated, and standardized. Product and custom code changes are owned by our Platform team. You'll partner with them rather than fork the product per customer. Deep system-internal issues escalate into Platform/Core. This keeps your focus on making deployments repeatable, not maintaining snowflakes
If words like Terraform modules, Kubernetes operators, GCP VPCs, IAM bindings, Cloudflare workers, and BYOC deployments sound like a good Tuesday, we want to hear from you.
What we're looking for
5+ years operating production cloud infrastructure - You've owned Terraform and at least one orchestrator (Kubernetes, Nomad, ECS) in production. You've built modules, managed state, debugged drift, and managed production incidents.
Hands-on Kubernetes at meaningful scale - You've operated Kubernetes clusters past the tutorial stage: real workloads, real traffic, real on-call. You can speak to ingress, RBAC, and autoscaling.
Strong Linux fundamentals - We're a low-level infrastructure product. You're comfortable deep in Linux: networking, namespaces and cgroups, systemd, filesystems, and debugging at the OS level. When a deployment breaks, the root cause is often below the orchestrator, and you can follow it there.
Comfortable working directly with customers - A chunk of BYOC is customer-facing: pre-sales technical discussions, deployment, and operational support for enterprise customers. You can hold a technical conversation with a customer and own the relationship through a rollout, not just hand off a config.
Multi-cloud comfort, with one cloud at expert depth - You've built and operated on Google Cloud, AWS, or Azure. Configured VPCs, managed IAM, set up private networking, debugged routing and DNS. We're primarily on GCP today and expanding; bring depth in at least one and be willing to ramp on the others.
Terraform as a first-class skill - You read other people's modules without flinching, write your own when needed, and have opinions about state, workspaces, and module boundaries.
Comfortable reading and writing code when the work crosses out of YAML - You won't be writing product Go. But you should read Go and Terraform fluently, contribute small fixes, and not be lost when a debug session moves from config into source.
Startup-pace tolerance - You've worked at a small team where ambiguity is the default and "figure it out" is the assignment. You don't need a ticket to start, and you push back when something doesn't make sense.
Familiarity with high scale environments - Either a high-traffic online product where you owned scaling problems, or an infrastructure-product company where infra was the product. Both work.
Excited to work in person from San Francisco on a DevTool product - We work as a team in person and the work moves faster when we're in the same room.
Bonus points for
Deep cloud expertise in AWS, GCP, or Azure
Experience building self-hosted or BYOC deployments for enterprise customers
Contributions to open-source infrastructure projects (Terraform providers, Kubernetes operators, Cloudflare modules)
Experience helping infra-side AI tooling (Claude, Codex) carry real production migrations
What it’s like to work at E2B
We’re a fast-growing startup with in-person (4 days on-site, 1 day WFH) offices in San Francisco and Prague, Czech Republic. We already generate 8-figure revenue and work directly with top-tier AI companies like Groq, Manus, Hugging Face, Lindy, and other exciting teams pushing the frontier of AI.
We offer healthcare, vision, and dental insurance, unlimited PTO, 401k, and a variety of perks for in-office employees.