Technical writer job description template: the documentation, the audience and the writing sample
On this page
"Technical writer: create clear documentation for complex products" covers an API writer working in a code repository next to engineers, a writer producing service manuals and work instructions for a machine builder, a medical device writer whose documents go through design control and regulatory review, and a support content writer measured on ticket deflection. They share a skill and little else: the readers, the tools, the review process and the subject matter all differ. A useful technical writer job description names the products, the readers, the document types, the authoring tools, how review works, and how much the writer must learn the subject on their own. Below are the seat types, a copy-ready template, education and classification lines with sources, screening and scorecard rows, and the mistakes that make documentation postings attract the wrong writers. For the general approach, see how to write a job description that screens.
Name the seat first
| Seat | What the work looks like | Must-have that separates it |
|---|---|---|
| Software and API documentation writer | Reference docs, tutorials, release notes, docs written in Markdown and reviewed in pull requests | Can read code and run sample requests; has published developer docs |
| Hardware or equipment documentation writer | Installation, operation and service manuals, illustrated procedures, parts lists | Has written procedures a technician followed on real equipment, working from drawings or the floor |
| Regulated documentation writer (medical device, pharma, aerospace) | Controlled documents, SOPs, labeling, change control, document reviews | Has worked in a document control system and managed revisions through formal approval |
| Support and knowledge base writer | Help center articles, troubleshooting guides, in-product help, content updates from tickets | Has improved articles using search and ticket data, not only by rewriting |
| Documentation lead or first writer | Information architecture, style guide, tooling choice, reviews, later hiring | Has set up a documentation system and a review process engineers actually used |
Then settle the facts: the products, the readers (developers, technicians, clinicians, end users), the document types, the authoring and publishing tools, whether docs live in a code repository or a content management system, who reviews for accuracy, release cadence, and who the writer reports to. If the job includes interface text in the product, say how it splits with design, and see the UX designer job description template for that side.
Education and classification lines, with sources
Not legal advice. The points below were checked against the BLS Occupational Outlook Handbook, the federal regulations and Department of Labor fact sheets as of October 2026. State overtime rules can be stricter; confirm classification with counsel.
Degree and certification. BLS says technical writers typically need a bachelor's degree, that employers generally prefer degrees in English, communications or journalism, that some writers start as specialists in a technical field, and that certification from associations is available but not mandatory (BLS Occupational Outlook Handbook, last modified August 27, 2026). Write the degree line as "or equivalent experience" unless you have a reason not to, and keep certifications in the nice-to-haves.
Exempt or nonexempt. The learned professions listed in the regulation include accounting, engineering and the sciences, not technical writing (29 CFR 541.301), so status turns on the writer's actual primary duty. The professional exemptions require either advanced knowledge customarily acquired by a prolonged course of specialized intellectual instruction, or work requiring invention, imagination, originality or talent in a recognized artistic or creative field (DOL Fact Sheet 17D); the administrative exemption is a separate test (DOL Fact Sheet 17C). Each requires a salary of at least the standard level, which the Department of Labor lists as $684 a week. A documentation lead who designs the information architecture is a different case from a writer who mostly formats content others drafted, so review each seat.
The technical writer job description template
[Senior] Technical Writer, [API and Developer Docs / Equipment
Manuals / Regulated Documentation / Knowledge Base]
[Company], [city, state] — [On-site / Hybrid: days / Remote within:
states]
Pay: $[min]–$[max] per year [or $N–$N per hour].
[Benefits summary, if required.] [Exempt or non-exempt, after review.]
SUMMARY
You will write [document types] for [product], read by [readers]
who use them to [goal: integrate, install, service, comply,
self-serve]. Docs are written in [tool] and published through
[system], reviewed for accuracy by [engineers / SMEs / QA] and
released [with each sprint / per product release / under change
control]. You will be [one of N writers / the first writer] and
report to [title].
WHAT YOU WILL DO
- Learn the product from [specs, code, prototypes, the floor,
SMEs] and write [document types] for [readers].
- Plan documentation for each release with [product / engineering].
- [Test procedures and code samples before publishing.]
- [Manage revisions through (document control system).]
- Use [search data / support tickets / reader feedback] to decide
what to fix next.
- Maintain the style guide and templates.
YOU MUST HAVE
- [N] years writing [similar documents] for [similar readers],
with samples you can share (redacted is fine).
- [Can read (code / drawings / schematics) well enough to check
your own work.]
- Working skill in [authoring tool] or similar.
- [Regulated: experience with controlled documents and formal
review.]
NICE TO HAVE
- Bachelor's degree in [field] or equivalent experience.
- Experience with [docs-as-code, structured authoring, (domain)].
If you meet the must-haves and none of these, please apply.
HOW WE HIRE
[Recruiter screen; review of two samples you choose; a writing
exercise of at most (N) minutes using material we provide;
conversation with (engineering / product) reviewers.]
[EEO STATEMENT]
Need an adjustment to apply or interview? Contact [address].Pay and EEO
Post the approved range and check pay transparency laws by state. BLS publishes pay data for technical writers in the Handbook profile linked above; this page does not quote figures. Close with a short EEO statement and an accommodation contact, and offer adjustments for the writing exercise.
From must-haves to screening questions and scorecard rows
| Must-have | Screening question | Scorecard competency | Evidence of a strong answer |
|---|---|---|---|
| Reader focus | "Pick a sample. Who was the reader, what were they trying to do, and what did you leave out for them?" | Audience judgment | A specific reader and task, and a deliberate omission |
| Learning the subject | "How did you learn the product well enough to write your last document? Who did you rely on?" | Technical learning | Hands-on testing, reading source material, targeted SME questions |
| Accuracy | "Tell me about an error that reached readers. How was it found and what changed?" | Attention to detail | Owns the error, fixes the process, not just the page |
| Working with reviewers | "How do you get busy engineers to review your drafts on time?" | Collaboration | A review process, short focused asks, escalation without friction |
| Improvement from data | "Which page did you improve because of reader data, and how did you measure it?" | Results orientation | Search terms, tickets or feedback, a change and a measured result |
For probing questions, see interview questions for written communication and interview questions for attention to detail. If the writer will sit inside an engineering team, the software engineer job description template shows how that team describes its own work.
Common mistakes in technical writer job descriptions
No reader named
"Create user-friendly documentation" could be anything. Name the readers and what they need to do.
A tool list as the requirement
Authoring tools are learned in weeks. Ask for the writing and the subject knowledge, and accept similar tools.
Unpaid real work as a test
Asking candidates to document part of your actual product for free is a poor exercise and a poor signal. Keep the exercise short and use material you provide.
Hiding the review process
If SMEs rarely review, writers will carry the accuracy risk alone. Say how review works and who signs off.
"Marketing writer" duties tucked in
Blog posts and campaign copy are a different job. If they are part of the role, give them a share of the week.
Before you publish
- The seat, the products, the readers and the document types are in the summary.
- Tools, publishing and review are described, with similar tools accepted.
- The writing exercise is short and uses material you provide.
- Classification has been reviewed against the actual duties.
- The pay range, EEO statement and accommodation contact close the posting.
Questions people ask
Does a technical writer need a degree in the technical field?
Not usually. BLS says technical writers typically need a bachelor's degree and that employers generally prefer degrees in English, communications or journalism, though some writers start as specialists in a technical field. Ask for the subject knowledge the work needs, such as reading code or schematics, and test it with a writing exercise.
Is certification required for technical writers?
No. BLS describes certification from professional associations as available but not mandatory. Treat it as a nice-to-have rather than a requirement.
Is a technical writer exempt from overtime?
It depends on the duties. Technical writing is not named in the federal regulation's list of learned professions, so status turns on whether the actual primary duty meets a test, along with a salary of at least the standard level, $684 a week as listed by the Department of Labor. A writer who mostly formats content written by others is a weaker fit. Review each seat and check state law.
What is a fair writing test for a technical writer?
Give a short, unpaid exercise of an hour or two at most, such as rewriting a confusing page or writing a procedure from a short demo or spec you provide. Tell the candidate how it will be judged. Longer exercises that resemble real deliverables should be paid or replaced with a review of past samples.