About the role
- Every agent on Baseten Sandboxes gets its own microVM, where it writes and runs code, calls tools, and keeps state across long tasks. Agents pause and resume constantly, so the machine underneath has to start, stop, snapshot, fork, and resume fast, and keep every tenant isolated while it does. General-purpose virtualization was not built for that workload
- The Agent Infra team builds that layer. Sandboxes run in microVMs with custom Linux kernels on bare-metal servers we operate. You’ll own how sandboxes start, stop, snapshot, fork, and resume, and how they perform on each host’s CPU and memory, down to the hardware. You’ll also own the guest and host side of each sandbox: its identity, how it attaches to different storage classes for performance or capabilities, and the virtual devices that connect it securely to the network. In September 2026, Baseten acquired Blaxel, whose microVM sandboxes are the foundation for Baseten Sandboxes
- We are building a cloud, not just using one. That means designing for many tenants from day one and thinking through what each decision means all the way down to the datacenter. The team is small and ownership is big: we ship in weeks and months, not multi-year programs
- Own the microVM lifecycle for agent sandboxes: start, stop, suspend, resume, snapshot, and fork
- Build and tune the custom guest kernels sandboxes run on
- Tune host CPU and memory configuration so sandboxes run fast and safely on each type of hardware we operate
- Manage host-level resources and sandbox density on each machine
- Own startup and resume performance end to end, from VM boot or snapshot restore to the first command
- Own the guest and host side of each sandbox: its identity, how it attaches to storage, and the virtual devices that connect it to the network
- Design isolation for multi-tenant workloads where the hypervisor is the security boundary
- Debug virtualization and isolation issues at scale, from userspace through the kernel to the hardware
- Contribute architecture decisions and code back to the open-source projects we build on
- EXAMPLE INITIATIVES:
- Blaxel is joining Baseten to build the future of agentic infrastructure
- Securing the open frontier with NVIDIA OpenShell and Blaxel sandboxes
- Baseten Sandboxes documentation
Benefits
- Remote-first work environment. The Baseten team is welcome to work from wherever they want; fully remote, in our San Francisco office, or a mix of both. Today, our team (including our founding team) is spread across the United States, Canada, and Armenia. We provide a $1,000 stipend for you to make your home-office comfortable and productive
- Regular in-person team summits. We get together as a team three times a year to plan, workshop, and most importantly, get to know each other better
- Unlimited PTO. We ask that everyone take at least 4 weeks of vacation. And we have a company-wide break between Christmas and New Year’s Day
- Full healthcare coverage. Medical, dental and vision insurance for you and your family
- Paid parental leave. 16-weeks fully paid parental leave (adoptive and non-birth parents included) and flexibility with schedules while returning to work
- Company-sponsored 401(k) for you to contribute to
- Learning and development budget. We encourage you to take classes, attend conferences, and invest in your craft and we’ll cover expenses to make it happen
- If you’ve worked deep in KVM and Firecracker, Cloud Hypervisor, or QEMU and want to build the computers AI agents run on, we’d love to talk
- If you are a motivated individual with a passion for machine learning and a desire to be part of a collaborative and forward-thinking team, we would love to hear from you
- Hands-on experience with KVM, plus Firecracker, Cloud Hypervisor, or QEMU
- You move fast and like owning a problem end to end on a small team
- Experience running virtualization on bare metal and tuning for specific CPU and memory architectures
- Contributions to KVM, Firecracker, Cloud Hypervisor, QEMU, rust-vmm, or the Linux kernel
- Working knowledge of container runtimes and sandboxing (containerd, runc, gVisor, Kata Containers)
- Experience building a sandbox, serverless, or function runtime product
- Strong systems programming background in Rust and/or Go; C/C++ also welcome
- Experience with Xen
- Experience debugging performance and correctness problems across userspace and kernel boundaries
- Deep understanding of Linux internals: namespaces, cgroups, memory management, and the boot path
- Familiarity with Linux performance tooling such as eBPF, perf, and ftrace
- Experience building cloud infrastructure as the provider (multi-tenant compute that customers run on), not only running workloads on a cloud provider
- Experience with VM snapshot and restore, fast VM resume, or building and tuning custom Linux kernels
- Experience building multi-tenant infrastructure where isolation is a security boundary