Technical Writer

📋 Description

• Drive, don't wait. Features land every day, and bigger launches several times a month. You find out
• Own it end to end. Work a feature out from the code and the product, write the page, verify it in
• Care about the reader more than the feature. Our docs come with data: what people can't find, what
• Make the product better, not just explain it. Documenting a feature means using it end to end.
• Write for three readers on one page. The non-technical builder, the developer, and the AI agent
• Build something that outlasts the week. AI drafts a lot of our pages. The human work is judgement

🎯 Requirements

• 3+ years documenting software products, with pages that get a reader to the outcome without
• Write with AI for research, drafting and checking; recognize and catch its errors.
• Test what you document - try the feature and read the source; raise issues when something is broken
• Comfortable with docs-as-code: Git, Markdown and pull requests.
• Ask engineers and PMs specific questions; raise early with reasons when a feature won't make sense
• Preferred: shipped docs weekly at a startup or scale-up, written for AI readers, UX writing/content

🎁 Benefits

• Work at a fast-growing, talent-dense AI company (TIME 100 Most Influential Companies, Forbes AI 50)
• Part of a team with high ownership and low-ego collaboration
• Opportunity to define documentation practices for both human and AI readers
• Direct impact on a product used by millions of users
• Cross-functional collaboration with engineers, PMs, and other teams