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:
Building with VM hypervisors like Firecracker, gVisor, or Linux system
Resource monitoring of sandboxes
Developing networking solutions for secure, isolated environments
Optimization of E2B sandbox performance and shaving off every millisecond
Building new kind of programming language runtimes for LLMs
We’re looking for an infrastructure engineer with a diabolical obsession with making things run fast and efficiently and running A LOT of them at the same time.
If this sounds exciting to you, we want to hear from you!
What we’re looking for
5+ years building infrastructure, especially distributed systems
Experience building infrastructure on scale
Excited to work in person from San Francisco on a devtool product
Detail-oriented with a great taste
Excited to work closely with our users
Not being afraid to take ownership of the part of our product
If you join E2B, you’ll get a lot of freedom. We expect you to be proactive and take ownership. You’ll be taking projects from 0 to 1 with the support of the rest of the team.
What it’s like to work at E2B
Work at a fast-growing startup at an early team (we grow 20%-100% MoM)
We ship fast, but don’t release junk
We like hard work and problems. Challenges mean potential value.
We have a long runway and can offer a competitive salary for the startup at our stage
Work closely with other AI companies on the edge of what’s possible today
Dogfooding our own product on projects like Fragments
No meetings, highly writing, and transparent culture
You’re the decision maker in day-to-day, important product and roadmap decisions are on Vasek (CEO) and Tomas (CTO)
Spend 10-20% of the roadmap on highly experimental projects
Hiring process
We aim to have the whole process done in 7-10 days. We understand that it’s important to move fast and try to follow up in 24 hours after each stage.
30-minute call with Vasek (CEO). We’ll go over your past work experience and what you’re looking for to make sure this would be a good fit for both of us.
First technical interview with Tomas (CTO). About 1 hour long call. You’ll get asked thorough technical questions. Often these are questions about problems that we ourselves experienced while building E2B.
Second technical interview. Another 1-2 hours long call. Expect live coding on this call. We’ll ask you to solve specific problems (don’t worry, it’s not a leet code) that are related to your role.
One day of in-person hacking at our office (paid). We invite you to our office to work on the product with us. This is a great opportunity for all of us to try how it’s working together and for you to meet the team.
Last call with Vasek. Last 30-minute call with the CEO to talk more about the role and answer any of your questions.
Decision and potential offer.
