Site Reliability Engineer - Platform
Company websitee2b.dev (E2B, opens in new tab)
Base salary $250K – $350K
Employer-published annual base salary, USD. Advertised base range in San Francisco, CA
You apply on the employer's own site. Six Figure Work does not handle applications.
- LocationSan Francisco, CA
- WorkplaceOn-site
- Status at last checkSource accepting applications when checked
- Last checked (12 min ago) · observed since
About this job
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 on Ashby · View original posting (opens in new tab)
How this pay compares
Base floor $250,000, above 90% of the 4,892 Software Engineering roles in California on this site. The employer's range is $100,000 wide, 40% of the floor. Observed open for 1 day so far (since Nov 19, 2026).
Pay in context
Among 4,892 Software Engineering roles in California listed on this site, the median base floor is $176,381 and the middle half runs from $149,100 to $202,000. This role's floor ($250,000) is above 90% of them; 42 others list the same floor.
Base floors of 4,892 Software Engineering roles in California
Table
| Floor band | Share | Postings |
|---|---|---|
| $100K to $125K | 7.8% | 384 |
| $125K to $150K | 17.5% | 856 |
| $150K to $175K | 22.7% | 1,109 |
| $175K to $200K | 22.7% | 1,110 |
| $200K to $225K | 12.8% | 625 |
| $225K to $250K | 6.6% | 323 |
| $250K to $275K | 4.6% | 227 |
| $275K and up | 5.3% | 258 |
How this is calculated
- Statistic
- Base floor distribution of the cohort
- Formula
- count of cohort postings in each $25K band of published base floor / postings in the cohort
- Denominator
- 4,892 open postings with this job family in California
- Sample size
- 4892
- Hidden when
- the cohort has fewer than 30 postings
- Calculation version
- jobpage-analysis-v1
- Data as of
- 2026-11-20
- Employer set
- Open jobs on this site that publish a base salary of $100,000 or more
Only jobs on this site count, and each one publishes a base salary of $100,000 or more, so this compares six-figure jobs with each other, not with the whole market. Computed Nov 20, 2026.
State against nationwide
Median base floor in California vs nationwide
Table
| Value | postings | |
|---|---|---|
| Software Engineering, California | $176,381 | 4,892 |
| Software Engineering, all states | $160K | 13,255 |
| This job's base floor (marked) | $250K |
How this is calculated
- Statistic
- Median floor, state vs nationwide
- Formula
- median published base floor of each cohort
- Denominator
- open postings of this job family
- Sample size
- 4892 in California; 13255 nationwide
- Hidden when
- either cohort has fewer than 30 postings
- Calculation version
- jobpage-analysis-v1
- Data as of
- 2026-11-20
- Employer set
- Open jobs on this site that publish a base salary of $100,000 or more
How E2B pays
This is the highest base floor among E2B's 7 live roles on this site (shared with 2 others). Across them the median floor is $240,000; the middle half runs from $200,000 to $250,000.
Base floors of E2B's 7 live roles
Table
| Floor band | Share | Roles |
|---|---|---|
| $100K to $125K | 0.0% | 0 |
| $125K to $150K | 0.0% | 0 |
| $150K to $175K | 28.6% | 2 |
| $175K to $200K | 0.0% | 0 |
| $200K to $225K | 0.0% | 0 |
| $225K to $250K | 28.6% | 2 |
| $250K to $275K | 42.9% | 3 |
How this is calculated
- Statistic
- Employer base floor distribution
- Formula
- count of the employer's open roles in each $25K band of published base floor / its open roles
- Denominator
- 7 open public roles at this employer
- Sample size
- 7
- Hidden when
- this employer has fewer than 5 roles
- Calculation version
- jobpage-analysis-v1
- Data as of
- current
- Employer set
- Open jobs on this site that publish a base salary of $100,000 or more
Similar pay elsewhere
Other employers' Software Engineering roles in California with the nearest published base floor to $250,000, one per employer.
- Staff Software Engineer Hike Medical · base floor $250,000
- Engineering Manager, Capital Adyen · base floor $250,000
- Tech Lead Manager Hamilton AI · base floor $250,000
- Senior Engineer, Backend/Infra AgentMail · base floor $250,000
- Engineering Manager, Cloud Infrastructure Replit · base floor $250,000
This listingSite Reliability Engineer - Platform$250K – $350K
Software Engineer, Systems$250K – $350K
Site Reliability Engineer - Enterprise$250K – $350K
Software Engineer, Infrastructure$250K – $350K
Head of DevRel and Ecosystems$240K – $310K
Trust & Safety Engineer$230K – $290K
Brand Creative Director$170K – $230K
Chart as a table
| Role | Published base |
|---|---|
| Site Reliability Engineer - Platform (this listing) | $250K - $350K |
| Software Engineer, Systems | $250K - $350K |
| Site Reliability Engineer - Enterprise | $250K - $350K |
| Software Engineer, Infrastructure | $250K - $350K |
| Head of DevRel and Ecosystems | $240K - $310K |
| Trust & Safety Engineer | $230K - $290K |
| Brand Creative Director | $170K - $230K |
Observed changes
No changes to the pay or listing since we first observed this role on Nov 19, 2026 (1 day ago).
- First observed on the employer's board, already publishing a qualifying base salary
- Observed since
- Employer-stated posting date
- 2026-11-19
Where this pay comes from
Location as the employer wrote it: San Francisco
USD 250,000 – 350,000 · 1 YEAR · Salary
- Method
- Structured pay field published by the employer
- Checked
- Rule set
- us-base-v2
The employer's job board publishes this pay as a dedicated data field. We read the field directly; no interpretation was needed.
What we verified
- The pay figures come from the employer's own listing, quoted exactly above.
- The pay is an annual base salary in US dollars with a minimum of at least $100,000.
- The role was publicly listed on the employer's job board when last checked.
We do not verify what the employer will actually offer, whether the employer is still recruiting for the role, or anything beyond what the employer published. Full methodology.
