Technical Writer at Vapi

San Francisco, California, United States -

Full Time

Start Date

Immediate

Expiry Date

20 Jun, 26

Salary

185000.0

Posted On

22 Mar, 26

Experience

2 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

Skills

Product Information Management, Documentation Drift Management, API Usage, Webhook Knowledge, POST Request Understanding, LLM Knowledge, Technical Writing, Clarity in Writing, Accuracy Verification, Developer Journey Friction Reduction, Support Volume Reduction, Activation Improvement

Industry

Software Development

Description

Vapi (/ˈVɑːpi/): We’re creating the shift to voice as humanity’s default interface We’re the most configurable platform for deploying voice agents We’ve grown to over 600k developers in two years, adding 2,000+ every day Try talking to Vapi now! Why We’re Hiring This Role: We are not looking just for a technical writer. We need someone who can manage product information for us. We ship fast. Fast enough that last month's docs might be actively lying to you today. We need someone who treats documentation drift like a production incident. Our support team troubleshoots customer issues using docs our developers use. Our in-product AI agent relies on those same documents. When docs are wrong, support is slow, customers are frustrated, and engineers get pulled into explaining things that should already be written down somewhere. We have genuinely complex concepts. The developer who gets it on the first read builds something great and tells their friends. The developer who doesn't, churns and tells their friends. This role reports directly to the VP of Product. Documentation isn't a nice-to-have at Vapi, it is a critical part of our product experience. AI can write docs. It can't verify them. It knows the job conceptually, it's never lived it. We use AI here and we trust and verify everything it touches. That last part needs you. What You’ll Do: 30 Day: Become dangerous on the Vapi platform. Actually build something. Actually break something. Read every doc we have and form an honest opinion about the state of it. Find the three questions developers ask most. Answer them so well they stop asking. Make friends with the support team. They know where the bodies are buried. Write your first doc. Ship it. Get feedback. Improve it. 60 Day: Own developer-facing docs end to end: API references, quickstarts, guides, tutorials, Knowledge base, FAQs, the works. Build a system for keeping docs current as the platform ships. A system that works when engineers forget to tell you something has changed. Make a new developer's first 30 minutes noticeably better than they were when you arrived. Then make it better again. Give the support team and Vapi Composer something amazing to work with. Make it so they stop guessing. Bonus points if you make them laugh. 90 Day: Measurably reduce friction in the developer journey. You'll know because support volume drops, activation improves, and engineers stop getting pulled into "can you just explain how this works" conversations. Make docs and information a competitive advantage. Ship it like one. Set the bar for what good looks like at Vapi. Then hold it even when the platform ships something new every other week. Who You Are: You've used an API. You know what a webhook is. You don't need an engineer to explain what a POST request does or what LLM stands for. You think bad docs are a product bug. You write like a human, not a manual. Direct, occasionally funny, always accurate and 100% clear. You have an uncomfortable relationship with outdated information. When you see a doc that's wrong, something inside you dies. You make friends with engineers and support teams without having to bribe them. You're faster than people expect and more thorough than they asked for. You like hanging out regularly with Karl the Fog in our San Francisco office. 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

Responsibilities

The role involves owning developer-facing documentation end-to-end, including API references, guides, and knowledge bases, while building systems to ensure documentation remains current as the platform rapidly evolves. Success will be measured by measurably reducing friction in the developer journey, leading to lower support volume and improved activation.