Explain complicated products clearly enough that somebody can actually use them. Writing, but paid like tech.
Click through it
Pay, the path, pros and cons and the facts on one printable page. Counsellors: send it to a student from your own email in one click.
The median pay is about $90,390 a year. Across everyone in the job it runs from about $57,440 at the lower end to about $145,270 at the upper end. The source is listed under Sources at the end of this page.
2 to 4 years after high school, on the usual route.
$500 to $48,500 all in for tuition, fees, exams and kit. Living costs are not counted.
No. There is no license to hold, though many employers still ask for training or a certificate.
Limited demand nationally, from government outlook data. Demand varies by region, so check your area.
Or read the whole thing here
What you earn and what it costs to get there.
Median
$90,390
Bottom tenth
$57,440
Top tenth
$145,270
The national median is $90,390 a year. The bottom tenth earn $57,440 or less and the top tenth $145,270 or more (2025 federal wage survey). That median is high for a writing job, and it is the main reason people move into this field from journalism or English.
$57,440 to $70,880
What the bottom tenth to bottom quarter of technical writers earn, 2025
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.
$122,320 a year
The median in New Jersey, the highest of any state
The District of Columbia is close behind at $117,810 and Massachusetts at $109,200. The lowest is Arkansas, at $61,180. State medians from the 2025 federal wage survey.
Roughly, all in
$500 to $48,500
Tuition, fees, exams and kit. Not rent, food or travel
There is no license 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 $12,000 a year. Two years at a community college first cuts that by about a third. 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.
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.
The exact path from high school to qualified.
There is no license and no single degree. What gets you hired is writing samples that prove you can explain something difficult.
High school
Grades 9 to 12
English and a science or computing subject together. The combination is the whole job in miniature.
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.
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.
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.
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.
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.
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.
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.
Things you don't need, but that help.
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. Often the hardest kind of writer to find.
Regulated writing
Medical device and pharmaceutical documentation, where the text is part of what a regulator approves. Slow and exacting.
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.
Be clear eyed about this. Drafting tools can produce a plausible first pass at a procedure, and companies have noticed. O*NET (Occupational Information Network), the federal career database, rates growth from 2025 to 2035 as slower than average (1% to 2%), with about 3,200 openings a year against about 46,400 people in the job in 2025. 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.
Day to day, pros and cons, where you'd work.
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 good
The hard parts
Things people don't tell you.
Titles reported to O*NET (Occupational Information Network) for this job include engineering writer, medical writer, grant writer and requirements analyst. The skill is the same, the subject matter is not.
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 has an advantage over one who cannot.
In the 2025 federal wage survey technical writers had a median of $90,390, against $77,920 for editors and $76,910 for writers and authors.
Every list is built from the same numbers shown above, so you can see where this career sits next to the others.
Writing and media first, then the rest of the field. See every career in creative.
Last checked October 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. How every figure on this site is sourced and checked.
Tell us about this page. A person reads every message.
No email app on this device? Use Gmail instead: report a mistake in Gmail or say what you like in Gmail.