Free Sample
The Complete Guide to Becoming A Technical Writer
What you'll really do, what you'll really earn, and whether you have the right temperament to thrive as a technical writer
by Alumigogo Books
Chapter 1: What Does a Technical Writer Actually Do?
Let's clear away the fog right now. A technical writer's core job is to turn complicated information into something a specific person can actually use. That's it. But the real work — the day-to-day, hour-to-hour reality — is far more varied and far more collaborative than the stereotype of a lone person typing in a basement.
The core responsibilities
On any given week, you will write, but you will spend an almost equal amount of time doing things that aren't writing. You'll interview subject matter experts (SMEs) — engineers, product managers, customer support reps, scientists — to extract the information you need. These people are often busy, sometimes terse, and rarely thinking about documentation. Your job is to ask the right questions, listen carefully, and translate their answers into prose a non-expert can follow.
You'll also test things. If the product is software, you'll install it, click through it, and intentionally break it to see what happens. If it's hardware, you might physically use the device, hand-tightening a screw or navigating a menu to make sure your instructions are accurate. A technical writer who doesn't verify the facts is writing fiction.
You'll maintain existing documentation. That means updating old guides when a product changes, fixing broken links in a help center, and deleting content that's no longer accurate. This is often called "content maintenance," and it's a real, recurring part of the job — not a one-time cleanup. For example, if