Forward Deployed Engineer

About E2B

E2B is a fast-growing Series A startup with 8-figure revenue. We’ve raised over $37M since our founding in 2023. Our customers include companies like Microsoft, Perplexity, Hugging Face, Manus, and Groq. We’re building the next hyperscaler for AI agents.

This is our first FDE hire.
You’ll define how E2B works with enterprise customers technically — the deployment playbooks, the integration patterns, the reference architectures. What you build becomes the foundation for the team that follows.

You’ll be E2B’s technical point of contact for our most important customers — the ones building AI agents that need secure and scalable sandboxes for their AI agents.

Your job is to make these customers successful. That means sitting inside their architecture, understanding their constraints, and doing whatever engineering work it takes to get E2B running in production. Some weeks that’s writing a custom sandbox template. Other weeks it’s debugging a networking issue in a BYOC deployment, building an integration prototype, or pairing with a customer’s engineering team to redesign how they handle sandboxed execution.

You’ll work directly with the customer’s engineers and our internal engineering team. When you hit a product limitation, you don’t just file a ticket — you understand the problem deeply enough to propose a solution, and you have the credibility (because you’ve been in the codebase) to make the case for it.

• Integrate E2B into customer stacks. Write code that connects E2B sandboxes to customer applications — SDK integrations, API wrappers, orchestration logic, CI/CD pipeline hooks. Python, Type Script, and Go are the languages that matter.
• Plan and execute BYOC and on-prem deployments. Many enterprise customers won’t use E2B’s managed cloud — they need E2B running inside their own AWS/GCP/Azure accounts or on bare‑metal infrastructure they control. You’ll lead these deployments end‑to‑end: assess their infrastructure, design the network topology (VPC peering, private endpoints, egress controls), provision compute with IaC, wire up observability, validate isolation, and get it to production.
  
  You’ll work inside environments you don’t own, with security policies you didn’t write, alongside platform teams with their own opinions about how things should work.
• Build custom sandbox templates and environments. Customers have specific runtime requirements — particular system packages, language versions, pre‑loaded models, custom file systems. You’ll build and optimize these.
• Own the technical success of enterprise deals. From initial technical discovery through production go‑live. You’re accountable for the customer being live and happy, not just for a successful demo.
• Debug hard problems under pressure. A customer’s sandbox is crashing in production. Their UFFD handler is deadlocking. Network egress is being blocked by their firewall rules. You figure it out.
• Feed signal back to product, sales, and engineering. You’ll see patterns across customers — what’s missing, what’s broken, what’s confusing. You’ll write up proposals, contribute to design docs, and sometimes ship fixes yourself.
• Build repeatable assets. The integration you build for Customer A should become the reference architecture for customers B through Z. You’ll write documentation, create example repos, and codify what works.
• Navigate enterprise IT environments. Large customers don’t just have engineering teams — they have IT, security, and compliance gatekeepers. You’ll work through SSO/SAML integration requirements, deal with MDM‑managed developer endpoints (Windows and Mac), troubleshoot corporate proxy and firewall interference, and ensure E2B works within the customer’s security posture, not around it.

• 5+ years of software engineering experience
  , with real depth in at least one of: backend systems, infrastructure/platform engineering, or Dev Ops/SRE. You’ve shipped and operated production systems, not just written code.
• Strong proficiency in Python and Type Script. Go is a bonus. You’ll read and write code in these languages daily — not toy scripts, but integrations, tooling, and debugging…