Synced from Ashby · May 21

Infrastructure Engineer

VapiSan FranciscoPosted May 21, 2026
Infrastructure EngineerOn-siteSenior
Apply now - freeSave & get alerts

Mirrored from Vapi's own Ashby careers system · refreshed hourly

34
Other open Vapi roles
May 21
Posted
Ashby
Applicant system
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:

  • Vapi runs live phone calls — when something breaks, callers hear it. We’re building cell-based, multi-region infrastructure to drive 99.99% call completion, and this hire owns the foundation: multi-cluster Kubernetes on EKS, a stateful data plane (Postgres, Redis, Kafka, Temporal, ClickHouse), Envoy/Cilium networking, and multi-region Kafka on MSK across EU and ANZ.

  • You’ll write Go for control-plane services like cluster-manager, traffic-control-plane, and environment-manager, and you’ll set the bar for how Vapi runs stateful workloads at scale.

What You’ll Do:

  • 30 Day: Ramp on the cell-based architecture, the regional EKS clusters (backend / networking / persistence / monitoring / models / kafka), and the Pulumi stacks. Shadow oncall, walk recent incidents (Envoy response flags, conntrack drops, cross-zone LB target resets), and own a first scoped infra change end-to-end.

  • 60 Day: Take ownership of one core domain — e.g., multi-region MSK (regional topic naming, Pulumi drift, compliance constraints), the Postgres/Neon consolidation path, or programmatic cluster creation via Cluster API. Ship a control-plane improvement in Go and drive a measurable reliability or capacity win.

  • 90 Day: Lead a roadmap pillar of the cell-based build-out: a new region, a stateful workload migration, or unblocking the SIP gateway SPOF. Operate as the infra owner other teams pull in for design reviews, and set the standards (runbooks, failure-domain modeling, capacity targets) the next infra hires inherit.

Who You Are:

  • You’ve run multi-cluster Kubernetes on EKS in production — backend, networking, persistence, monitoring, models, and kafka clusters per region — and you’ve used Cluster API or similar for programmatic cluster creation.

  • You’ve operated a stateful data plane (Postgres, Redis, Kafka, Temporal, etcd, ClickHouse) at scale — you’ve sharded it, migrated data between instances, and lived with the consequences.

  • You’re fluent in Envoy and Cilium/eBPF. You’re comfortable debugging Envoy response flags, conntrack drops, and cross-zone LB behavior. VPC/NAT/Cloudflare alone isn’t enough.

  • You’ve run multi-region Kafka on MSK in production — not just Kafka. You’ve dealt with regional topic naming, MSK Pulumi drift, and compliance constraints.

  • You write Go for control-plane services. Vapi’s cluster-manager, traffic-control-plane, and environment-manager are all Go, and you’re comfortable owning code in that stack.

  • Bonus: SIP / RTP / telephony background. The Nov 7 SIP gateway SPOF is still unsolved, and a telephony-savvy infra hire unblocks that roadmap item.

  • Bonus: cell-based / shard architecture experience — Shopify pods, AWS cell-based reference arch, Slack shards, or equivalent. Microservices experience alone isn’t the same.

  • You likely come from one of: a company that ran cell-based in prod (Shopify, AWS service teams, Slack); a distributed systems shop (Cockroach, MongoDB, Confluent, Temporal, Redpanda, ClickHouse Inc.); a voice/video/CPaaS company (Twilio, Plivo, Bandwidth, Vonage, LiveKit, Daily.co, Dialpad); an Envoy/service-mesh org (Lyft, Stripe, Airbnb, Pinterest, Isovalent/Cilium); or a streaming-infra team (Confluent, Uber, LinkedIn, Datadog) that ran MSK/Kafka multi-region.

Why Vapi:

  • Generational impact: Build the human interface for every business

  • Ownership culture: 70% of the company are previous founders

  • Kind team: The founders, Jordan and Nikhil, are Canadians

  • Tier-1 Investors: YC, KP seed, Bessemer Series A

What We Offer:

  • Real stake: We offer a competitive salary and excellent equity ownership

  • Comprehensive health coverage: medical, dental, and vision plans

  • Team love: We love hanging out, and we do quarterly off-sites

  • Flexible time off: take what you need

  • More: catered meals, transportation, gym, and a $10k annual L&D budget

View original posting on Ashby

What applying to Vapi usually looks like

Based on publicly available information, candidates applying through ashby for roles at Vapi can generally expect an online application involving a resume submission and possibly some role-specific questions. The process may include multiple stages, such as an initial recruiter or talent team screen, followed by hiring manager conversations, and potentially technical or role-specific assessments depending on the position, such as engineering, sales, or design tasks. Some roles may also involve panel interviews or take-home exercises. Communication is typically handled through the ashby platform, which may send automated updates regarding application status. Response times vary and can depend on the volume of applicants and the specific team hiring. Candidates should typically be prepared to discuss their relevant experience, motivations for applying, and alignment with the role's requirements throughout the various stages.

Based on publicly available information. LandEarly does not verify interview process details.

Land this one early - before the req fills.

LandEarly tailors your resume and screening answers to each posting, submits within minutes of a role going live, and tracks every application in one place.

Free to start · No credit card · Cancel anytime

Keep exploring

What this role pays, where else it is open, and how to write the application.

Infrastructure Engineer
Vapi · San Francisco
Apply