How to Become a Technical Writer in 2026: A Realistic Roadmap

At FreelanceAtlas, we help freelancers turn a skill into a business that pays its bills. This guide covers what technical writers produce, what the BLS and two industry surveys say about pay, the skills and tools clients expect, the free training worth your time, how to build samples without a client, where the work comes from, and what AI is doing to the field. If you are still choosing between writing paths, read it alongside How to Become a Freelance Writer in 2026: A Realistic Roadmap and Freelance Writing Rates in 2026: Per Word, Per Hour and Per Project.

What Technical Writers Actually Produce

Technical writing is documentation that lets someone use, build, fix or support a product. The BLS profile of technical writers says they “prepare instruction manuals, how-to guides, journal articles, and other supporting documents to communicate complex and technical information more easily.” Freelance work usually falls into a handful of deliverable types:

• User guides and manuals. Step-by-step instructions for setting up and operating a product, from a software app to a piece of lab equipment.
• API reference and developer guides. A description of every endpoint, with its parameters and error codes, plus tutorials that show a developer how to make a first request.
• Standard operating procedures (SOPs). Internal instructions that let staff do a repeated or regulated task the same way every time.
• Knowledge base articles. Short help center answers that let customers solve a problem without contacting support.
• Proposals and white papers. Longer documents for technical buyers or funders. The BLS notes that “Some technical writers help write grant proposals for research scientists and institutions.”

One useful way to organize this work is Diátaxis, a framework that identifies “four distinct needs, and four corresponding forms of documentation – tutorials, how-to guides, technical reference and explanation.” Knowing which of the four forms a page is meant to be makes your drafts clearer and shows you the gaps in a client’s docs.

Technical Writer Pay and Job Outlook: What the Data Shows

The BLS Occupational Outlook Handbook page for technical writers, last modified August 27, 2026, uses May 2025 wage data and projections for 2025 to 2035. These are its main figures:

• Median pay: $90,390 a year, or $43.46 an hour. The median for all US workers was $50,980.
• Range: the lowest 10 percent earned less than $57,440, and the highest 10 percent earned more than $145,270.
• Jobs: about 46,400 in 2025, projected to reach 46,700 by 2035. The BLS calls that 1 percent growth “slower than the average for all occupations.”
• Openings: about 3,200 a year on average, mostly to replace workers who move to other occupations or leave the labor force, for example to retire.

The Write the Docs 2025 salary survey drew 755 responses from documentation professionals in 48 countries. Among the 539 respondents whose main role was technical writer, the median salary was $90,610, with the middle half earning between $62,355 and $135,005.

By the federal measure, technical writing is a high paying job: the BLS median is $39,410 above the median for all workers. For freelancers, income depends on how many hours you can bill.

What Freelance Technical Writers Charge

No government survey measures freelance rates, but two industry sources do. The Editorial Freelancers Association’s 2026 Rate Chart is based on a survey of members from November 2025 through mid-January 2026, with over 1,100 respondents reporting what they charged during 2025. For work-for-hire technical writing, where the client “retains all rights to the material,” the median range is $1.00 a word, or $60.00 to $98.56 an hour. Ghostwritten technical writing shows 87.5 cents to $1.08 a word, or $75.00 to $126.00 an hour.

The Write the Docs survey received 80 contractor responses. The median hourly rate was $58 worldwide, based on 67 contractors, and $60 in North America, based on 47, where the middle half charged $48 to $84 an hour. Of those contractors, 57.5 percent had a single client at a time, and 24 of the 80 worked only on long contracts of 6 to 12 months or more. In this survey, documentation contracting often meant a long engagement with one client rather than many small jobs.

Here is how to turn those figures into a quote. Say you want to match the BLS median of $90,390 and expect to bill 1,200 hours a year once you subtract unpaid time for marketing and admin. You need about $75.33 an hour before business costs and self-employment tax, which the IRS puts at 15.3 percent. A 3,000-word getting started guide that takes 20 hours, including interviews with engineers and two review rounds, then costs about $1,507, which you might round up to $1,550. The FreelanceAtlas rate calculator runs the same math with your own numbers.

