Member of Technical Staff - Product Engineering (PLG)

Build the execution layer for the agent era.

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.

About Runta

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.

The Role

Our runtime team builds the engine. You get developers to pick it up on their own, keep using it, and tell other people about it.

Runta runs, governs and records long-running agents. Underneath that are microVMs, snapshot graphs and audit machinery. Your job is to make sure an agent builder who finds us on X or GitHub gets an agent running in five minutes and comes back the next day. You own the self-serve path from first visit to paying user: the SDK, the CLI, the quickstart, the examples, and the public story around them.

What You’ll Do

• Build and keep improving the SDK, CLI, quickstarts and templates developers use to run, snapshot, branch and replay agents.

• Find the scenarios where Runta clicks for an individual developer, then turn them into demos and starter projects.

• Ship integrations with tools agent builders already use, and use them for co-marketing.

• Build in public: write posts, record demos, and share what you learn on X, LinkedIn, Reddit and GitHub.

• Maintain open source projects around Runta and respond to the community that forms around them.

• Watch activation and retention, find where people drop off, and fix it.

The Problems You’d Be Solving

• We have hundreds of sign-ups and very few active users. What's breaking between sign-up and a running agent?

• Branching a running agent is a new primitive. What demo makes it click in 10 seconds?

• What should a developer get for $5 a month, and what makes them upgrade?

What We’re Looking For

• You've built something developers chose to use, like an SDK, a CLI, a devtool or an open source project, and you kept maintaining it after launch.

• You have a real public presence. You write, post and ship in the open, and people follow you for it (roughly 1K+ followers on at least one platform).

• Builder mindset: you'd rather ship a demo tonight than write a plan about it, and you change it based on what users say.

• Strong API and DX taste, and clear writing. Docs and error messages are product here.

• You don't need deep infra experience, but you need to understand what's underneath well enough that your abstractions don't lie.

• You build with AI agents every day and have opinions about what's frustrating about today's frameworks.

Nice to have: Developer advocacy or technical content that people actually shared, growth or activation experiments, new grads with a strong public building record.

This Role Is Probably Not for You If

• You've never shipped something people outside your company use.

• You don't want to write or post in public.

• You need a PM to hand you specs.

How We Work

Small team, high trust, high ownership. We value people who are hungry, humble, and sharp. We look for clear communicators who hold strong opinions loosely and use AI-native workflows in their daily engineering. You’ll work directly with the founder, alongside the core runtime and isolation teams.