Skip to main content
E2B logo

Site Reliability Engineer - Platform

E2B

San Francisco, CAFull-timePosted todayStill listed · checked in the last 2 days

See where you stand before you apply. No sign-up to start.

You apply on the posting's application page, with no Olive account needed.

Watch jobs like this.

Don't just apply. Show up ready.

Olive works from this exact posting.

At a glance

Compensation
No compensation found
Location
San Francisco, CA
Schedule
Full-time
Work Authorization
Not specified

Olive focuses on jobs in the United States, including remote roles you can work from there.

Job overview

E2B builds infrastructure for AI agents, running Firecracker sandboxes across Google Cloud, AWS, and Azure. The Site Reliability Engineer will improve platform reliability through code, observability, automation, and production-ready capabilities, working with infrastructure, systems, and sandbox teams. The role includes incident response and on-call work, and is based in person in San Francisco with a four-day on-site, one-day work-from-home schedule.

Skills & qualifications

RequiredNice to have

Skills

Site Reliability Engineering, nice to haveGo (Programming Language), nice to haveC++ (Programming Language), nice to haveKubernetes, nice to haveInfrastructure as Code (IaC), nice to haveDevOps, nice to haveTerraform, nice to haveLinux, nice to haveInternetworking, nice to haveRelational Databases, nice to haveReliability, nice to haveIncident Response, nice to haveChaos Engineering, nice to haveDistributed Systems Operations, requiredRust, nice to haveC/C++, nice to haveReliability Engineering, requiredSLOs and Error Budgets, requiredGitOps, requiredArgo CD, nice to haveGCP, nice to haveAWS, nice to haveAzure, nice to haveNetworking, requiredDNS, requiredTCP, requiredLoad Balancing, requiredCaches, requiredPerformance Diagnosis, requiredPrometheus, nice to haveGrafana, nice to haveOpenTelemetry, nice to haveKernel Tracing, nice to haveeBPF, nice to haveCapacity Planning, nice to haveCost Efficiency, nice to haveDeterministic Simulation Testing, nice to haveFirecracker, nice to haveKVM, nice to haveVM Workload Operations, nice to haveOpen Source Contributions, nice to have

Qualifications

Around 5+ Years Relevant Work, nice to haveIn-Person San Francisco Work, requiredComfort With Public Code and Infrastructure, required

Benefits

Medical Insurance
Vision Insurance
Dental Insurance
Paid Time Off
401(k) Match

Full job description

About E2B E2B is a fast-growing Series A startup with over $37M in funding and 9-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, Groq, and Artificial Analysis. 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 E2B has started billions of Firecracker sandboxes across regions on Google Cloud, AWS and Azure, for customers whose products stop when our sandboxes do. Reliability here is an engineering problem: the fixes for our hardest incidents land in code, not in configuration. Your job will be to build the reliability of the platform: defining what healthy means, building the observability and automation that keep it there, and making new capabilities work reliably in production. You'll work closely with our infrastructure and systems engineers, who build the platform, and with our sandbox team in Prague. Responsibilities include:

  • Defining SLOs and error budgets for the platform's core paths, such as sandbox start, resume and connect, and making them part of how we alert, release and prioritize

  • Building the observability and alerting that tells us the platform is healthy before customers do

  • Taking new platform capabilities from first release to working reliably in production

  • Building the automation that removes operational work, from release checks to routine fleet operations

  • Building the security and trust layers the platform's reliability depends on, such as service-to-service mutual TLS

  • Making our private cloud and enterprise deployments as reliable as our own regions

  • Running incident response, and improving how we handle incidents so a class of failure does not come back

  • Being on call, and helping shape the rotation for the rest of the platform team

This role requires a high amount of ownership. You'll write the code and the design docs for the hardest changes in your area, and ship every day. If words like SLOs, error budgets, eBPF, Kubernetes, multi-region, or noisy neighbor problem sound exciting rather than scary, we want to hear from you! What we're looking for

  • Experience operating 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 proactively fix issues across the codebase, including in services you didn't originally write

  • Reliability engineering: you've defined SLOs and error budgets for a production service and held the platform to them

  • Incident response: you've been on call, fixed what paged you, and written post-incident reviews that led to lasting fixes

  • Experience operating Kubernetes in production

  • Infrastructure as code and GitOps, for example Terraform and Argo CD, with deep experience on at least one of GCP, AWS or Azure; we run on all three, and you don't need to know them all

  • Solid Linux and networking fundamentals: enough to debug a host under load and reason about DNS, TCP and L4/L7 load balancing

  • Operating relational databases and caches in production, including performance diagnosis

  • Excited to work in person from San Francisco

  • Comfortable with our code and infrastructure being public

We expect this experience will often come from around five or more years of relevant work, but the depth of what you've built matters more than a specific number. Bonus points for:

  • Running observability pipelines at scale, for example Prometheus, Grafana and OpenTelemetry

  • Kernel tracing and eBPF tooling

  • Capacity planning and cost efficiency across clouds

  • Chaos engineering or deterministic simulation testing

  • Familiarity with Firecracker, KVM or how VM workloads behave on shared hosts

  • Contributions to CNCF or similar open source projects

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 9-figure revenue and work directly with top-tier AI companies like Manus, Genspark, Lindy, Groq, Artificial Analysis 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.

How this job compares

Set against the 2,225 open Site Reliability Engineer jobs on Olive Jobs, counted November 18, 2026.

Pay
  • This postingNot listed
  • California median$165–244K/yr326 salary ranges
  • US median$60–69/hr25 hourly ranges
Openings
Olive Jobs lists 415 open Site Reliability Engineer jobs in California and 2,225 across the US. 19% of them nationwide are listed as remote or flexible.
Hiring the most in California
Experience
Site Reliability Engineer postings that state a minimum ask for 5 years of experience at the median; the middle half ask for 5 to 8 years (1,869 postings).
Education
484 of the 2,225 open Site Reliability Engineer jobs (22%) ask for a bachelor's degree or higher.

Counted across the open, public US postings on Olive Jobs on November 18, 2026. Figures based on too few postings are left out.

Prepare for this role

You've read the whole posting — now see how you match it.