Member of Technical Staff, Infrastructure Engineer

Why this Role:

• Vapi’s real-time voice platform depends on core infrastructure across compute, storage, networking, and telephony. As usage grows, reliability has to be designed into the systems our customers depend on.

• We’re adding a dedicated SRE profile to our five-person Infrastructure team. We need a software-first engineer who can build tooling and automation, improve observability, and turn operational lessons into lasting engineering improvements.

• This role has a distinct focus from our broader Infrastructure Engineer role because it requires deep reliability and operability judgment. You’ll join a calibrated team and work on latency-sensitive systems at meaningful scale. This role is based in San Francisco.

What You’ll Do:

• 30 Days: Learn Vapi’s architecture, production environment, incident history, and reliability practices. Build context with the Infrastructure and product engineering teams, then contribute an initial operational or reliability improvement.

• 60 Days: Own a reliability workstream across observability, incident response, capacity, performance, or production automation. Reduce manual work and improve how the team detects, understands, and responds to failures.

• 90 Days: Become the go-to owner for a meaningful part of Vapi’s reliability surface. Deliver a durable improvement to failure prevention or recovery, and propose a roadmap for the next reliability investments.

Who You Are:

• You are a senior or staff-level software engineer with meaningful SRE, production engineering, or infrastructure experience in distributed systems.

• You write production-quality software and have built reliability tooling or automation yourself, rather than relying only on operational process.

• You have deep experience with observability, incident response, failure analysis, capacity, and the practices that keep production systems healthy.

• You are comfortable with Kubernetes, networking, and cloud infrastructure, and you can debug across application and infrastructure boundaries.

• You reason clearly about failure modes and can balance reliability investments with product and engineering velocity.

• Experience with real-time networking or telephony, Envoy, Postgres, Redis, Kafka, Aurora, ClickHouse, or a Google-style SRE environment is a strong plus.