Example · Technical Writer
58% of your week as a technical writer is still yours.
AI now drafts docs from code and specs. Knowing where a draft is wrong stays with you.
Make my planA typical week at the middle pace. Your plan uses your own tasks.
Is technical writing dead because of AI?
In a typical week at the middle pace, 38% of this work needs your judgment and 20% is work you do using AI. AI could do about 42%. Hand a current model your OpenAPI spec and the merged PR (pull request) and it produces first drafts, reference pages, release notes, how-to articles and copyedits in minutes, at a quality a docs lead would accept after a pass. About 42% of your week sits there.
Read more
Microsoft's study of real Copilot conversations ranks technical writers near the top of all occupations for AI applicability, and in March 2026 Snowflake cut most of its documentation team and said in public that models would do the work. That is where we start.
But docs work has always been more than the pages. It means finding out what the product actually does, deciding what deserves a page, and signing that it is true before customers rely on it. If support escalates to you and the hard questions come to you, you already do that. An agent can draft a page in a minute and also invent a parameter that does not exist. That mistake gets caught only if someone has tested the endpoint. When drafting is free, the valuable person is the one who can tell the draft is wrong and who answers for it. The plan moves your week toward that person. It also changes the part you may dread, chasing engineers for review.
The week, task by task
Who does each hour of a typical 40-hour week.
See every task
Needs your judgment.
- Interview engineers and PMs to find out what a feature actually does10%
- Standup, planning, release readiness, cross-team syncs7%
- Test documented procedures against staging before publish6%
- Information architecture: what pages exist, structure, taxonomy6%
- + 2 smaller tasks8%
AI does the slow parts. You still own it.
- UX copy: microcopy, error messages, empty states with design8%
- Investigate "the docs are wrong" escalations from support8%
- Screenshots, nav and cross-links after UI changes5%
AI could do most of it.
- Draft API reference pages from OpenAPI diffs and merged PRs12%
- Draft help-center how-to articles for shipped UI features10%
- Draft release notes from tickets and PR titles8%
- Edit engineers' READMEs and support macros to the style guide7%
- + 1 smaller task5%
Why some tasks still need a person
Finding out what a feature actually does by asking the engineer instead of reading the ticket
The gap between what the PR says and what the product does lives in people's heads and in Slack. A model reading the diff sees what changed. It can't see what the PM promised a customer or which edge case was dropped.
Testing the procedure against staging before you publish it
Discovering that a published doc is wrong is expensive: a support ticket, a failed integration, a customer who no longer trusts the page. The person who runs the call before the page ships is the cheapest place that cost can be paid.
Being who support escalates to when "the docs are wrong"
Sorting "the behavior changed" from "the doc is wrong" from "the customer misread it" needs product history and a sandbox account, and it produces the one signal your docs quality can be measured by.
Deciding what pages exist and which quadrant they belong in
A model can fill any structure, but it cannot know that your enterprise customers read the webhooks page first and never open the tutorial. That is architecture, and it is the part of information design that lasts.
Holding the terminology
"Is this the right word?" is often a product decision. Consistency across app, docs and support is what makes a product feel finished, and someone has to own the list.
Good to know
What is hard about this field, and what you can do about it.
The hard truth
Technical writing is a small field with few openings.
The whole country sees about 3,200 openings a year and almost no new seats. Most openings appear only when someone leaves or retires.
Sources (2)
- About 46,400 technical writer jobs in 2025, projected to grow 1%, about 400 jobs, by 2035. BLS Occupational Outlook Handbook, Technical writers, 2025
- About 3,200 openings a year, mostly from workers who retire or change occupations. BLS Occupational Outlook Handbook, Technical writers, 2025
What's next for a technical writer?
Plan A is the best move inside the work you do now.
Grow in the job you have
The main focus. Most weekly sessions build toward it.
- Each week
- 4 sessions
- Ready in
- About 4 to 6 months
Why it fits
Why you. If you already catch what the agent invents, going from "the reviewer who catches it" to "the owner of what it may do" is a guardrails file, a linter, a test, and one conversation with your lead.
The gap. Today you may review in a browser rather than in the repo, with no Vale style rules and no doc test. If the lead set up the pilot, it is hers until your results make it yours.
The trade-off. You will write more YAML than prose, and some weeks you will feel like a build engineer. It is low-visibility infrastructure, so the value shows up in a review only if you keep the numbers. And if the platform team decides the pipeline is theirs, you will have built something you do not own.
2 other moves that fit
- Own how machines read the productReady in about 6 to 9 months
- Product management, by way of what you already knowReady in about 12 to 18 months
What's a plan B for technical writers?
Plan B is meant to be different from this job. It was picked because skills from this role carry over.
Get ready for a new kind of job
A second option. A newer job AI is creating that these skills already fit.
Deciding which pages exist and holding the terminology is exactly the knowledge curation AI agents need to give correct answers.
- Each week
- 1 session
- Outlook
- Hiring now
- Pay
- $104K to $130K a year, or $38 to $40 an hour (temp)Checkr staff posting (5+ years) and an Aquent temp posting, June 2026.
2 other options
- AI evaluation specialistTesting a procedure against staging before you publish is quality checking, and AI teams need people who verify outputs the same way.
- AI product managerAsking engineers what a feature actually does gives you product depth, and many writers move into owning an AI feature from there.
In your own plan you can switch to any of the 47 roles.
The 13 weeks
Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.
By week 13 you will have
AFor Plan A
- A rules file and style checks for the docs agent
- Two working doc tests
- A memo asking for a Senior Technical Writer or Documentation Engineer title
BAnd for Plan B
- A revised help center and a before-and-after table
- A content standard for AI, with test results, for your portfolio
- 1Measure your week and the AI
- 2Ask who owns AI quality
- 3Turn style rules into code
- 4Write rules for the agent
You finish withA finished course and one improvement to your instruction file
- 5Build your first doc test
- 6Check in on ownership
- 7Test AI answers on your docs
- 8Report on the AI pilot
You finish withA public thread with two new ideas from other writers
- 9Sign off a release
- 10Review how AI reads your API
- 11Measure output, draft the memo
- 12Make your ask
- 13Decide what's next
You finish withA one-page review of your 90 days
Three courses from the plan
- Documenting APIs: A guide for technical writers and engineersTom Johnson, idratherbewriting.com · Free (optional paid PDF)
Yes, week 5, the OpenAPI and testing chapters.
- OpenAPI Fundamentals (LFEL1011)Linux Foundation Training · Free
Yes, week 2.
- DiátaxisDaniele Procida, diataxis.fr · Free
Yes, week 3.
Checked 2026-09-22.
The fuller picture
Risks beyond AI: moderateCost-center risk
Documentation teams are cost centers and get cut in every downturn; the 2022–23 contraction hit docs and developer-relations teams hard for reasons unrelated to models. Some of today's anxiety is about AI and some is about interest rates, and the plan works either way.
Where this could be wrong
- The shares are estimates until week 1. If your log shows half your week is drafting, junior openings shrink faster and the week-6 checkpoint becomes a week-3 checkpoint.
- The docs lead may not be able to grant scope. If the week-2 answer is "that's up to Product," the memo goes to the Product director and the ask is harder.
- The employment base is ambiguous. BLS's count fell from 56,400 in its 2024 edition to 46,400 in its 2025 edition. Some of that may be reclassification. If not, the profession shrank by a sixth in a year and the moderate scenario is optimistic.
- The Snowflake figures are from press accounts, not a primary filing. The count might be off, but the direction is clear.
Also matched: technical writer, documentation writer, api writer. Research checked 2026-09-22. Page updated .