Careerhelp

Technical Writer

Explain complicated products clearly enough that somebody can actually use them. Writing, but paid like tech.

Typical pay
$90,390a year
Time to qualify
2 to 4 yearsafter high school
Demand
Limited
Licence needed
Noanyone can do it

Click through it

Start
Download the one-pagerPDF

Pay, the path, pros and cons and the facts on one printable page. Good for a wall or a guidance counsellor.

Or jump to a part

  1. 1.MoneyWhat you earn and what it costs to get there.5 screens
  2. 2.EducationThe exact path from high school to qualified.5 screens
  3. 3.OptionalThings you don't need, but that help.3 screens
  4. 4.ExtrasDay to day, pros and cons, where you'd work.4 screens
  5. 5.FactoidsThings people don't tell you.4 screens

Or read the whole thing here

Money

What you earn and what it costs to get there.

What technical writers make

Typical

$90,390

Starting out

$57,440

Senior, top tenth

$145,270

The national median is $90,390 a year, and the bottom tenth start near $57,440. That median is high for a writing job, and it is the main reason people move into this field from journalism or English. Software and medical device work sits at the top of the range, manufacturing manuals nearer the bottom.

Starting pay

Roughly $57,000 to $70,000

A junior writer on a documentation team

Pay tracks the industry you write for more than it tracks your writing. The same skill earns noticeably more documenting software or medical devices than documenting appliances.

The middle is $43.46 an hour

$43.46 an hour

The published median hourly rate for this job

That hourly figure matters because a lot of this work is done on contract. Contractors and agency writers bill by the hour or by the project, usually at a higher rate than a salaried writer earns, with no benefits attached.

What it costs to get there

Community college associate degree
Roughly $4,000 to $6,000 a year in-state
Bachelor's degree, in-state public university
Roughly $11,000 to $16,000 a year in tuition and fees
A laptop and the software
Most tools are paid for by your employer. A decent laptop is the only real personal cost
Short courses in a documentation tool
A few hundred dollars, and often reimbursed once you are employed
Roughly, all in
$500 to $52,000

Tuition, fees, exams and kit. Not rent, food or travel

There is no licence and no required degree, so the low end is somebody who already writes clearly, takes a short course in a documentation tool for a few hundred dollars, and gets hired on a portfolio of real samples. That cheap door exists but is harder to walk through than it sounds, because most job postings still screen for a degree and you have to produce the samples with no employer to hand you a subject. The high end is four years of a bachelor's degree at an in state public university at roughly $13,000 a year. Two years at a community college first cuts that close to half. Employers supply the writing software.

Fill in the FAFSA (Free Application for Federal Student Aid). This is a field where a cheap degree plus a strong portfolio beats an expensive degree with nothing to show, so borrow as little as you can.

How technical writers get paid

  • Salary

    Most jobs. Software, engineering, pharmaceutical and medical device companies all keep permanent documentation teams.

  • Contract

    Very common. Six or twelve month contracts at a higher hourly rate, with no paid leave or health insurance.

  • Freelance

    Per project work for smaller companies that need a manual written once and then left alone.

  • Government

    Federal agencies hire writers and post the jobs on USAJOBS (the official federal hiring site). Slower hiring, better security, and a pension.

Education

The exact path from high school to qualified.

The path

There is no license and no single degree. What gets you hired is writing samples that prove you can explain something difficult.

  1. 1

    High school

    Grades 9 to 12

    English and a science or computing subject together. The combination is the whole job in miniature.

  2. 2

    A degree

    2 to 4 years

    Technical communication if your school has it. Otherwise English, journalism, engineering or a science. Employers hire from all of these.

  3. 3

    Build a portfolio

    While studying

    Write real documentation: a setup guide for an open source project, a manual for something in your house, instructions for a process at your job.

  4. 4

    Internship or first junior role

    One summer to a year

    Documentation teams take juniors. A single internship is often enough to be taken seriously afterwards.

  5. 5

    Learn the toolchain

    First year on the job

    Structured authoring, a help publishing tool, and version control. This is the part that separates a technical writer from a writer.

High school courses that help

  • English

    Clear, ordered, boring-on-purpose prose. That is the craft here, not flourish.

  • Computer science

    You do not need to be a programmer, but you must be able to read code and follow what it does.

  • Physics or chemistry

    Practice at understanding a system well enough to describe it accurately.

  • Graphic design or media

    Diagrams, screenshots and page layout are part of the deliverable.

  • A language other than English

    Documentation gets translated. Writers who understand that write more translatable English.

Time and money, at a glance

Years after high school
2 to 4
Admission
Ordinary university or community college admission
Total tuition
$10,000 to $60,000 in-state, depending on the route
Paid while training?
Internships are usually paid, and many people enter from another job

