Senior Technical Writer – AI-First Documentation
At VWO, documentation is product infrastructure.
We’re hiring a Senior Technical Writer who wants to design documentation systems and workflows, and not just write help articles. This role blends technical writing, AI automation, experimentation knowledge, and strategic thinking.
What You’ll Do
Build & Evolve AI Documentation Agents
- We already leverage AI. Now we want to push it further. You will:
- Design, build, and scale AI agents that automate documentation processes and workflows
- Identify areas where human effort can be reduced without compromising quality
- Blend product expertise with automation to enhance documentation velocity
- This is not about using AI to write. This is about building systems that make documentation smarter.
Create, Review, & Maintain High-Impact Product Documentation
- Write clear, accurate, user-focused KB articles
- Edit and peer review articles to ensure they maintain style guide adherence
- Streamline large-scale clean-ups of knowledge base content
- Maintain structured, consistent documentation at scale, across product streams
Collaborate & Influence
- Partner with Product, Engineering, Support, CSMs, UI/UX, and Product Consultants
- Influence how features are communicated and adopted
Create Visual Learning Assets
- Create infographics and capture screenshots that simplify and support technical concepts
What You Bring
Experience
- 5-6+ years in Technical Writing (B2B SaaS)
AI & Automation
- Hands-on experience with AI tools and automation workflows
- Strong understanding of GenAI in documentation ecosystems
- Ability to design and improve scalable AI-driven documentation systems
Technical Foundation
Comfortable with:
- Web technologies and browser behavior
- Web experimentation (A/B testing, feature rollouts, targeting logic, etc.)
- Cookies & cookie consent frameworks
- Third-party integrations and data flow concepts
- Client-side vs server-side concepts
- If terms like event tracking, client-side vs server-side, and SDK integration don’t scare you, you’d be in the right place.
Writing & Editing Excellence
- Excellent written English and a strong command over its grammar
- Sharp attention to detail
- Ability to design structured, contextual, and user-focused content
- Design documentation strategies and information architecture aligned with product goals
Strategic and Analytical Mindset
- Experience with measuring documentation impact using analytics tools (GA4 or similar)
- Data-driven approach to improving content performance
Working Style & Mindset
- Agile. You adapt as fast as products and priorities evolve.
- Multitasker. You manage multiple streams without sacrificing quality.
- Strong prioritizer. You balance speed and precision intelligently.
- Owner. You spot gaps and fix them.
- Comfortable with ambiguity. You bring structure where none exists.
- Stakeholder-savvy. You align inputs and drive reviews efficiently.
Tools
- Zendesk, Jira, SnagIT, Figma, GitHub.
- Markdown tools (GitBook, ReadMe.io) are a plus.
The Team
Highly driven. Self-motivated. Curious.
We experiment. We build internal tools. We measure impact.
There’s real ownership and real growth here. You won’t just execute tasks, you’ll influence strategy, improve systems, and help define what AI-first documentation looks like at scale.
Never a dull day. Because the product evolves, the ecosystem grows, and we move with it.
Apply If You…
Genuinely love technical writing. Structure makes you happy. Clarity excites you.
Can’t stop until the audience understands. Not just reads, understands.
Obsess over details. Because yes, the smallest details make the biggest difference.
Have strong audience empathy. You think in user journeys, not just sections. You constantly ask: Who is reading this? What are they trying to do? What’s blocking them?
Thrive in fast-paced environments. Priorities shift. Screens change. You adapt.
Think in systems, not just articles. You care about scalability and automation.
Like experimenting with AI tools. You’ve probably built something just to test what’s possible.
Believe documentation is a product. And should be treated like one.