Member of Technical Staff, QA

Requisitos y responsabilidades

Contenido del rol extraído en secciones para revisar más rápido.

Details

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
Build and deploy real assistants on Vapi, run live calls and simulations across our main provider integrations (LLMs, STT, TTS, telephony), and break the product in at least a few interesting ways.
Get up and running in our existing e2e test framework and ship your first Playwright tests against the dashboard.
File bugs that engineers fix, and develop a working point of view on where our coverage is weakest.
Own release testing for at least one major product area (assistant builder, simulations, monitoring, knowledge base, or versioning), and earn engineers' trust to gate it.
Meaningfully improve automated coverage in your area.
Partner with engineers on test strategy for new features before they ship.
Use AI coding agents to multiply your throughput on test scenarios and regression coverage.
Operate as a full peer to engineers on the team, owning QA across the product surface without handholding.
Extend our testing practices and contribute patterns the rest of the team picks up.
Be involved in new features from the start, with the automation suite meaningfully larger on your watch.

Why We’re Hiring This Role:

Vapi is the platform enterprises use to build production voice agents, and our product surface is expanding fast to support the next billion calls.
We're hiring our first dedicated QA Engineer on the product team to own end-to-end quality across that surface.
This is a real ownership role: you'll work on the cutting edge of AI, define how we test a non-deterministic product, partner directly with engineers on a small team, and have outsized impact on what our customers experience every day.

What You’ll Do:

First 30 Days:Build and deploy real assistants on Vapi, run live calls and simulations across our main provider integrations (LLMs, STT, TTS, telephony), and break the product in at least a few interesting ways.Get up and running in our existing e2e test framework and ship your first Playwright tests against the dashboard.File bugs that engineers fix, and develop a working point of view on where our coverage is weakest.
Build and deploy real assistants on Vapi, run live calls and simulations across our main provider integrations (LLMs, STT, TTS, telephony), and break the product in at least a few interesting ways.
Get up and running in our existing e2e test framework and ship your first Playwright tests against the dashboard.
File bugs that engineers fix, and develop a working point of view on where our coverage is weakest.
By 60 Days:Own release testing for at least one major product area (assistant builder, simulations, monitoring, knowledge base, or versioning), and earn engineers' trust to gate it.Meaningfully improve automated coverage in your area.Partner with engineers on test strategy for new features before they ship.Use AI coding agents to multiply your throughput on test scenarios and regression coverage.
Own release testing for at least one major product area (assistant builder, simulations, monitoring, knowledge base, or versioning), and earn engineers' trust to gate it.
Meaningfully improve automated coverage in your area.
Partner with engineers on test strategy for new features before they ship.

Who You Are:

5+ years in QA, SDET, Test Engineering, or product engineering with a strong testing focus.
Hands-on with at least one modern e2e framework — Playwright preferred; Cypress, Selenium, or equivalent are fine.
Comfortable reading and writing TypeScript / JavaScript well enough to extend our test suite and file bugs with a hypothesis attached.
Track record testing complex, distributed systems with real failure modes — APIs, integrations, real-time behavior, anything where "correct" isn't a fixed string.
Daily use of AI coding agents (Claude Code, Cursor, or similar) with opinions about where they help and where they don't.
Self-directed: you read the PR, open the product, and start finding what's broken without waiting for a spec.
Strong written communication, especially in bug reports and test plans.
Customer empathy and a bias for action: you ship, you own outcomes, and you care what users actually experience.

Who You Are:

Background in voice AI, conversational AI, LLM applications, or telephony.
Experience with LLM evals or testing non-deterministic systems.
Worked on a developer-facing product — APIs, SDKs, dashboards — where the audience is technical.
Early-stage startup experience; comfortable with ambiguity and shifting priorities.
Open-source contributions or public writing on testing, evals, or QA practice.