Member of Technical Staff - Product Engineering, Enterprise

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 make it work inside real companies.

You own Runta's relationship with our design-partner and enterprise accounts from the engineering side. You sit with the customer's agent and infra teams, figure out what they actually need, decide which requests are worth building, and ship it. You act as your own PM, and what you learn shapes what the runtime team builds next.

What You'll Do

• Work directly with customer engineering teams to get their agents running on Runta in production.

• Judge which customer requests are reasonable and turn the right ones into product, not one-off hacks.

• Build what accounts need to adopt Runta and stay: integrations, storage and signal interfaces, secrets and access controls, audit and compliance surfaces.

• Debug production issues across the customer's stack and ours.

• Help shape a repeatable process from first technical call to production rollout.

• Bring the customer's view back into the team and push for it.

The Problems You'd Be Solving

• A customer wants every agent to reach their internal Vault. Is that a feature, an integration, or a sign we've got the product wrong?

• An agent fails in the customer's environment but not in ours. Where do you look first?

• Five accounts ask for five different things. Which one becomes a product?

What We're Looking For

• You've built internal infra or platform products for engineering teams at a mid-size or large company, or you were a founding engineer who did that work.

• Deep infra understanding: containers, scheduling, networking, identity and access, observability.

• You can talk to a customer's staff engineer as a peer and say no when a request doesn't make sense.

• You've been the buyer. You've run an internal platform, or built an AI app or infra company that didn't make it, and you know why tools get adopted or dropped.

• You write clearly and act as your own PM.

• You build with AI agents and understand what breaks when they run for hours.

Nice to have: forward-deployed or solutions engineering at a devtools or infra company, experience with enterprise security reviews.

This Role Is Probably Not for You If

• You want to stay heads-down and never talk to customers.

• You'd rather take requests than push back on them.

• Your experience is mostly end-user web or mobile apps.

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.