Explore
Software & engineering documentation
Technical Writer
Understanding the thing well enough to explain it simply.
Typical pay
$65k-$120k
How you get in
Writing samples plus technical fluency
Outlook
Steady in software; strong for API and developer docs
Technical writers produce documentation, API references, guides and help content. The hard part is not the writing — it is extracting accurate information from engineers who are busy and assume you already know.
A day in the life
- 9:00aReview engineering tickets for changes needing documentation
- 10:00aInterview a developer about a new API endpoint
- 11:30aDraft and structure the reference page
- 1:00pLunch
- 2:00pTest the instructions by actually following them
- 4:00pReview cycle and publish to the docs site
How to get in
Writer who learns the technology
Duration
6-18 months
Cost
$0-$3,000
Credential
None — a documentation portfolio
- Build genuine technical literacy — learn to read code and use a terminal
- Write documentation for an open source project; it is public, verifiable work
- Learn the docs toolchain: Markdown, Git, static site generators
- Apply with a portfolio of real published documentation
Engineer or support into docs
Duration
1-2 years
Cost
$0
Credential
None — domain expertise
- Work in support, QA or engineering first
- Volunteer to write the docs nobody else wants to
- Build a portfolio from real internal and public documentation
- Technical credibility is the hardest half, and you already have it
Technical communication degree
Duration
2-4 years
Cost
$15,000-$120,000
Credential
Degree or certificate in technical communication
- Complete a technical communication program
- Learn information architecture and content strategy formally
- Intern with a software or engineering company
- Still build a public portfolio — that is what gets read
What people love
- · Remote-friendly and stable
- · Pays well for a writing career
- · Less deadline chaos than journalism or marketing
- · Portfolio matters more than a degree
What wears people down
- · Documentation is the first budget cut
- · Chasing engineers for answers is most of the job
- · Invisible when done well
- · Requires real technical comprehension, not just writing skill