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

Open nowPosted 40 days ago

Member of Technical Staff - Cloud Infrastructure

Runta3 open roles

Pay
$150,000 – $250,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 - Cloud InfrastructureRunta · 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 40 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 execution engine. You build the cloud platform it runs on: the production infrastructure that serves paying customers. You are the person accountable for it working, scaling, and not bankrupting us.

Runta does three things: run, govern, record. This role makes run economical at scale, gives record a storage layer that’s cheap at volume and fast on restore, and owns the network boundaries that make govern enforceable in production. You decide ECS vs. EKS, when Spot instances make sense, how snapshot storage should be tiered, and what the architecture costs at 10x load.

You’ll also own the infrastructure-as-code layer that makes our platform reproducible and portable. Writing Terraform is table stakes here. The job is designing modules other engineers consume, managing state at scale, and building abstractions that keep multi-cloud on the table without over-engineering for it today.

This is an ownership role, not a support role. The infrastructure layer is part of the product: customer-facing, versioned, reproducible.

WHAT YOU’LL DO

- Design and operate Runta’s production infrastructure on AWS: compute, networking, storage, observability

- Own the IaC layer: Terraform modules, state management, CI/CD for infrastructure changes

- Design cross-cloud abstractions that don’t lock us into a single provider

- Own the infrastructure side of snapshot/resume/branch: snapshot graph storage, control plane / data plane separation, local ↔ cloud state consistency

- Make cost-aware architecture decisions: instance strategy, Spot fleet design, storage tiering, rightsizing

- Shape the infrastructure roadmap as an early technical leader, working directly with the founder

THE PROBLEMS YOU’D BE SOLVING

- A workload runs anywhere from 2 seconds to 2 hours, unpredictably. How do you size, schedule, and price the fleet under it?

- Agents checkpoint constantly. Snapshot storage must be cheap at petabyte volume but restore in seconds. What’s the tiering design?

- An agent job fans out 50 concurrent sub-tasks, then the whole fleet goes idle for 10 minutes. Autoscaling policies tuned for web traffic fall over. What replaces them?

- Agents retry non-deterministically on failure. Where must the infrastructure itself be idempotent, and where is eventual consistency a silent-corruption risk?

- The same platform needs to deploy identically across environments, and someday across clouds. What do you abstract, and what stays provider-specific?

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

WHAT WE’RE LOOKING FOR

- You’ve designed and operated production AWS infrastructure you were accountable for, not just worked within someone else’s

- Deep Terraform (or equivalent IaC) experience: complex modules built for other engineers to consume, state management at scale, infra CI/CD

- Multi-cloud or cross-cloud experience: provider-spanning abstractions, workload migrations, or internal platforms built on IaC

- Experience running serverless or container platforms at scale (Lambda, Fargate, ECS, EKS)

- A cost-optimization track record you can talk through in specifics: RI strategy, Spot fleet design, rightsizing with real numbers

- Solid distributed systems fundamentals: consistency models, replication, consensus

- You understand orchestration platforms at the why level, not just the kubectl level

Nice to have: background in AI/ML infrastructure, agent frameworks, or LLM serving.

YOU SHOULD GENUINELY CARE ABOUT AI

Our customers are AI builders. The decisions you make (cold-start latency, snapshot frequency, concurrency limits) determine what AI products are possible to build on Runta. The best fit is someone who already uses AI tools daily, tinkers with agents on their own time, and has real curiosity about where agentic systems are going. If AI is “just another workload” to you, this probably isn’t the right role.

THIS ROLE IS PROBABLY NOT FOR YOU IF

- Your infrastructure experience is primarily operating clusters others designed

- Your orchestration background is enterprise application workflow (BPMN, Spring-based orchestration) rather than execution infrastructure

- You’re looking for a role where the architecture is already settled and the job is keeping it running

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.