You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
E2B

Software Engineer, Infrastructure

  • Office

Salary

$250,000 - 350,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is a fast-growing Series A startup that has raised over $37M and generates 9-figure revenue.

It builds the Agent Cloud and supplies the infrastructure behind AI labs and widely used consumer and enterprise agents, including customers such as Manus, Genspark, Lindy, Groq and Artificial Analysis.

Its founders include the original authors of Firecracker, the AWS microVM technology behind Lambda, and the team has alumni from Cognition, JetBrains, Zapier and Wish.

The company has started billions of Firecracker sandboxes across regions on Google Cloud, AWS and Azure, and some single customers want 100,000 running at once.

The control plane is a set of Go services backed by Postgres and Redis, running on Kubernetes and managed through GitOps.

You will own how the platform fits together, working with systems engineers who own Linux, the host software that runs sandboxes, and sandbox networking, as well as the product engineers who build on the control plane.

The runtime is open source, and the API service and the proxy are good places to start reading the code.

Responsibilities

  • Build Go services and APIs, including new endpoints, gRPC and OpenAPI contracts, and the data models behind them.
  • Build and evolve the edge proxy and its routing state so traffic stays correct as sandboxes pause, resume and move between hosts.
  • Scale the API, Redis and Postgres to hundreds of thousands of concurrent sandboxes per region through query and schema design, caching, sharding and migrations under load.
  • Write Kubernetes automation that scales with demand, adding capacity ahead of load spikes and draining long-lived nodes without disrupting running sandboxes.
  • Implement placement across machine families and CPU generations on several clouds, so a resumed sandbox always lands on a host that can restore it.
  • Build the Terraform modules, Helm charts and Argo CD configuration that let a new region or cloud be stood up quickly and repeatably.
  • Build metrics, tracing and alerting for the services you own.
  • Make sure self-hosted and enterprise deployments run what the company runs, since the project is open source.
  • Join the platform team's on-call rotation for the platform you build.
  • Take high ownership: write the code and design docs for the hardest changes in your area, and ship every day.

Requirements

  • Have owned a large-scale distributed system end to end, building it, running it in production across regions, and being the one called when it breaks.
  • Write strong Go, and ship fixes in services you did not write.
  • Have run large-scale Kubernetes clusters in production, including controllers, operators and node lifecycle management.
  • Have hands-on experience with infrastructure as code and GitOps, such as Terraform and Argo CD, and deep experience with at least one of GCP, AWS or Azure. The company runs on all three, so you do not need all of them.
  • Design APIs and data models with backward-compatible gRPC and OpenAPI contracts and Postgres schemas, and handle schema changes and migrations on a primary that cannot go down.
  • Have solid Linux and networking skills, enough to debug a host under load and reason about L4/L7 traffic, load balancing and connection draining.
  • Be excited to work in person from San Francisco.
  • Be comfortable with the code and infrastructure being public.
  • Typically have around 5 or more years of relevant work, though the depth of what you have built matters more than a specific number.
  • Bonus:
  • Experience building reliable distributed APIs with idempotency, leases and backpressure.
  • Experience with multi-account cloud organizations such as AWS Organizations or GCP folder hierarchies.
  • Experience shipping infrastructure that customers run themselves.
  • Familiarity with Firecracker, KVM, or how VM workloads behave on shared hosts.
  • Contributions to Kubernetes or other CNCF projects.

Conditions

Work in person in a hybrid pattern: 4 days on-site and 1 day working from home.

Offices are in San Francisco and Prague, Czech Republic, and this role is based in San Francisco.

Benefits

  • Healthcare, vision and dental insurance.
  • Unlimited PTO.
  • 401k.
  • A range of perks for in-office employees.

Where you’d work

From the office

The office

About the company

E2B

Office in San Francisco, United States

Also hiring in Prague, Czechia

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 21 checks run
  • 1 red flag

Still hiring?

14 checks

No red flags

How crowded?

7 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation, Employment
Tech stack
  • Go
  • PostgreSQL
  • AWS
  • Google Cloud
  • Kubernetes
  • Terraform
  • Azure
  • Linux
  • Argo CD
  • Helm
Type
Full-time
Specialty
Backend
Region
United States
Pay period
Annual
Show 4 more factsShow less

Role

Category
Development
Specialty
Backend
Tech stack
  • Go
  • PostgreSQL
  • AWS
  • Google Cloud
  • Kubernetes
  • Terraform
  • Azure
  • Linux
  • Argo CD
  • Helm

Location

Work model
Office
Region
United States
Office
  • San Francisco, United States

Compensation

Salary
$250,000 - 350,000 / year
Pay period
Annual

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason