How to become a Technical Writer
Most technical writers didn't plan on the job. They were the engineer who wrote the only readable setup guide, the support agent whose macros everyone copied, or the English grad who liked figuring out how software worked. Hiring managers care far less about your degree than about whether you can take something confusing and make it usable.
What the job really is
You write the instructions people reach for when they're stuck. That can mean API reference pages, an admin guide for hospital software, release notes, a troubleshooting article in the help center, or the text inside a settings screen. The writing is the smaller part. Most of your week goes to getting information out of engineers and product managers who are busy, testing the product yourself until you understand where people trip, and deciding what to leave out.
The work splits roughly into two camps. Software documentation lives in tools like Confluence, a docs-as-code setup with Markdown and Git, or an authoring tool like MadCap Flare. Hardware, manufacturing, medical device and defense documentation leans on structured authoring, DITA, and strict review and sign-off. Both pay the bills. The skills overlap more than job titles suggest.
Four ways people get hired
Move over from a technical job you already have
This is the route that works most often. Support agents, QA testers, junior developers, lab techs and field service people already know a product from the inside. Start writing the docs your team is missing: a runbook, an onboarding page, a cleaned-up internal wiki. Then ask to own the release notes. When a writing role opens at your company, you're the obvious internal pick, and you have real samples you can talk about.
Come from writing, then learn the tech
Journalists, editors, teachers and marketing writers already know how to structure information and hit a deadline. What they usually lack is comfort with the product side. Learn enough to read a code sample, run a command in a terminal, and call an API with Postman or curl. Then document something real, so a hiring manager sees you can handle technical material and not just prose.
Build a portfolio through open source
Open-source projects are short on docs and usually happy to take help. Pick a project you actually use, find a gap in the getting-started guide, and submit a pull request on GitHub. You learn the docs-as-code workflow, you get reviewed by maintainers, and you end up with public proof of your work that anyone can click. Some projects even label easy docs issues for newcomers, so look for those first.
Take a certificate course
Community college certificates and short online courses can teach structure, style guides and tools. They help most when you're starting from nothing and want a guided first portfolio piece. They're a weak signal on their own, though. A hiring manager will read your samples before they look at a certificate, so treat the course as a way to produce samples, not as the credential that gets you in.
What goes in a writing portfolio
Your portfolio does more work than your resume. Keep it short: a few pieces, each with a line on who the reader was, what the product did, and what you changed. Hiring managers like seeing a task-based procedure, a concept explainer, and a piece of reference material, because those are the three kinds of topic you'll write every week.
If your best work is behind an employer's login, don't post it. Rewrite a public version for a made-up product, or document an open-source tool instead. A before-and-after of a messy page you rewrote is one of the most convincing samples you can show, because it proves judgment and not just clean sentences.
Words that show up in technical writer postings
Applicant tracking systems and recruiters search for exact terms, so use the ones you can honestly claim, spelled the way the posting spells them.
Turning a vague line into evidence
Responsible for writing and updating product documentation.
Rewrote the admin setup guide for a billing platform, cutting related support tickets by 38% in 6 months; moved 140 help articles from Word to Markdown in GitHub.
The part some writers can't stand
You'll spend a lot of time waiting on people. The engineer who owns the feature is heads-down on the next sprint, the product manager changed the design after you finished the draft, and the review comes back the night before release. Writers who need long, quiet stretches of pure writing often find this grinding.
You also get little credit when things go well. Good docs are invisible, and nobody sends a thank-you note because the install worked. The people who last in the job get their satisfaction from the craft itself, and from quietly watching the support queue shrink.
What Technical Writer postings ask for
Hiring the most
- "ProSidian Consulting, LLC"37
- Collabera234
- IntegratedResourcesINC34
- Anduril Industries20
- ArtechInformationSystemLLC16
Remote
6% of openings are fully remote.
Posted pay
$69,000 – $122,100
Typical range in the 33 of the newest 60 postings that list pay.
Questions people ask
Do I need to know how to code to be a technical writer?
Not to get your first job, in most cases. You do need to be comfortable reading code samples, running commands and testing an API call, especially for software docs. The writers who can also fix a broken code sample or build the docs site themselves tend to get the better offers and the developer-facing roles.
What degree do technical writers have?
All kinds. English, communications and journalism are common, and so are engineering, computer science and the sciences. Some universities offer technical communication programs. A hiring manager will judge your samples and your grasp of the product far more than the name on your diploma.
Is technical writing being replaced by AI tools?
The first-draft part of the job is changing, and plenty of teams now use AI tools to rough out reference pages or summarize changes. The parts that are hard to hand off are the ones that make docs useful: deciding what the reader needs, testing the steps yourself, and pushing back when the product is confusing. Writers who lean into that editorial and testing work are in a stronger spot than those who only produce text.
Ready to apply?
Tell HeroApply you want Technical Writer roles. It finds the openings and applies for you each day.