Technical writer
Definition
What is a technical writer? Role, skills, examples
A technical writer translates complex technical information into clear, accurate documentation that real users can follow. Think installation guides, API references, standard operating procedures, and release notes. The job is not “writing about tech.” It is making products and processes usable through prose, diagrams, and structured content.
The role sits between engineering, product, and support. Good technical writers spend as much time interviewing subject matter experts and testing the product as they do at the keyboard. Their measure of success is whether the reader gets the job done without filing a ticket.
Modern technical writers also own information architecture, style consistency, and the tooling that publishes docs to the web. Many work in docs-as-code pipelines using Git, Markdown, and static site generators, closer to a developer’s workflow than a traditional editor’s.
How it works
A technical writer’s workflow usually follows five stages: audience research, source gathering, drafting, review, and publishing. Each stage has a different output, a different reviewer, and a different definition of “done.”
| Stage | Typical inputs | Output | Reviewer |
|---|---|---|---|
| Audience research | Personas, support tickets, search queries | Doc plan, scope brief | Product manager |
| Source gathering | SME interviews, specs, the product itself | Notes, screenshots, draft outline | Engineering lead |
| Drafting | Outline, style guide, templates | First draft in Markdown or DITA | Peer writer |
| Review | Draft, test environment | Edited, fact-checked copy | SME + editor |
| Publishing | Final draft, CMS or static site generator | Live page, indexed and versioned | Docs manager |
The two style references most enterprise docs teams default to are the Microsoft Writing Style Guide and the Google developer documentation style guide. Both are free, both are maintained, and both define a house voice that scales to hundreds of contributors.
Modern technical writers also use structured authoring formats (Markdown, reStructuredText, AsciiDoc, or DITA XML) so content can be reused across products, translated efficiently, and published to multiple channels from one source. That’s the “single-sourcing” principle the Society for Technical Communication has championed since the 1990s.
Examples
Technical writing shows up in every industry that ships a product with instructions. Four named examples make the range clear.
- Stripe publishes one of the most-cited API references on the web. Its docs team writes alongside engineers and ships changes the same day APIs do, a model the company has been refining since 2014.
- Atlassian maintains a public documentation portal for Jira, Confluence, and Bitbucket that serves millions of admins. The team uses a custom docs-as-code stack and a published style guide.
- Red Hat employs hundreds of technical writers globally to document Linux distributions, OpenShift, and Ansible. The team contributes its style work back to open source.
- GE Healthcare staffs technical writers in regulated medical-device documentation, where every instruction has to pass FDA 21 CFR Part 820 design-history-file scrutiny before the product ships.
Outsourcing the function is also routine. Philippines-based BPO firms and Indian KPO providers have run dedicated technical-writing teams since the mid-2000s, mostly for software vendors and engineering consultancies that need 24-hour doc cycles or multilingual output. Rates in the Manila and Cebu corridor commonly run 50–70% below US in-house equivalents.
According to the US Bureau of Labor Statistics’ Occupational Outlook Handbook, technical writers in the US earned a median annual wage of $80,050 in 2023, and the field is projected to grow about 4% through 2033 — roughly in line with the average for all occupations.
Related terms
- Business writer: focuses on internal and external business communication rather than product instructions.
- Copywriter: writes persuasive marketing copy; success is measured in conversions, not task completion.
- Subject matter expert: the domain authority a technical writer interviews and partners with.
- Content marketing: a distribution discipline; technical writing serves users post-purchase, not pre-purchase.
- Transcription virtual assistant: often supports tech writers by turning SME interview audio into searchable text.
- Knowledge process outsourcing (KPO): the outsourcing tier most technical-writing teams sit in, given the domain expertise required.
- Business process outsourcing (BPO): the broader category covering offshore documentation teams in the Philippines and India.
FAQ
What’s the difference between a technical writer and a copywriter?
A technical writer documents how a product works for users who have already bought it. A copywriter writes promotional copy to convince people to buy. Different audiences, different tone, different success metrics.
Do technical writers need a STEM degree?
No. Many strong technical writers come from English, journalism, or communications backgrounds and learn the domain on the job. Others come from engineering and lean into writing. What matters is the ability to interrogate an expert, test the product, and explain it cleanly.
What tools do technical writers use day-to-day?
Common stacks include Markdown editors (VS Code, Obsidian), version control (Git, GitHub), static site generators (MkDocs, Docusaurus, Hugo), structured authoring tools (Oxygen XML, Paligo, MadCap Flare), and screenshot or diagramming tools (Snagit, Excalidraw, Figma).
How much does a technical writer cost when outsourced?
Mid-level technical writers in the Philippines or India typically run $1,500–$3,500 per month fully loaded, compared with $7,000–$10,000+ for a comparable US in-house hire. Final pricing varies with domain — medical devices and finance command higher rates than general software.
Is AI replacing technical writers?
AI tools speed up drafting, fact-checking, and translation, but they still need a writer in the loop to interview SMEs, judge accuracy, and own the content strategy. Most teams are using AI to publish more documentation with the same headcount, not fewer writers.
What does a technical writer’s deliverables list look like?
A typical month covers a mix of user guides, API references or endpoint docs, release notes, FAQ updates, internal SOPs, and at least one larger piece — a getting-started tutorial, a migration guide, or a redesigned information-architecture map.
Need a technical writer who already knows docs-as-code, regulated industries, or your stack? Browse vetted outsourcing providers on Outsource Accelerator to compare shortlists, rates, and case studies before you hire.
Independent
