Member of Technical Staff, Forward Deployed
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions.
We need to parse the posting.
Let's extract sections:
- About the role: The "Why We're Hiring This Role" paragraph(s) describing growth, need for FDE, etc. Also maybe "What You'll Do" and "What You'll Own" could be responsibilities.
- Responsibilities: "What You'll Do" (30/60/90 day) and "What You'll Own" bullet list.
- Requirements/Qualifications: "Who You Are" and "What We're Looking For" (experience, skills). Also "Hard Skills" list.
- Skills: maybe separate "Hard Skills" and "Nice to Have".
- Benefits: "What we offer" bullet list: Real stake, Comprehensive health coverage, Team love, Flexible time off, More: Catered meals, transportation, gym, $10k L&D budget.
- Pay: "Compensation Range: $200K - $280K". Also maybe "Real stake: Competitive salary and excellent equity ownership". So we can include Pay section with compensation range.
- Schedule: Not mentioned. So we should not include Schedule.
- Also maybe "About Vapi" description at top: "Vapi (/ˈVɑːpi/): Voice AI that resolves, not transfers..." That's company description; could be part of About the role? But the instruction: Use headings for sections like About the role, Responsibilities, etc. The top blurb is more about company; could be considered "About the role" or maybe we can include as part of About the role. However we must not repeat job title. The job title is likely "Field Deployment Engineer" or similar? Not explicitly given but implied. We'll not include.
We must not include boilerplate like "Backed by Peak XV, Bessemer..." etc? That's part of company description; maybe we keep as part of About the role? It's substantive info about company backing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The backing info is not boilerplate; it's substantive. So we can keep.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "Enterprise ARR has grown 10x", etc.
We need to format using for section headings, - for any list of duties/requirements/benefits, and
for prose.
We must not emit a heading followed by filler/placeholder text. So only include sections with real content.
Let's craft sections:
- About the role: combine company description and why hiring. Could be multiple paragraphs.
- Responsibilities: include "What You'll Do" (30/60/90 day) and "What You'll Own". Could be a combined list or separate paragraphs.
- Requirements: include "Who You Are" and "What We're Looking For" (experience, etc.) plus maybe "Hard Skills" as a list.
- Skills: maybe separate "Hard Skills" and "Nice to Have". But we could incorporate Hard Skills under Requirements; Nice to Have as separate Skills section.
- Benefits: "What we offer" list.
- Pay: compensation range.
We must not include Schedule.
Let's extract exact text.
Company description:
"Vapi (/ˈVɑːpi/): Voice AI that resolves, not transfersPowering 1 billion calls for companies like Amazon Ring, Intuit, ServiceTitan, and New York LifeTrusted by 1 million developers building the future of voice agentsBacked by Peak XV, Bessemer, Kleiner Perkins, M12, Y Combinator, and more with $72M raisedTry talking to Vapi now!"
That seems like a run-on; but we keep as is.
Why We're Hiring This Role:
"This Role 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."
What You'll Do:
"30 Day: Deploy an Enterprise customer end-to-end
60 Day: Ship internal tooling or product contributions that make the next similar deployment materially faster
90 Day: Establish a process or infrastructure the team didn't know it needed"
What You'll Own:
"Lead deployment engagements end to end for assigned enterprise customers, from scoping through go-live and handoff
Build production-ready Vapi deployments (assistants, squads, tools, structured outputs, telephony/SIP, webhooks, integrations)
Debug live production issues across call records, app logs, provider request/response, and infra metrics
Own customer-facing GitOps repos and dedicated cluster configuration
Manage technical and executive stakeholders across technical and non-technical audiences
Build platform work that removes deployment toil: outbound campaigns, evals and simulations, observability, CLI and MCP tooling
Feed deployment insight back into the product roadmap"
Who You Are:
"You've worked in a technical role at an early-stage startup — you know what it means to build without a playbook
You've been an FDE, Solutions Architect, or Solutions Engineer at a company we admire
You've driven process change proactively — not because someone asked, but because you couldn't leave a broken system alone
You're comfortable operating in ambiguity and find structure by doing, not by waiting
You have a genuine bias toward action: you identify a gap, you fix it, you document it
Bonus: You've built your own startup or pursued your own projects, and iterated on them"
What We're Looking For:
"5+ years of professional engineering experience
Strong generalist: you can move between UI/UX implementation, API design, data modeling, and systems architecture
Early-stage startup experience — you've worn multiple hats in a scrappy, resource-constrained environment
Can communicate clearly with both technical and non-technical stakeholders
Conceptual understanding of working with AI in production"
Hard Skills:
"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"
Nice to Have:
"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"
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, Kleiner Perkins seed, Bessemer Series A"
What we offer:
"Real stake: Competitive salary and excellent equity ownership
Comprehensive health coverage: Medical, dental, and vision
Team love: We hang out — quarterly off-sites included
Flexible time off: Take what you need
More: Catered meals, transportation, gym, and a $10k annual L&D budget"
Compensation Range: "$200K - $280K"
We need to ensure we don't duplicate content. Also remove duplicated lines: I see some repeated like "Powering 1 billion calls..." etc appears once.
Now produce HTML.
We'll have sections:
About the role
... (company description + why hiring)
Responsibilities
- 30 Day: Deploy an Enterprise customer end-to-end
- 60 Day: Ship internal tooling or product contributions that make the next similar deployment materially faster
- 90 Day: Establish a process or infrastructure the team didn't know it needed
- Lead deployment engagements end to end for assigned enterprise customers, from scoping through go-live and handoff
- Build production-ready Vapi deployments (assistants, squads, tools, structured outputs, telephony/SIP, webhooks, integrations)
- Debug live production issues across call records, app logs, provider request/response, and infra metrics
- Own customer-facing GitOps repos and dedicated cluster configuration
- Manage technical and executive stakeholders across technical and non-technical audiences
- Build platform work that removes deployment toil: outbound campaigns, evals and simulations, observability, CLI and MCP tooling
- Feed deployment insight back into the product roadmap
Alternatively could separate "What You'll Do" and "What You'll Own" but it's okay as list.
Requirements
Who You Are:
- You've worked in a technical role at an early-stage startup — you know what it means to build without a playbook
- You've been an FDE, Solutions Architect, or Solutions Engineer at a company we admire
- You've driven process change proactively — not because someone asked, but because you couldn't leave a broken system alone
- You're comfortable operating in ambiguity and find structure by doing, not by waiting
- You have a genuine bias toward action: you identify a gap, you fix it, you document it
- Bonus: You've built your own startup or pursued your own projects, and iterated on them
What We're Looking For:
- 5+ years of professional engineering experience
- Strong generalist: you can move between UI/UX implementation, API design, data modeling, and systems architecture
- Early-stage startup experience — you've worn multiple hats in a scrappy, resource-constrained environment
- Can communicate clearly with both technical and non-technical stakeholders
- Conceptual understanding of working with AI in production
Skills
Hard Skills
but we only allowed for section headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications,
- for any list of duties/requirements/benefits, and
for prose. We must not emit a heading followed by filler/placeholder text. So only include sections with real content. Let's craft sections: - About the role: combine company description and why hiring. Could be multiple paragraphs. - Responsibilities: include "What You'll Do" (30/60/90 day) and "What You'll Own". Could be a combined list or separate paragraphs. - Requirements: include "Who You Are" and "What We're Looking For" (experience, etc.) plus maybe "Hard Skills" as a list. - Skills: maybe separate "Hard Skills" and "Nice to Have". But we could incorporate Hard Skills under Requirements; Nice to Have as separate Skills section. - Benefits: "What we offer" list. - Pay: compensation range. We must not include Schedule. Let's extract exact text. Company description: "Vapi (/ˈVɑːpi/): Voice AI that resolves, not transfersPowering 1 billion calls for companies like Amazon Ring, Intuit, ServiceTitan, and New York LifeTrusted by 1 million developers building the future of voice agentsBacked by Peak XV, Bessemer, Kleiner Perkins, M12, Y Combinator, and more with $72M raisedTry talking to Vapi now!" That seems like a run-on; but we keep as is. Why We're Hiring This Role: "This Role 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." What You'll Do: "30 Day: Deploy an Enterprise customer end-to-end 60 Day: Ship internal tooling or product contributions that make the next similar deployment materially faster 90 Day: Establish a process or infrastructure the team didn't know it needed" What You'll Own: "Lead deployment engagements end to end for assigned enterprise customers, from scoping through go-live and handoff Build production-ready Vapi deployments (assistants, squads, tools, structured outputs, telephony/SIP, webhooks, integrations) Debug live production issues across call records, app logs, provider request/response, and infra metrics Own customer-facing GitOps repos and dedicated cluster configuration Manage technical and executive stakeholders across technical and non-technical audiences Build platform work that removes deployment toil: outbound campaigns, evals and simulations, observability, CLI and MCP tooling Feed deployment insight back into the product roadmap" Who You Are: "You've worked in a technical role at an early-stage startup — you know what it means to build without a playbook You've been an FDE, Solutions Architect, or Solutions Engineer at a company we admire You've driven process change proactively — not because someone asked, but because you couldn't leave a broken system alone You're comfortable operating in ambiguity and find structure by doing, not by waiting You have a genuine bias toward action: you identify a gap, you fix it, you document it Bonus: You've built your own startup or pursued your own projects, and iterated on them" What We're Looking For: "5+ years of professional engineering experience Strong generalist: you can move between UI/UX implementation, API design, data modeling, and systems architecture Early-stage startup experience — you've worn multiple hats in a scrappy, resource-constrained environment Can communicate clearly with both technical and non-technical stakeholders Conceptual understanding of working with AI in production" Hard Skills: "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" Nice to Have: "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" 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, Kleiner Perkins seed, Bessemer Series A" What we offer: "Real stake: Competitive salary and excellent equity ownership Comprehensive health coverage: Medical, dental, and vision Team love: We hang out — quarterly off-sites included Flexible time off: Take what you need More: Catered meals, transportation, gym, and a $10k annual L&D budget" Compensation Range: "$200K - $280K" We need to ensure we don't duplicate content. Also remove duplicated lines: I see some repeated like "Powering 1 billion calls..." etc appears once. Now produce HTML. We'll have sections:
About the role
... (company description + why hiring)
Responsibilities
- 30 Day: Deploy an Enterprise customer end-to-end
- 60 Day: Ship internal tooling or product contributions that make the next similar deployment materially faster
- 90 Day: Establish a process or infrastructure the team didn't know it needed
- Lead deployment engagements end to end for assigned enterprise customers, from scoping through go-live and handoff
- Build production-ready Vapi deployments (assistants, squads, tools, structured outputs, telephony/SIP, webhooks, integrations)
- Debug live production issues across call records, app logs, provider request/response, and infra metrics
- Own customer-facing GitOps repos and dedicated cluster configuration
- Manage technical and executive stakeholders across technical and non-technical audiences
- Build platform work that removes deployment toil: outbound campaigns, evals and simulations, observability, CLI and MCP tooling
- Feed deployment insight back into the product roadmap
Requirements
Who You Are:
- You've worked in a technical role at an early-stage startup — you know what it means to build without a playbook
- You've been an FDE, Solutions Architect, or Solutions Engineer at a company we admire
- You've driven process change proactively — not because someone asked, but because you couldn't leave a broken system alone
- You're comfortable operating in ambiguity and find structure by doing, not by waiting
- You have a genuine bias toward action: you identify a gap, you fix it, you document it
- Bonus: You've built your own startup or pursued your own projects, and iterated on them
What We're Looking For:
- 5+ years of professional engineering experience
- Strong generalist: you can move between UI/UX implementation, API design, data modeling, and systems architecture
- Early-stage startup experience — you've worn multiple hats in a scrappy, resource-constrained environment
- Can communicate clearly with both technical and non-technical stakeholders
- Conceptual understanding of working with AI in production
Skills
Hard Skills
but we only allowedfor section headings. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications,