About E2B

E2B is a fast-growing Series A startup with over $37M in funding and 8-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

You will be building the next cloud platform for running AI software - a cloud where AI apps are building other software apps.

Your job will be:

1. Building a distributed system for millions and billions of AI agents running on E2B
2. Building an orchestrator for placing sandboxes in the right nodes
3. Adding support for sandbox live migrations
4. Making sure our self-hosting DX is as smooth as possible (we’re open-source)
5. Not letting our sandboxes take more than 200ms to start (starting with the user hitting enter)
6. Scaling to millions and later billions of sandboxes running at the same time
7. Building an observability stack starting at the kernel level of virtual machines

We’re looking for an infrastructure engineer passionate about making things run fast and efficiently, and running A LOT of them at the same time.

If you aren’t afraid of going into the kernel of a VM and words like Firecracker, eBPF, UFFD, block device, L4 load balancing, noisy neighbor problem, or hugepages sound exciting to you, we want to hear from you!

What we're looking for

• 5+ years building distributed systems - You've operated infrastructure at serious scale (100K+ RPS, multi-region, PB-scale data) and understand the trade-offs between consistency, availability, and partition tolerance in practice, not just theory
• Deep Linux internals expertise - You're comfortable working at the kernel level. You've debugged performance issues using eBPF, understand CPU scheduling, memory management, and can explain the difference between cgroups v1 and v2 without looking it up
• VM hypervisor experience - You've worked with Firecracker, QEMU, KVM, or similar. You understand virtio, know what a hypercall is, and have opinions about nested virtualization trade-offs
• Systems programming skills - Strong in at least one of: Go, Rust, C/C++. You've written performance-critical code and know when to reach for lock-free data structures, memory-mapped files, or io_uring