Blaxel

AWS for the Agentic Era

Blaxel is building the cloud infrastructure specifically designed for artificial intelligence agents. As AI agents shift from experimental tools to production systems that manage calendars, respond to emails, and generate code autonomously, they require infrastructure fundamentally different from traditional web applications. The company provides a perpetual sandbox platform that spins up virtual machines in under 25 milliseconds, offering automatic hibernation and scale based on agent activity patterns. Blaxel has already processed billions of agent requests across 16 global regions, with one customer running over 1 billion seconds of agent runtime to process millions of videos.

A Culture of Fast-Paced Infrastructure Building

Blaxel operates with a unique dynamic, driven by a six-founder team—including Paul Sinaï, Charles Drappier, Christophe Ploujoux, Nicolas Lecomte, Thomas Crochet, and Mathis Joffre—who previously built and sold an analytics company to OVHcloud. This shared history fosters a highly collaborative and ambitious engineering culture. The team is focused on building from first principles around agent requirements, avoiding the complexity of adapting legacy services. They emphasize rapid experimentation, true isolation, and building LLM-friendly OS interfaces that agents can directly consume.

What You'll Actually Do

As an engineer at Blaxel, you will be tackling deep infrastructure challenges that current major cloud providers like AWS and Google Cloud weren't built to handle. You might work on optimizing their serverless compute engine to deliver sub-25ms cold starts, building secure sandboxes that prevent container escapes, or developing intelligent gateways that provide unified access to major LLMs with built-in caching and rate limiting. The work involves creating systems that can handle distributed, high-latency connections required by AI agents, ensuring enterprise-grade security like SOC2 and HIPAA compliance, and implementing data residency controls.

Compensation & Benefits

Blaxel offers competitive compensation for a seed-stage startup. Based on their current job listings, a DX/AX Engineer can expect $175K–$250K with 0.1%–0.5% equity, while a Network Software Engineer commands $250K–$300K with 0.1%–1% equity. A Site Reliability Engineer role offers $175K–$250K with 0.05%–0.5% equity, and a Forward Deployed Engineer ranges from $150K–$225K. Non-engineering roles, such as Head of Marketing and Founding Technical Recruiter, offer $140K–$230K and $140K–$180K respectively. Employees also receive equity packages, and the company operates primarily on-site in San Francisco.

The Interview Process

While specific details about the interview rounds are not widely publicized yet, the process for technical roles at Blaxel is expected to be rigorous and focused on infrastructure expertise. Candidates can anticipate technical deep dives into systems engineering, cloud architecture, and networking challenges. Given the founding team's strong background in infrastructure and their previous successful exit, interviews likely involve significant architectural discussions and problem-solving scenarios related to building scalable, high-performance computing environments.

Why Join / Why Not

Why Join: If you are passionate about foundational cloud infrastructure and want to be at the forefront of the AI agent revolution, Blaxel offers a rare opportunity. You will be solving novel problems that even Big Tech hasn't fully figured out yet, working alongside a proven founding team with a successful exit under their belts. The recent $7.3M seed funding led by First Round Capital provides a solid runway to build out their vision.

Why Not: Blaxel is taking on massive incumbents like AWS, Google Cloud, and Microsoft Azure, as well as newer players like Modal and Replicate. The competition is fierce, and the pressure to deliver flawless, highly scalable infrastructure is immense. The company requires a strong on-site presence in San Francisco, which may not appeal to those seeking fully remote or highly flexible work arrangements. If you prefer working on application-layer features rather than deep backend infrastructure, this might not be the right fit.