5+ years in production systems at the infrastructure layer, focusing on high-throughput or low-latency serving systems.
Direct experience with LLM inference serving in a production environment.
Proven reliability ownership, with experience designing for failure.
Strong systems fundamentals in concurrency, networking, and scheduling.
Self-directed with the ability to navigate ambiguity in a founding role.
Responsibilities
Own the end-to-end inference serving stack, from design to production.
Continuously optimize cost-per-token through batching and hardware utilization.
Implement monitoring and failover systems for reliability under customer load.
Collaborate with the compiler and bring-up team to define model interfaces.
Shape the serving roadmap, influencing future development and strategies.
Set technical standards for the growing serving team through early architecture decisions.
Benefits
Opportunity to shape the architecture and direction of a new team.
Work in a fast-paced, innovative environment with real ownership.
Be part of a founding team with significant influence on company culture.
Engage in cutting-edge technology with a focus on specialized hardware.
Full Job Description
About the Role
Getting a model correct and fast on our silicon is only half the problem - the other half is serving it. You'll build and own the inference layer that sits between a bought-up model and a live customer request: request scheduling, batching, KV-cache management, autoscaling across our ASIC fleet, and the failure modes that only show up at real traffic and real scale.
This is a founding role on a small team, which means the scope is wide and the ownership is real: there's no separate SRE org to hand reliability to and no platform team to hand infra to. You'll design the serving architecture, then be the person paged when it breaks. The bet is that a serving stack built specifically for our hardware - not adapted from a GPU-first framework - is a durable edge, and you're the person who proves that out in production.
What You'll Do:
Own the inference serving stack end-to-end. Design and build the system that takes a bring-up-verified model and serves it in production: request routing, batching, scheduling, and autoscaling a single model's serving replicas.
Push cost-per-token down. Continuously tune batching strategy, KV-cache handling, and hardware utilization to widen the throughput advantage over GPU-based serving.
Build for reliability from day one. Put in place the monitoring, alerting, and failover that make a fast-moving inference stack trustworthy under real customer load - and be the one who responds when it isn't.
Work at the boundary with the compiler and bring-up team. Define the interface between "a model is correct and compiled" and "a model is live and fast," and push issues back to the right side of that line.
Shape the roadmap, not just the backlog. As a founding engineer, you'll help decide what we build next in serving - multi-tenant isolation, speculative decoding, new scheduling strategies - not just execute a spec someone else wrote.
Set the technical bar for the team you're helping build. Early architecture and code-quality decisions you make here will shape how the serving team operates as it grows.
What We Need From You:
5+ years building and operating production systems at the infrastructure layer, ideally including a high-throughput or low-latency serving system.
Direct experience with LLM inference serving - request batching, KV-cache management, continuous batching, or similar - in a production environment, not just research code.
Comfortable owning reliability: you've been on call for a system that mattered, and you design for failure rather than reacting to it after the fact.
Strong systems fundamentals - concurrency, networking, scheduling - deep enough to reason about performance at the hardware level, not just the application level.
Self-directed and comfortable with ambiguity. This is a founding role: there's no existing playbook to follow, and you'll help write it.
Nice-to-Haves:
Experience serving models on non-NVIDIA accelerators (TPU, Trainium/Inferentia, Tenstorrent, Groq, Cerebras, or similar).
Familiarity with serving frameworks such as vLLM, TGI, TensorRT-LLM, or SGLang, and an opinion on where they fall short.
Experience running infrastructure at a small company or in a founding/early-engineer capacity before.
Exposure to capacity planning or fleet management for specialized hardware.
