Technical Writer
You make complicated things understandable, in writing, for someone in a hurry.
No degree needed Approachable to enter, hard to do excellently.
Can I actually do this?
One of the most genuinely open routes here, and a common way into tech for people from teaching, journalism or support. Hiring is sample-led: two or three pieces of clear documentation are the whole application.
Who it suits. People who get irritated by bad instructions and can explain something without showing off.
Runway. Months. Writing samples matter more than anything you could study.
Coming from support, teaching or writing? You already have the core skill; what you add is the technical vocabulary. Help Desk / IT Support
Also advertised as
The route
Four stations, in order. Each one is a thing you finish before the next matters.
-
Station one
Learn it free
Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.
Google — Technical Writing courses
Free to learn · no certificate
Google's own free technical-writing curriculum, aimed at engineers and writers alike. Free; no certificate.
Verified 2026-07-27
MDN — Learn web development
Free to learn · no certificate
Enough technical grounding to document software honestly. MDN is also, itself, a model of what good documentation reads like.
Verified 2026-07-27
GitHub Actions — quickstart
Free to learn · no certificate
Docs live in repositories now. Being comfortable with pull requests and CI is what separates a technical writer from a writer.
Verified 2026-07-27
-
Station two
Attest strategically
Nothing worth buying. This field hires on writing samples, full stop. The fastest credential is a merged documentation pull request on a real open-source project — free, public, and directly checkable.
Nothing here is worth paying for
No credential needed
Nothing worth buying. This field hires on writing samples, full stop. The fastest credential is a merged documentation pull request on a real open-source project — free, public, and directly checkable.
Checked 2026-07-27
-
Station three
Prove it
A certificate says you passed a test. These say you can do the job.
A merged docs pull request
Fix or improve documentation on a real open-source project and get it merged. Public, dated, and attributable to you.
A tutorial that works when followed exactly
Write one, then watch someone follow it literally without helping. Fix everything they stumble on.
A reference page for something undocumented
Find a tool with poor docs and write the page that should exist.
-
Station four
Get hired
Search these exact titles
Who hires for this. Software companies, cloud vendors, open-source foundations, hardware makers, and any regulated industry that must document what it built.
A merged pull request is public and dated, so it evidences both the writing and the ability to work in an engineering workflow. That is our reasoning about what is checkable, not a hiring statistic we have verified.
On salaryWe don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.
Where this route continues
- UX Designer — content design overlaps heavily
- UX Researcher — sideways move
This page last verified 2026-07-27 · How we verify
Google Technical Writing, MDN and GitHub Actions docs fetched and READ 2026-07-27.