Runta cuts what agents waste, bounds what they can reach, and records everything they did. Backed by a16z.
About the role
Our runtime team builds the engine. Our infrastructure team makes it scale. You decide what it feels like to use. Runta does three things: run, govern, record. Underneath, that’s microVMs, snapshot graphs, and audit machinery. Your job is to make sure developers never have to think about any of that. They should think “I can pause my agent, branch it into three versions, and resume the best one,” and the SDK, CLI, docs, and examples you build are what makes that thought possible.
What they're looking for
- You’ve built developer-facing product surfaces: an SDK, a CLI, a public API, or a devtools product people chose to use
- Exceptional API taste, with opinions you can defend about what to expose, what to hide, and what to name things
- You write clearly. Docs, examples, and error messages are product surfaces here, not chores
- You can read the systems underneath: you don’t need to build a hypervisor, but you need to understand what one is, so your abstractions don’t lie
- You genuinely enjoy solving user problems and get satisfaction from someone else’s “oh, that was easy”
- Nice to have: open source maintainership with a reputation for good DX, developer advocacy or technical writing experience, experience building with AI agents or LLM APIs
More about this role
Runta builds runtime infrastructure for long-running AI agents: efficient execution, enforceable access controls, and complete execution records.
We’re a small, well-funded team based in the San Francisco Bay Area and Singapore. High talent density. High ownership.
Runta builds runtime infrastructure that lets AI agents execute reliably over long time horizons: run agents efficiently, govern what they can reach, and record what they did. Workloads that run for hours or days break the assumptions web infrastructure is built on. An agent can fan out fifty sub-tasks in a second and then go idle for ten minutes, must survive instance recycling mid-run, and needs to snapshot, resume, and branch its execution state the way developers branch code. We’re building the substrate that makes this possible.
We’re a small, well-funded team, moving fast.
Our runtime team builds the engine. Our infrastructure team makes it scale. You decide what it feels like to use.
Runta does three things: run, govern, record. Underneath, that’s microVMs, snapshot graphs, and audit machinery. Your job is to make sure developers never have to think about any of that. They should think “I can pause my agent,...
Browse similar: Startup jobs · San Francisco Bay Area