Member of Technical Staff, DevOps
No longer in the current catalog. Last included 2026-09-09. Check the employer’s posting for availability.
Technologies
Pulumi · Terraform · ArgoCD · GitHub Actions · Kubernetes · EKS · Go · TypeScript · Docker · canary-manager
About Vapi
API platform for developers to build, test, and run production voice AI agents across phone and web channels with flexible model, telephony, and workflow control.
Series A · 50–100 people
Job description
The full responsibilities and requirements are on the employer’s site.
Open application page ↗Source and classification
Internal deployment & tooling · Evidence for this classification:
Vapi (/ˈVɑːpi/): Voice AI that resolves, not transfers Powering 1 billion calls for companies like Amazon Ring, Intuit, ServiceTitan, and New York Life Trusted by 1 million developers building the future of voice agents Backed by Peak XV, Bessemer, Kleiner Perkins, M12, Y Combinator, and more with $72M raised Try talking to Vapi now! Why We’re Hiring This Role: 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
More from the job description
Vapi (/ˈVɑːpi/): Voice AI that resolves, not transfers Powering 1 billion calls for companies like Amazon Ring, Intuit, ServiceTitan, and New York Life Trusted by 1 million developers building the future of voice agents Backed by Peak XV, Bessemer, Kleiner Perkins, M12, Y Combinator, and more with $72M raised Try talking to Vapi now! Why We’re Hiring This Role: 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. What You’ll Do: 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 to [... source excerpt omitted ...] th Infra and SRE on cell creation, multi-region rollouts, and oncall tooling. Who You Are: 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
Employer postings · Data from · Sources