Technical Writer
Every time you read instructions to set up a new printer, a help page about "how to reset your password", or a guide that came with your new washing machine, someone wrote that.
When the instructions are good, you don't even notice. When they're bad, you want to scream. 😤
Technical writers are the people who make complicated things simple. Let's look at this quiet but solid job.
What is this job, really?
The simple version: a technical writer explains complicated products in simple words.
Think of a technical writer as a translator, but not between languages. Between "engineer language" and "normal human language". The engineer says: "Initialize the device by toggling the primary input." The technical writer says: "Press the power button."
What does a technical writer actually do?
Writes help pages and FAQs for apps and websites.
Writes user manuals for products and software.
Creates step-by-step guides with screenshots.
Writes documentation for developers (more advanced).
Talks to engineers and product teams to understand how things work.
Updates texts when the product changes, which happens often.
Who needs a technical writer, and why?
Software and tech companies: they need help centers and documentation.
Manufacturers: machines, devices, medical equipment.
Banks, healthcare and other industries with complex rules and processes.
Good instructions save companies money. Every confused customer who calls support costs time and money. A clear help page answers the question before the phone rings.
Freelance or in a company?
Most technical writers work in companies, often remotely. Freelance projects exist too.
How much talking is involved?
Low to medium. You'll interview experts and join some meetings to understand products. Then lots of quiet writing.
How hard is it to learn? How long does it take?
Plan for 6 months or more. You'll learn:
how to write clear, simple instructions;
how documentation is structured;
tools for documentation and screenshots;
basics of the field you want to write about (software, medical devices...).
Big plus: if you've worked in an office, a hospital or another technical field, that knowledge is valuable. Many technical writers come from other professions.
You'll probably enjoy it if you:
Like to understand how things work.
Enjoy order, structure and lists.
Get annoyed by bad instructions (and secretly rewrite them in your head).
How is AI changing this job?
AI impact: AI-assisted 🤖
AI can write a first draft of documentation quickly. But here's the catch: AI doesn't actually know how the product works. It guesses. And in instructions, a wrong guess means a broken product or a very angry customer.
The real job is:
understanding the product by testing it and asking engineers;
checking every step really works;
organizing hundreds of pages so people find answers fast.
Technical writers use AI to write faster and spend more time on accuracy.
Honest downsides
It can feel dry. You're writing manuals, not novels.
Products change often, so you keep updating old texts.
You need to chase busy experts for answers.
Getting the first job takes a portfolio of sample documentation.
Try it before you choose it
Here's a secret nobody tells you: you don't have to choose a profession for the rest of your life. You're picking something to try. Like a new dish at a restaurant. If you hate it, you order something else next time. No drama.
And honestly? You can't know if you'll like a job until you try it. Reading about it is like reading about swimming. Useful, but you stay dry.
So here's the tiny, safe step:
Take one short beginner course. Watch a few lessons in the evening, after work. Try a small practice task. Then ask yourself one simple question: "Do I want to do more of this?"
Yes? Great. Now it makes sense to look for a deeper, more serious course.
No? Also great. You just saved yourself months, and you can try the next job on your list.
Either way, you keep your current job while you test the waters. No quitting, no big risks, no throwing your stapler out of the window.