Quote per project when you can. A short procedure that has to be tested step by step can take longer than a long overview, so per-word pricing rarely fits technical work.

What Qualifications You Need to Become a Technical Writer

The BLS lists a bachelor’s degree as the typical entry-level education and says employers “generally prefer candidates who have a bachelor’s degree in English, communications, journalism, or a related field.” It adds that knowledge of a technical subject, “such as science or engineering, is beneficial,” and that some technical writers “begin their careers as specialists or research assistants in a technical field.” That second route suits career changers: a nurse, an electrician or a QA tester already knows a subject that needs documenting.

Google’s page on becoming a technical writer at Google is more relaxed about degrees. It says “There is no single path to becoming a technical writer at Google” and that most of its writers “come from other worlds,” including software engineers, journalists and teachers. The shared skills it lists are writing clearly in English, learning complex technologies quickly, explaining them in useful ways for the target audience, strong interpersonal skills and the ability to “Understand code.” Google says it does not care whether English is your first language or your tenth, only about the quality of the writing. You do not need to be a developer, but you should be able to follow a code sample and run it.

Do You Need a Technical Writing Certificate?

The BLS says certifications are “not mandatory,” although they can “demonstrate competence and professionalism.” If you see advice to get certified through the Society for Technical Communication (STC), check the date. In January 2025, the STC posted a notice on its website that it would dissolve the organization and stop all activities, including certification courses and exams. Write the Docs co-founder Eric Holscher reported the news on January 29, 2025, quoting the board’s statement that “our debt and operational expenses now outweigh our ongoing revenue.” For freelance work, put your time into samples that look like the documentation your target clients need.

The Skills and Tools Clients Expect

The tools depend on what a client documents. O*NET’s profile of technical writers lists the technology used in the occupation, including Git, Atlassian Confluence, Adobe FrameMaker, MadCap Flare and DITA, the Darwin Information Typing Architecture, a standard that an OASIS technical committee defines and maintains. Learn the set that matches the clients you want, and pick up paid tools such as Flare, which MadCap offers as a free trial, only when a target client or job posting asks for them.

Markdown, Git and Docs as Code

Software teams often treat documentation like code. Write the Docs defines docs as code as “a philosophy that you should be writing documentation with the same tools as code,” naming issue trackers, version control with Git, plain text markup such as Markdown, code reviews and automated tests. It adds that these concepts “are widely practiced in the software industry.” In practice, you write in Markdown, save your changes with Git, which describes itself as “a free and open source distributed version control system,” and submit the edits as a pull request that an engineer reviews.

CommonMark describes Markdown as “a plain text format for writing structured documents,” and its site links to a “Learn Markdown in 60 Seconds” tutorial. Git takes longer, but a writer needs only a small part of it: cloning a repository, creating a branch, committing changes and opening a pull request.

API Documentation Basics

If you want to write for developers, learn to read an API description. The OpenAPI Initiative calls its specification “a specification language for HTTP APIs” and notes that these specifications “are typically written in YAML or JSON.” To practice, pick a free public API and write a getting started guide that a new developer could follow without help.

Free Training: Google’s Technical Writing Courses and Style Guides

Google publishes its technical writing courses on its developer site. They are aimed mainly at software engineers, computer science students and people in engineering-adjacent roles such as product managers, but Google adds that “many technical writers or people training to be technical writers find these courses useful.” There are four:

• Technical Writing One: “the critical basics of technical writing,” with about 2 hours of pre-class work and a 2.5 to 3 hour instructor-led session.
• Technical Writing Two: intermediate topics, with 1.5 hours of pre-class work and a 2.5 to 3 hour instructor-led session.
• Tech Writing for Accessibility: 1.5 hours, as self-study or instructor-led. Google says it is “particularly useful for technical writers.”
• Writing Helpful Error Messages: a 1.5 hour self-study course.

Google gives organizations the materials to run the instructor-led sessions and occasionally runs free public sessions, but it says “the pre-class work by itself provides significant educational value.” Anyone can read the lessons on the site without paying or signing in. There is no certificate at the end, and the courses are only available in English.

