Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 37 days ago

Member of Technical Staff - Product Engineering

Runta3 open roles

Pay
$150,000 – $200,000 a year
Where
San Mateo
Work mode
On site
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowMember of Technical Staff - Product EngineeringRunta · San Mateo

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Runta's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

12.4% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 2.1%1 day
  2. 4.5%3 days
  3. 12.4%7 days
  4. 20.0%14 days
  5. 35.5%30 days
  6. 58.6%60 days
This job: posted 37 days ago

The posting

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. 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.

This role decides whether Runta is an impressive piece of infrastructure or a platform people build on. Powerful primitives with a bad interface lose to weaker primitives with a great one. You own the interface.

You’ll be the developer-zero for every capability the runtime team ships: the first person to use it, the person who decides what gets exposed and what stays hidden, and the person who makes the 5-minute quickstart actually take 5 minutes.

WHAT YOU’LL DO

- Design and build Runta’s SDK and CLI: the primary surface through which developers run, snapshot, branch, and replay agents

- Make API design decisions with long consequences: what to expose, what to hide, what to name things

- Build the examples, quickstarts, and reference docs that take a developer from curiosity to a running agent

- Turn runtime capabilities into product language: translating “microVM snapshot semantics” into things agent builders immediately want

- Feel every rough edge first and fix it: error messages, failure modes, onboarding friction

- Represent the developer inside the company: your feedback shapes what the runtime team builds next

THE PROBLEMS YOU’D BE SOLVING

- Branching a running agent is a new primitive with no established mental model. What’s the API shape, and what metaphor makes it click in 10 seconds?

- A resume fails three days after the snapshot was taken. What error message does the developer see, and what can they do about it?

- The runtime exposes 40 knobs. Which 5 belong in the quickstart, which 35 belong behind an escape hatch, and how do you keep the escape hatch from becoming the front door?

- A developer’s first 5 minutes decide whether they come back. What does the ideal zero-to-running-agent path look like, and what’s currently in its way?

If you read those and started sketching answers, we want to talk to you.

WHAT WE’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.

YOU SHOULD GENUINELY CARE ABOUT AI

The developers you serve are agent builders. If you’re one yourself, you’ll know what they need before they file the issue. The best fit is someone who uses AI tools daily, has built things with agents on their own time, and has opinions about why today’s agent frameworks are frustrating.

THIS ROLE IS PROBABLY NOT FOR YOU IF

- Your product experience is primarily end-user web or mobile apps, and developer tools would be a career change rather than a return to form

- You need a PM to hand you specs. Here you’d write them

- You see documentation and error messages as someone else’s job

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.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Runta's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Runta's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Runta's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.