Site Reliability Engineer - Platform

E2B
San Francisco, CA
On-siteCareer-pivot friendly

Who this role is best for

Best suited to candidates with deep experience in large-scale distributed systems and reliability engineering working in multi-region cloud environments.

Best fit for

  • Candidates with a background in defining and maintaining SLOs and error budgets for mission-critical services
    — “defining what healthy means, building the observability and automation that keep it there”
  • Individuals who have operated Kubernetes in production and built observability pipelines at scale
    — “Experience operating Kubernetes in production”
  • Candidates comfortable with on-call responsibilities and incident response with lasting fixes
    — “Incident response: you've been on call, fixed what paged you, and written post-incident reviews that led to lasting fixes”
  • Candidates with a track record of building automation for fleet operations and release checks
    — “Building the automation that removes operational work, from release checks to routine fleet operations”

Things to consider

  • The role requires a significant on-site presence in San Francisco, with only one day of remote work per week
    — “Excited to work in person from San Francisco”
  • Candidates must be comfortable with their code and infrastructure being made public
    — “Comfortable with our code and infrastructure being public”

How to stand out

  • Highlight your experience with defining SLOs and implementing error budgets in your resume and interviews
    — “Reliability engineering: you've defined SLOs and error budgets for a production service”
  • Showcase your hands-on code ownership and proactive issue resolution in services you did not originally write
    — “you take ownership of the services you build and proactively fix issues across the codebase”
  • Emphasize your experience with multi-region cloud deployments and observability pipeline scaling
    — “operating large-scale distributed systems in production across regions”
  • Demonstrate your ability to build and maintain security layers like mutual TLS in production systems
    — “Building the security and trust layers the platform's reliability depends on, such as service-to-service mutual TLS”
Pace · Fast PacedCollaboration · HighAutonomy · MediumDecision Impact · Team

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

  • reliability improvements
  • automation
  • security
Typical background
software engineeringreliability engineering

Skills & requirements

Required

GoKubernetesObservabilityIncident ResponseSlosError Budgets

Preferred

RustC/c++EbpfMulti-region

Stack & domain

GoRustC/c++SlosError BudgetsEbpfKubernetesMulti-regionNoisy Neighbor ProblemObservabilityAlertingAutomationSecurityTrust LayersIncident ResponseOperating Relational DatabasesOperating CachesPerformance DiagnosisOwnershipProblem-solvingTeam CollaborationCommunicationDecision-makingCloud InfrastructureAI LabsEnterprise Agents

About the role

Original posting from E2B via Ashby

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.

Source: E2B careers (Ashby)

Similar roles

More roles at E2B