2025 median annual pay
$90,390
Median for the whole occupation, across all experience levels. It is not specific to a level or to Brazil.
Career in 2026 and 2027
Technical Writer
A Technical Writer makes complex software usable by turning what engineers know into documentation readers can act on. The work combines clear writing, a feel for the reader, and increasingly the tooling and governance that keep documentation correct over time.
Content reviewed on October 21, 2026
- Levels
- 4
- Skills mapped at Mid-level
- 7
What each level must prove
Mid-level
Accountable for a complete, consistent documentation set for a product, including reference material and code samples.
You own the docs for a product area, write in the team's style guide, publish through a docs-as-code workflow and document APIs with working samples. Compared with junior, you manage a whole set of content and the toolchain behind it, not individual pages.
Average score required: 71%
Grammar & Style Guides
Why: You can apply a style guide and a term list across a product so the same feature is not called three names in three articles.
Tutorials
Why: You can structure a tutorial series that builds in difficulty and checks learning outcomes, so users progress from a first call to a real integration.
How-To Guides
Why: You can write guides that handle branches, such as different cloud providers or error cases, with troubleshooting that answers the tickets support keeps getting.
Markup Languages
Why: You can pick and use the right markup, such as Markdown, AsciiDoc or DITA, and convert legacy content without breaking links or structure.
Docs-as-Code
Why: You can keep docs in version control with a pull request review and a build that fails on broken links, so docs ship with the code that changed.
API Reference Writing
Why: You can document endpoints, schemas and authentication from an OpenAPI spec so an integrator can make a first authenticated call without asking the team.
Code Samples & Examples
Why: You can write samples that run as pasted, include error handling and are tested in CI, so a release does not leave readers with broken examples.
Study for Technical Writer: trails and practice exams
Each level of this career maps to a study trail. Read the full topic map for free, then measure your level.
Market snapshot (United States)
Projected job growth, 2025–2035
+1%
Slower than average
US occupation used: Technical Writers. US Bureau of Labor Statistics, Occupational Outlook Handbook, updated August 27, 2026
Two ways to move up one level
12 weeks · intensive
For whoever has a deadline
About 8 hours a week, in 1 cycle focused on the gaps that weigh most.
40 weeks · regular
Alongside work
About 4 hours a week, in 3 cycles. Each cycle carries what was left from the previous one.
Frequently asked questions
What is Technical Writer?
A Technical Writer makes complex software usable by turning what engineers know into documentation readers can act on. The work combines clear writing, a feel for the reader, and increasingly the tooling and governance that keep documentation correct over time.
What must each level of Technical Writer prove?
Technical Writer is mapped in 4 levels: Junior, Mid-level, Senior, and Expert. Open each level above to see the skills it must prove.
How long does the Technical Writer plan take?
The plan has 2 paces: 12 weeks per level at about 8 hours a week (intensive) and 40 weeks per level at about 4 hours a week (regular).
How the plan works
AI tutor
A study session on each new topic, at your level.
AI school
Hands-on lessons on using AI in your career's daily work.
Assessments
Each requirement is proven by measurement, not by a checkbox.
Stage review
At the end of each cycle you see what moved and what carries over.
Find out which level you are at
A short diagnostic measures the skills you already have. The journey starts from there.