What are the responsibilities and job description for the Member of Technical Staff, DevOps position at Vapi?
Voice AI that resolves, not transfers.
Most phone systems trap callers in menus and scripts. Vapi is the platform for deploying voice agents that know your business and can listen, adapt, and resolve in minutes.
Must-haves
Most phone systems trap callers in menus and scripts. Vapi is the platform for deploying voice agents that know your business and can listen, adapt, and resolve in minutes.
- The numbers: 1 billion calls. 1 million developers. 10x enterprise ARR growth
- The customers: Amazon Ring, ServiceTitan, New York Life, Intuit, Kavak, and thousands more, from YC startups to the Fortune 500
- The news: a $50M Series B led by Peak XV Partners, with Bessemer Venture Partners, Kleiner Perkins, M12 (Microsoft's Venture Fund), Y Combinator, and our earlier backers. Total raised: $72M
- Three of our worst recent incidents — Nov 29 config rollout, Dec 23 duplicate messages, Oct 13 egress proxy — were resolved by rollback. That’s the SDLC gap this role closes. Vapi engineers are your users, and the deploy pipeline, preview environments, cell-creation tooling, and oncall tooling are products with SLAs, docs, and feedback loops.
- You’ll own progressive delivery (canary, blue/green, automated rollback, soak periods), the GitOps story across multiple clusters and regions, and the on-demand environment tooling that’s on the Q3 roadmap. Success is measured by how fast every other team ships safely.
- 30 Day: Get fluent in the Pulumi stacks, the ArgoCD setup, and GitHub Actions pipelines. Sit with engineers from agents and FDE teams to find the top 3 deploy pain points. Land a quality-of-life improvement to the deploy pipeline.
- 60 Day: Own progressive delivery end-to-end — canary, automated rollback, soak — for at least one critical service path. Ship the first version of cell-creation tooling or preview environments. Make the deploy pipeline measurably faster (lead time, MTTR for failed deploys).
- 90 Day: Roll out progressive delivery as the default across services. Establish SLAs and a feedback loop with engineering teams. Own the developer-platform roadmap and partner with Infra and SRE on cell creation, multi-region rollouts, and oncall tooling.
Must-haves
- You have a platform-as-a-product mindset — you treat internal engineers as customers, with SLAs, docs, and feedback loops, not tickets and ad-hoc help.
- You’ve operated Pulumi (TypeScript) or Terraform at scale (40 stacks, multi-region) and you’ve felt the pain when IaC sprawl gets ahead of you.
- You’ve run ArgoCD or equivalent GitOps for deploying applications across multiple clusters.
- You’ve built progressive delivery in production — canary, blue/green, automated rollback, soak periods. You can describe a real rollout that automated rollback caught.
- You’ve designed CI/CD pipelines (GitHub Actions preferred) for many services and Dockerfiles, not just one repo.
- You’ve built deploy tooling for on-demand environments — preview envs, dev deployments, or cell creation.
- You’ve written Go for platform services (Vapi’s canary-manager is Go).
- You’ve operated developer platforms at a mid-stage infra-heavy company or a DevEx team at a larger shop.
- Languages: TypeScript (primary, for Pulumi and tooling), Go (for canary-manager and platform services), Bash.
- IaC: Pulumi (TypeScript) at scale (40 stacks across regions), Terraform.
- GitOps and deploy: ArgoCD (multi-cluster), GitHub Actions, 15 Dockerfiles.
- Progressive delivery: canary, blue/green, automated rollback, soak periods (canary-manager Go service).
- Orchestration: Kubernetes on EKS (multi-cluster, multi-region).
- Vapi services you’ll touch: canary-manager, cell-creation tooling, preview env tooling.
- Vercel, Render, Railway, Fly, Temporal, Cockroach (mid-stage infra-heavy), or DevEx/Platform teams at Stripe, Shopify, Airbnb, or Block.
- Weak fit: classic AWS sysadmin, or someone whose CI/CD experience is mostly Jenkins GUI-level.