Member of Technical Staff, Forward Deployed

• 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!

Our Enterprise ARR has grown 10x — customers like Amazon Ring, NY Life and Intuit deploy in weeks and expand rapidly when we support them well. Customer deployments now consume most of our current FDE capacity, which means platform roadmap work competes directly with delivery. We're opening more seats this quarter in San Francisco and New York to take on that unowned roadmap work. Steady-state accounts are handing off to our Agent Engineering team so FDEs can return to building the platform, not just running it.

Unlike a solutions engineer, an FDE ships code: into customer repos, into Vapi's GitOps configs, and into the Vapi platform itself.

This isn't CRUD engineering. You're building real-time, latency-sensitive systems that orchestrate multiple providers — speech-to-text, LLMs, text-to-speech, telephony — simultaneously, in production, at enterprise scale. It's the kind of systems problem most engineers only get to touch on infra teams at much larger companies, and you'll own it end to end.

• →
  • →

    Backend: Node.js, Express, FastAPI, Django, or Flask

  • →

    Frontend: React, Next.js, Vue, or Tailwind

  • →

    Language: TypeScript or Python

  • →

    Database: SQL, MongoDB, DynamoDB, or Redis

  • →

    Deployment: AWS, GCP, Azure, Vercel, or Railway

  • →

    Coding Tools: Cursor, Claude Code, Codex, or Windsurf

• AI/ML: LLM APIs, RAG, vector databases (Pinecone, pgvector), self-hosted models

• Infra: Docker, Kubernetes, IaC

• Real-time: WebSockets, SSE, WebRTC, SIP

• Led a project without a management title

• Open source contributions

• Has shipped at least one product with real users — at least one of the following should be easy to verify:

  • Product with 1,000+ active users

  • Product generating revenue from paying customers

  • Product a real company depended on to run part of their operations

• 1+ year as a founding or early engineer (first 10) at a startup that raised Series A or beyond

• 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, Kleiner Perkins seed, Bessemer Series A