Pair the courses with a published style guide. The Google developer documentation style guide says it “helps you write clear and consistent technical documentation for software developers and other technical practitioners,” and Microsoft publishes the Microsoft Writing Style Guide. Google’s careers advice says a portfolio should “Adhere to a well-known style guide,” so name the guide you followed on each sample.

How to Build a Technical Writing Portfolio With No Clients

Google’s advice to applicants without experience is direct: “If you don’t yet have a technical communication portfolio, we recommend contributing documentation to open-source projects.” It also says the portfolio should “Represent a variety of documentation types.” A practical way to build three to five samples:

1. Pick products your target clients would recognize. If you want software clients, document a free developer tool. If you want manufacturing clients, write a procedure for equipment you own or have used at work.
2. Find a documentation gap in an open-source project. GitHub’s guide to contributing to open source says “Documentation improvements are almost always welcome,” and that many projects use the “good first issue” or “help wanted” labels to point newcomers to tasks.
3. Cover more than one document type. Use the Diátaxis forms as a checklist: a tutorial, a how-to guide, a reference page and an explanation.
4. Get the work merged or published. A merged pull request shows a client that a real project accepted your writing. Link to the live page and to the pull request.
5. Show a before and after. For one sample, put the original page next to your rewrite and explain in a few sentences what you changed and why.

Google Season of Docs, which supported this kind of work from 2019 to 2024, “has concluded after six great years.” For presenting your finished samples, see What to Put in Your Freelance Portfolio When You Have No Clients.

Where Technical Writing Jobs and Freelance Clients Come From

The BLS says freelance technical writers “are either self-employed or work for a technical consulting firm” and receive “short-term or recurring assignments, such as writing about a new product.” That points to these sources of work:

• Technical consulting firms. The BLS names these firms as one of the two ways freelancers in this field work. Search for documentation and technical consulting firms in your niche and ask how they bring on contractors.
• Companies with thin documentation. Read a company’s help center or developer docs, note specific problems, and send a short pitch with a rewritten sample. The template below shows the format.
• Your former industry. If you worked in healthcare, engineering or IT support, the companies that sell into that field are natural prospects, because you already know the subject.
• The Write the Docs community. Write the Docs runs a jobs section in its monthly newsletter and a #job-posts-only channel in its Slack, where employers pay to list roles.
• LinkedIn and job boards. Set alerts for contract technical writer roles in your niche. LinkedIn for Freelancers: How to Find Clients, Build Your Profile, and Win Inbound Leads covers the profile side.

A Short Pitch to a Software Company

Lead with a specific problem you found and a sample that fixes it:

Subject: Your [product] setup guide

Hi [Name],

I am a technical writer who documents [developer tools / SaaS products]. I followed your [getting started guide] this week and got stuck at [step], because [specific problem, such as a missing step for creating an API key].

I rewrote that section as a sample: [link]. It follows the [Google developer documentation style guide], and I tested every step against version [number].

If your team needs help with [setup guides / API reference / release notes], I work at a fixed price per project. Would a 15-minute call next week be useful?

[Your name]
[Portfolio link]

For follow-up timing and more subject lines, see Cold Email for Freelancers: Templates That Actually Get Replies.

Will AI Replace Technical Writers?

The BLS gives the official answer. It expects demand to continue because technical writers are needed “to convert complex information into a format that nontechnical users of these products understand,” but adds: “However, employment growth may be slowed by artificial intelligence (AI) tools that allow these workers to be more productive.” The federal forecast is slow growth with each writer doing more.

Research on how people actually use AI shows why writing work is exposed. A Microsoft Research study, Working with AI: Measuring the Applicability of Generative AI to Occupations, analyzed 200,000 anonymized conversations with Bing Copilot. Technical writers ranked 13th among its 40 occupations with the highest AI applicability score, at 0.373, while writers and authors ranked third at 0.454. The authors warn against reading those scores as job loss forecasts: “AI’s effects on employment and wages will depend on hard-to-predict business decisions.”

People in the field are more worried than they were. In the Write the Docs survey, the share of employees feeling less confident in their job security rose from 21.9 percent in 2024 to 36.0 percent in 2025. The survey does not say why.

