Role profile
Technical writer
Also called: Documentation writer · API documentation writer · Developer documentation engineer · Content designer (overlaps) · Information developer
Technical writers produce the manuals, help articles, API references and how-to guides that explain complex products to the people using them. Software companies, engineering and manufacturing firms, and government contractors are common employers, and some writers work freelance.
- Median pay, 2025
- $90,390
- $57,440 to $145,270 (10th to 90th percentile)
- US jobs, 2025
- 46,400
- Technical Writers
- Outlook, 2025-35
- +1%
- Slower than average
- Typical entry
- Bachelor's degree
- Experience: Less than 5 years
What the work looks like
- Interview engineers and product managers to understand a feature, then try it yourself.
- Write and update help articles, API references, release notes and setup guides.
- Keep docs in sync with the product, often working in Git alongside the code (docs as code).
- Create screenshots, diagrams and short code samples, and test that the samples actually run.
- Organize a documentation site so readers can find answers, using analytics and support tickets to see what is missing.
- Edit content written by engineers and support staff for clarity and consistency.
- Review AI-drafted content for accuracy, since a confident wrong instruction does real damage in docs.
How people get in
The BLS lists a bachelor's degree as typical, often in English, communications or journalism, and says knowledge of a technical subject is a plus. Less than five years of related experience and short-term on-the-job training are typical.
Many technical writers start in another technical role (support, QA, engineering or lab work) and move into writing because they explain things well. Others come from writing backgrounds and learn the technical side, which works best if you can read code and use a command line.
Build a portfolio before applying: rewrite a confusing open-source project's README, document a public API, or contribute to an open-source documentation project. Certification exists through professional associations but is optional.
Skills employers ask for
- Clear, concise writing and editing
- Markdown
- Git and pull requests
- Docs-as-code tools (Docusaurus, MkDocs or similar)
- Reading code (Python or JavaScript)
- API documentation (OpenAPI)
- Command line basics
- Diagramming tools
- Information architecture
- Style guides
Outlook to 2035
The BLS projects 1% growth from 2025 to 2035, slower than average, with about 3,200 openings a year mostly from replacement. AI writing tools put pressure on generic documentation work. Writers with real technical depth, such as API and developer docs, hold up better because accuracy there depends on understanding the product.
How the pay compares
Technical writer highlighted against the other 13 roles we track.
Source: U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Technical Writers. Pay is 2025 median annual wage; outlook is projected employment change 2025-35.