Not regulated, and the degree is negotiable

No state licenses technical writers, and there is no required qualification. Reported education is genuinely mixed: in the federal occupational survey about a third of people in the job said an associate degree was needed and about a third said a bachelor's degree was. What every employer asks for instead is samples. A portfolio of three or four pieces of real documentation, with a short note on each explaining who it was for and what problem it solved, does more than any certificate in this field.

Where people study

  • Technical communication programs

    A handful of universities run a dedicated major. It is the most direct route if your state has one.

  • A technical university

    Somewhere like Michigan Technological University puts a writing student in the same buildings as the engineers whose work they will be documenting.

  • Community college plus a portfolio

    An associate degree in communication or English, built out with real writing samples. The cheapest credible route.

  • Sideways from another job

    Plenty of technical writers were engineers, nurses, support agents or teachers first, and the subject knowledge is why they were hired.

Optional

Things you don't need, but that help.

Skills that raise your pay

  • Documentation as code

    Writing docs in plain text, storing them in Git and GitHub alongside the software, and publishing them automatically. This is the standard on software teams now.

  • Structured authoring

    Writing in XML (a markup language for structured documents) so the same content can be reused across manuals, help sites and print.

  • Help publishing tools

    MadCap Flare and Adobe FrameMaker are the two names that appear most in job ads.

  • API (application programming interface) documentation

    Documenting how one piece of software talks to another. The best paid corner of the field, and the hardest to staff.

  • Regulated writing

    Medical device and pharmaceutical documentation, where the text is part of what a regulator approves. Slow, exacting and well paid.

Nice-to-haves

  • A published portfolio

    Three or four pieces online, each with a line about who it was for and what it fixed.

  • Open source contributions

    Almost every project needs its documentation improved, and the work is public and easy to point at.

  • Diagram skills

    A clear diagram replaces two pages of prose. Being the person who can draw it is worth a lot.

  • Interviewing engineers

    Most of the job is extracting knowledge from busy people who would rather be coding.

What artificial intelligence is doing to this job

Be clear eyed about this. Drafting tools can produce a plausible first pass at a procedure, and companies have noticed. The federal projection has this occupation growing more slowly than average, with about 4,500 openings a year against roughly 56,400 people in the job. What is not easily automated is the part where you sit with an engineer, work out what the product really does, notice that the documented behavior is wrong, and decide what the reader actually needs to be told. Writers who only reformat what they are handed are the ones at risk.

Extras

Day to day, pros and cons, where you'd work.

A typical day

Start by checking what changed: a release is coming and three features need documenting. You read the ticket, try the feature yourself, and find that it does not work the way the description says. You message the engineer, get half an answer, and book fifteen minutes with them. Then you write, which is mostly deleting: cutting a six step procedure down to four and making sure every screenshot matches the current version. Afternoon is review comments from a previous draft, and a meeting where somebody asks whether the help site can explain a decision the product team has not made yet.

The honest trade-offs

The good

  • The best paid ordinary writing job in the country
  • Remote work is normal, and has been for years
  • You learn how things genuinely work, in detail, for a living
  • No license, no gatekeeping exam, and a portfolio can get you in

The hard parts

  • Growth is slower than average and drafting tools are pressing on the simpler work
  • Documentation is the first budget cut when a company is squeezed
  • You depend on busy engineers who see explaining things as an interruption
  • Recognition is thin: good documentation is invisible and bad documentation is everyone's complaint

Work life

Typical hours
40 a week, with pressure before a product release
Remote work
Very common, including fully remote roles
Physical demand
Low
Unionized
No, except some government and media employers

Factoids

Things people don't tell you.

The job title hides a dozen jobs

Reported titles in this occupation include engineering writer, medical writer and requirements analyst. The skill is the same, the subject matter is not, and the subject matter is what your pay is really based on.

Writers now use programmers' tools

On software teams documentation is written in plain text, stored in Git and GitHub next to the code, reviewed like code and published automatically. A writer who can work that way is worth more than one who cannot.

Deleting is most of the work

Experienced technical writers talk about cutting rather than writing. A procedure that takes six steps to describe usually means the product is badly designed, and pointing that out is part of the job.

Sometimes the manual is the product

In medical devices and aviation, documentation is part of what a regulator approves before anything can be sold. Getting a sentence wrong there is not a typo, it is a compliance problem.

Where these numbers come from

Last checked September 2026. Pay figures are typical full-time annual amounts in United States dollars, based on Bureau of Labor Statistics wage data and published pay scales. They vary by state, employer and experience. Tuition is for in-state students at public schools unless the card says otherwise.