Technical Writer

Vapi (/ˈVɑːpi/):

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.

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.

Details

Location

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.

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.