Runta
Runta

Member of Technical Staff - Product Engineering (Enterprise)

$150–200kSan Mateo, CAOn-siteSeniorFull-time

Posted 8 days ago

The role in short

Embeds with enterprise customers' agent and infra teams to get their long-running agents into production on Runta, building the integrations they need.

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.

Prep for this interview

4 questions likely to come up at Runta, each matched to a line in this posting.

  1. 1Integrations and APIs
    They wrote: “Build what accounts need to adopt Runta and stay: integrations, storage and signal interfaces, secrets and access controls, audit and compliance surfaces.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  2. 2LLMs, RAG and agents
    They wrote: “Runta builds runtime infrastructure for long-running AI agents: efficient execution, enforceable access controls, and complete execution records.”

    When would you use an agent that takes actions, and how do you keep it safe?

    How to answer

    Why they ask: Agent work is growing fast in FDE postings. Senior candidates are expected to know where agents fail.

    1. Use agents for multi-step tasks with clear success checks; avoid them where one wrong action is costly
    2. Give the agent narrow tools and permissions, not broad access
    3. Require human approval for risky actions
    4. Log every step so the customer can audit it

    Tip: Start from the cost of a wrong action. Limit what the agent can do, and log everything.

  3. 3Cloud, deployment and security
    They wrote: “Nice to have: forward-deployed or solutions engineering at a devtools or infra company, experience with enterprise security reviews.”

    The customer's security team sends a 200-question review. How do you handle it?

    How to answer

    Why they ask: Security reviews often block deals. FDEs help get through them.

    1. Start from your company's standard answers (SOC 2 report, past reviews)
    2. Answer clearly; don't oversell
    3. Bring in your security team for anything you're unsure of
    4. Keep the new answers for the next customer

    Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.

  4. 4Ownership and working with customers
    They wrote: “We’re a small, well-funded team based in the San Francisco Bay Area and Singapore. High talent density. High ownership.”

    Tell me about something you shipped that broke in production.

    How to answer

    Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.

    1. What broke and who it affected
    2. How you found out and what you did in the first hour
    3. The root cause, said plainly
    4. What you changed so it can't happen the same way again

    Tip: Pick a real one with a cost. Spend most of the answer on what you changed.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

Runta

$150–200k · On-site

Apply