For a new freelancer, the practical response is to build skills that need access to the product and the people behind it: testing every step yourself, interviewing engineers and deciding how a docs site is organized. If you use AI tools for drafts, tell the client and check every step against the real product. Can Clients Tell You Used ChatGPT? (Yes, Here is the Fix) covers how clients react.

A 90-Day Plan to Start as a Freelance Technical Writer

This sequence assumes about 10 hours a week alongside a job.

1. Weeks 1 to 2: do the pre-class lessons for Technical Writing One and Two and choose one niche. How to Choose a Freelance Niche (and Actually Stick With It) walks through the decision.
2. Weeks 3 to 4: learn Markdown and basic Git, then open your first documentation pull request on an open-source project.
3. Weeks 5 to 8: write three to five samples in your niche, covering at least two Diátaxis forms.
4. Weeks 9 to 10: work out your hourly floor and turn it into project prices.
5. Weeks 11 to 12: send pitches with rewritten samples and apply for contract roles.

Conclusion

Technical writing pays well by federal measures, with a May 2025 BLS median of $90,390, and North American contractors in the Write the Docs survey reported a $60 median hourly rate. Growth is slow, with 1 percent projected from 2025 to 2035, and the BLS links that partly to AI tools that make each writer more productive. A degree is the usual entry route, but Google says there is no single path.

Start with what clients can check. Take Google’s free courses, learn Markdown and enough Git to open a pull request, and build three to five samples in one niche, including at least one merged open-source contribution. Then set a project price from your hourly floor and send pitches that show a fix for a real problem in the company’s own docs.

Key Takeaways

• The BLS reports a May 2025 median wage of $90,390 a year, or $43.46 an hour, for technical writers, against $50,980 for all workers.
• Technical writer employment is projected to grow 1 percent from 2025 to 2035, with about 3,200 openings a year, and the BLS says AI tools may slow that growth.
• The Write the Docs 2025 survey found a median contractor rate of $60 an hour in North America, and 57.5 percent of contractors worked for one client at a time.
• The EFA’s 2026 Rate Chart puts work-for-hire technical writing at $1.00 a word, or $60.00 to $98.56 an hour.
• The self-study parts of Google’s four technical writing courses take 1.5 to 2 hours each, and Google does not issue a certificate for them.
• Google recommends that people without experience build a portfolio by contributing documentation to open-source projects, and Google Season of Docs, which supported that work from 2019 to 2024, has ended.

Frequently Asked Questions

What qualifications do you need to be a technical writer?

The BLS lists a bachelor’s degree as the typical entry-level education, usually in English, communications, journalism or a related field, and says knowledge of a technical subject such as science or engineering is beneficial. Certification is not mandatory. For freelance work, samples are what a client can check, so build three to five documents in your niche that follow a named style guide before you pitch.

Will AI replace technical writers?

The BLS does not forecast replacement. It projects 1 percent employment growth from 2025 to 2035 and says AI tools that make writers more productive may slow that growth. A Microsoft Research study ranked technical writers 13th among 40 occupations with the highest AI applicability, but its authors say effects on jobs will depend on business decisions. The safest skills to build are the ones that need access to the real product and the people who built it.

Is technical writer a high paying job?

By federal data, yes. The BLS median for technical writers was $90,390 a year in May 2025, compared with $50,980 for all occupations, and the top 10 percent earned more than $145,270. Freelancers earn per hour or per project instead. The Write the Docs 2025 survey found a $60 median hourly rate for North American contractors, and your income depends on how many hours you can bill each year.

How can I start my career as a technical writer?

Start with Google’s free Technical Writing One and Two pre-class lessons, then learn Markdown and basic Git. Pick one niche, ideally one you know from past work, and write three to five samples that follow a published style guide. Contribute at least one documentation fix to an open-source project so a client can see merged work. Then pitch companies with a rewritten sample of their own docs and apply for contract roles.

How much do freelance technical writers charge?

The Write the Docs 2025 survey found a median of $58 an hour worldwide and $60 in North America, where the middle half of contractors charged $48 to $84. The EFA’s 2026 Rate Chart shows $60.00 to $98.56 an hour, or $1.00 a word, for work-for-hire technical writing. For technical work, a project price built from your hourly floor is safer than a per-word rate, because testing and interviews take time that a word count does not show.