Technical Writing and Content
Making complex technology clear for the people who need to use it
Overview
Technical Writing and Content covers the roles responsible for creating the documentation, guides, and reference material that help people understand, use, and build with technology. From API documentation and developer portals to user guides, onboarding tutorials, and internal knowledge bases, the work in this category sits at the intersection of language and technology — requiring both clear communication skills and enough technical literacy to write accurately about complex systems.
The category is small but underserved. There are consistently more open positions than qualified candidates — particularly for practitioners who can write developer-facing documentation, work in docs-as-code environments, and engage credibly with engineering teams. Good technical writing reduces support costs, accelerates user adoption, and improves the experience of working with a product or platform. It is a career path that suits people with strong language instincts who have developed, or want to develop, genuine technical understanding.
Roles in this Category
10 roles
Web Content Manager
StableUX Writer
GrowingDeveloper Advocate
GrowingContent Moderator
StableDocumentation Specialist
StableContent Strategist
GrowingKnowledge Base Manager
StableContent Operations Manager
GrowingAPI Documentation Engineer
GrowingTechnical Editor
StableSkills
Hard Skills
- Technical Writing
- Content Strategy
- Information Architecture
- Audience Analysis
- Style Guide Development
- Content Management
- Search Engine Optimisation
- User Experience Writing
- Data Analysis
Soft Skills
- CommunicationProducing language that is precise, accurate, and calibrated to purpose
- Attention to DetailImprecision in technical content is a quality defect with direct user impact
- Analytical ThinkingStructuring information architectures, audience models, and content performance questions
- CollaborationBridging domain experts and end users as the translation layer between them
- Audience AwarenessModelling what a specific reader knows, needs, and will misunderstand
- Editorial JudgementMaking principled content decisions where accuracy, standards, and audience needs intersect
Tools & Software
Core Themes
- Writing and maintaining API documentation, user guides, and developer tutorials
- Structuring documentation portals for clarity, discoverability, and accuracy
- Testing product features and APIs to verify documentation before publication
- Collaborating with engineers and product teams to capture and communicate technical detail
- Applying and maintaining documentation style guides across all written output
- Working in docs-as-code environments using Markdown, Git, and static site generators
- Gathering user feedback on documentation quality and iterating based on pain points
Typical Entry Points
The category is accessible from both writing and technical backgrounds. Google's Technical Writing courses (One and Two) are free, widely recognised, and directly cited in job descriptions. Degrees in English, Journalism, Computer Science, or related disciplines are all valid backgrounds. A portfolio of published technical documentation — including API docs or tutorials for real or open source projects — is the primary hiring signal. Contributing documentation to open source projects on GitHub is the most practical route to building a portfolio before being hired.
Who This Category Is For
- People with strong writing skills who want to work in technology without becoming software engineers
- Those who find genuine satisfaction in making complex things clear and accessible
- People from journalism, academia, or communications backgrounds who want to move into tech
- Those who are technically curious and enjoy learning how systems work in order to explain them
- Developers or analysts who want to pivot toward documentation and developer experience roles
- People who want to work closely with engineering teams without writing production code
- Those who prefer deep-focus, craft-oriented work over meeting-heavy delivery roles
- People who want strong long-term demand — the supply of qualified technical writers remains consistently below the number of open positions
Related Categories
Recommended Reading
Docs for Developers — Jared Bhatti et al.
Every Page Is Page One — Mark Baker
The Product Is Docs — Christopher Gales et al.
Strategic Writing for UX — Torrey Podmajersky