How to become a technical writer — the portfolio is the credential

General career information, not a guaranteed hiring outcome. Certification details change; check current requirements before paying for anything.

Most "become a technical writer" advice is written by certificate sellers. Here is the awkward fact underneath their sales pages: no required credential exists. Employers hire on whether your samples show you can make complex things usable — which is bad news for the sellers and very good news for you.

What the job actually is

Technical writing is not prose about technology. It is instruction design: a user, a task, and the shortest honest path between them. The deliverables look like API references, tutorials, release notes, runbooks, knowledge-base articles and compliance procedures — and the daily work is closer to information architecture than to essay writing. You interview engineers, run the product, break it, and write down what actually happens.

Two consequences follow. First, precision beats elegance: an accurate ugly sentence outranks a beautiful vague one. Second, you must use the thing you document. Writers who document from screenshots get found out in review, every time.

The skill stack, in order

1. Plain language under constraint. Say exactly one thing per sentence, in the order the user needs it. If you can write a recipe a stranger follows without texting you, you have the core skill.
2. Docs-as-code. The modern stack is Markdown, Git/GitHub, a static site generator, and for software work the OpenAPI/Swagger specification. This is the single highest-leverage week of learning available: teams hire writers who can open a pull request, because you cost them zero workflow change.
3. Audience and task analysis. The difference between a tutorial, a how-to and a reference is the reader's state of mind. Knowing this taxonomy is what separates writers from typists.
4. Enough technical fluency to be dangerous. Command line basics, REST APIs, and reading code without writing it. You are not required to be an engineer; you are required to not be intimidated by one.

Certifications: what they're actually for

• CPTC (Certified Professional Technical Communicator) — the credential from the Society for Technical Communication, roughly $400–500. Respectable, but it assumes about five years of experience or an education-equivalent, so it is a mid-career signal, not an entry door.
• Google's technical writing certificate (via Coursera) — affordable, sensible structure, useful on a CV for career-changers.
• Postman's API documentation course — free to learn, small fee if you want the verified certificate, and it teaches the exact artifact software teams ask for.

None of these replaces a portfolio. All of them are cheaper than the bootcamps implying otherwise. If money is tight, the Postman course plus a public docs contribution outranks any wall certificate.

The portfolio plan that works

Hiring managers spend minutes, not hours. Build two or three artifacts, each with a one-paragraph context note (audience, problem, your approach):

1. A documentation fix in a real open-source project. Find a README that assumes knowledge the reader doesn't have, rewrite it, submit the pull request. The merged PR is verifiable proof — nobody can accuse you of inventing samples, and the diff shows your judgement.
2. An API reference for a public API. Pick any open API, document five endpoints by hand in OpenAPI-backed Markdown, including a getting-started tutorial. This is the artifact that gets freelance applicants shortlisted, because it's the artifact teams are short of.
3. A before/after rewrite. Take a genuinely bad public help page (they are everywhere), show the original, show yours, and annotate three decisions. This demonstrates the skill employers think can't be demonstrated: editing, not just writing.

That third one is the honest answer to "can't AI do this now?" — AI drafts generic text fine. It cannot attend the sprint, discover the undocumented failure mode, and argue with the engineer about what the product actually does. Your portfolio should quietly demonstrate the parts of the job that require attendance.

Where the first work comes from

• Open source projects with docs debt. Maintainers know their docs are bad; many will take a serious unsolicited docs contribution, and some fund ongoing writers once trust exists.
• SaaS startups between five and fifty engineers. Docs get written nights-and-weekends by founders until exactly the point where they'll pay someone. See the sibling piece on becoming a SaaS writer — the buyer is the same person.
• Documentation agencies and product companies hiring freelance doc writers. Slower to break into, steadier once you're in.
• Adjacent pivots count too: nurses who write medical-device procedures and accountants who write finance-team runbooks enter through domain knowledge. The medical writing route is a worked example of that door.

Pricing without underselling

The niche's pay structure — survey figures, sub-niche splits, and why documentation errors cost engineering hours — is covered in what technical writing pays. The short version for new writers: price the project (one tutorial, one API reference section), not the hour of typing, and let the rate calculator tell you what a day rate actually nets. Per-word pricing fits technical writing badly; a gorgeous 900-word API guide can take three days or three hours depending on the engineer.

Keep the admin side light from day one — a simple tracker and the project and client tooling most writers already have is enough until retainers arrive.

What to do this month

1. Learn Markdown and Git to the pull-request level. One weekend.
2. Do the Postman API course. One more weekend.
3. Ship portfolio artifact #1 — the open-source docs PR.
4. Then #2, the API reference, while #1 is in review.
5. Pitch three SaaS startups a specific docs fix ("your Quickstart assumes the CLI is installed; here's the rewrite") — specific pitches, not "I write tech docs".
6. Price the first job as a project, check it against the rate calculator, and read what technical writing pays before you name the number.

Certification details reflect published pricing and prerequisites as of 6 September 2026 (CPTC via the Society for Technical Communication, Google's Coursera certificate, Postman's API course). Programs change — verify before paying. This is general career information, not a hiring guarantee.