Skip to main content
E2B logo

Software Engineer, Systems

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 and operates Firecracker sandboxes across major cloud providers. The Software Engineer, Systems will build and own the Go service running on each host, along with Linux host networking, memory, and isolation. The role spans sandbox lifecycle reliability, performance, fleet upgrades, observability, and resource isolation, with engineers focusing on Linux systems or sandbox networking.

Skills & qualifications

RequiredNice to have

Skills

Go (Programming Language), nice to haveLinux, nice to haveC++ (Programming Language), nice to haveInternetworking, nice to haveCgroups, nice to haveMemory Management, nice to haveSystems Software, requiredRust, requiredC/C++, requiredProcess Management, requiredCPU Scheduling, requiredNamespaces, requiredLinux Networking, requiredFailure Recovery, requiredCrash Recovery, requiredState Reconciliation, requiredNetwork Namespaces, nice to haveVirtual Interfaces, nice to haveIptables/Nftables, nice to haveEgress Control, nice to havePerformance Profiling, requiredFirecracker, nice to haveKVM, nice to havegVisor, nice to haveRunc, nice to haveSnapshot and Restore, nice to haveGPU Infrastructure, nice to haveGPU Passthrough, nice to haveGPU-as-a-Service, nice to haveKernel Tracing, nice to haveeBPF Tooling, nice to haveSeccomp, nice to haveLinux Security Modules, nice to haveKubernetes, nice to haveOpen Source Contributions, nice to have

Qualifications

Large Production Fleet Experience, requiredFive or More Years Relevant Work, nice to have

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. Every sandbox is a real virtual machine that has to start in well under a second, resume from a snapshot on a different host, and share a host with up to about 200 others without noticing them. Your job will be to build and own the Go service on every host that creates, pauses, resumes and tears down sandboxes, along with the Linux underneath it: host networking, memory and isolation. You'll work closely with our sandbox team in Prague, who own the Firecracker runtime, the guest kernel, sandbox storage and live migration, and with our infrastructure engineers, who put the platform together. We're hiring more than one engineer into this role, each with a different focus: some go deepest on Linux and how sandboxes run on the host, others on sandbox networking. Our runtime is open source at github.com/e2b-dev/runtime, and the sandbox package is a good place to see what you'd work on. Responsibilities include:

  • Making sandboxes start fast and keeping them fast as the fleet grows to millions and later billions of sandboxes, with starts under 200ms

  • Evolving the architecture of the software that runs sandboxes on every host, so it can change without disrupting them

  • Making the sandbox lifecycle reliable under failure, so no sandbox is leaked or lost when a process or host dies

  • Keeping the host OS and kernel current across the fleet, rolling out upgrades without disrupting running sandboxes

  • Building the sandbox network: isolation, egress control and addressing for untrusted workloads

  • Enforcing resource isolation between sandboxes on shared hosts, so every sandbox gets the CPU, memory and I/O it was allocated

  • Building host-level observability, so we understand what every sandbox costs the host it runs on

  • Being on call for the platform you build, alongside 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 you aren't afraid of going deep into the Linux kernel when a problem needs it, and words like eBPF, cgroups, network namespaces, nftables, conntrack, or noisy neighbor problem sound exciting to you, we want to hear from you! What we're looking for

  • Experience building and operating systems software across a large production fleet: node agents, container or VM runtimes, schedulers, or similar

  • Strong Go, or strong Rust or C/C++ and the willingness to pick up Go quickly; our services are in Go

  • Deep Linux knowledge: processes, CPU scheduling, memory management, cgroups and namespaces, and the network stack

  • Experience making software correct under failure: crash recovery, reconciling recorded state with what is actually running, and cleanup when a process or host dies

  • For a networking focus: Linux networking for multi-tenant workloads, such as network namespaces, virtual interfaces, iptables/nftables and egress control

  • A performance mindset: you've shaved milliseconds off hot paths, profiled production systems under load, and treat p99 as a number you own

  • 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:

  • Experience with VM or container runtimes such as Firecracker, KVM, gVisor or runc, including memory management and snapshot and restore

  • GPU or accelerator infrastructure, passthrough or GPU-as-a-service

  • Kernel tracing and eBPF tooling

  • OS-level hardening, such as seccomp and Linux security modules

  • Running workloads on Kubernetes, which our fleet runs on

  • Contributions to the Linux kernel, Firecracker, 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 11,265 open Systems Engineer jobs on Olive Jobs, counted November 18, 2026.

Pay
  • This postingNot listed
  • California median$140–207K/yr1,738 salary ranges
  • California median$70–88/hr44 hourly ranges
Openings
Olive Jobs lists 2,004 open Systems Engineer jobs in California and 11,265 across the US. 5% of them nationwide are listed as remote or flexible.
Hiring the most in California
Experience
Systems Engineer postings that state a minimum ask for 5 years of experience at the median; the middle half ask for 3 to 8 years (9,471 postings).
Education
4,107 of the 11,265 open Systems Engineer jobs (36%) ask for a bachelor's degree or higher.

Pay, requirements and demand for Software Engineer jobs

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.