Site Reliability Engineer - Platform
E2BSan FranciscoOn-Site
Needs a free Superjobs account. You'll finish on E2B's Ashby page.
Skill score
Summary
The Site Reliability Engineer - Platform defines what healthy means for E2B's platform, builds the observability, alerting and automation that keep it reliable, and takes new capabilities to reliable production, while also running incident response and on-call. It suits engineers with deep experience operating large-scale distributed systems who want to fix reliability problems in code rather than configuration.
- Function
- Development
- Estimated salary
- Est. $138k–208k/yr
- Estimated for a mid-level role, ~5 yrs experience, United States. Not published by the employer.
- Work mode and location
- On-Site, San Francisco
- Experience
- 5+ yrs
- Employment type
- Full-time
Job description
Overview
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.
Roles and responsibilities
- 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.
Skills required
Top skills
- Go
- Kubernetes
- SLOs and error budgets
- Incident response
All skills (8)
- Infrastructure as code
- Terraform
- Argo CD
- GCP, AWS or Azure
- Linux and networking
- Relational databases and caches
- Prometheus and Grafana
- eBPF
Qualifications
- 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.
Nice to have
- 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
Other details
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!
Benefits
We offer healthcare, vision, and dental insurance, unlimited PTO, 401k, and a variety of perks for in-office employees.
Company info
About E2B
E2B is an open-source sandbox platform that gives AI agents isolated machines in which to run their code. Its sandboxes are used by developers and teams building AI agents.