Member of Technical Staff - Cloud Infrastructure

• 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

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

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

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.

• 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

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.

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.