It's the classic catch.
Employers want to see technical writing samples. But you can't get samples without a technical writing job.
Here's the good news: you don't need a job to build a strong portfolio.
You need a few well-chosen pieces. Pieces that show how you think and how clearly you write.
Here's what to include.
Where to find subjects.
How to present your work.
And what to avoid.
There's a checklist at the end, too.
There's no license for technical writers. The U.S. Bureau of Labor Statistics describes certification as "not mandatory."
So when a hiring manager decides whether to interview you, your samples usually carry the most weight.
They answer the only question that really matters.
Can this person write the documents we need?
(More on what employers look for, and why it isn't a certification.)
Three to five.
Strong and varied beats long and average. Many hiring managers look closely at only one or two pieces. So every sample should be one you're proud of.
Aim for range.
Something procedural. Something explanatory. Something that shows your editing judgment.
Here's a mix that works:
| Sample type | What it proves | A beginner-friendly idea |
|---|---|---|
| Step-by-step instructions | You can turn a task into clear, ordered steps | Set up a feature in an app you use every day |
| Standard operating procedure (SOP) | You document precisely enough for someone to repeat it | An SOP for a fictional lab, kitchen or small business |
| Conceptual overview | You can explain how something works to a non-expert | A one-page explainer on a common technology |
| Troubleshooting guide | You anticipate problems and organize solutions | "If X happens, try Y" for a device you know well |
| Before-and-after rewrite | You have editing judgment | Make confusing public instructions clear |
| API or developer docs | You can write for technical users | Document a free, public API with sample requests |
One tip: real subjects beat invented ones.
A clear rewrite of instructions for a real, widely used tool shows more than a manual for a made-up product.
Work in a lab, clinic or plant? You may have more material than you think. Here's how to turn SOP experience into samples safely.
Hiring managers want to know how you work.
So add a short note to each sample. Just a few sentences:
Here's what that looks like in practice:
That before-and-after edit is one of the fastest ways to stand out. It shows how you think, not just what you produced.
It matters even more now that AI tools can produce a first draft. Judgment is what employers are hiring for. (See how the job is shifting.)
Applying for software documentation roles? Include something technical, like a developer guide or API reference.
Aiming for health care, life sciences or manufacturing? Include a procedure.
The wrong mix can make rejections feel random. So tailor your top two or three samples to each type of job.
You'll want to set up a home base for your portfolio, so folks can find it and you can show it off.
Whatever you choose, test every link. And check that each sample opens quickly on a phone.
Only include work you have the right to share.
Wrote something for an employer or client? Ask permission first, or recreate a similar sample from scratch.
And never include internal documents, customer information or anything with personal or health information. Not even with names removed.
Before you send your portfolio, check every item:
☐ I have three to five samples, and I'm proud of each one.Oregon State University's online Technical Writing Certificate is built around producing portfolio pieces.
Each course has you write real document types: manuals, usability documents, SOPs and flowcharts. And an OSU writing instructor gives you feedback every week.
The final course, Technical Writing Portfolio Creation, helps you select, edit and present your best work in a WordPress portfolio. With practical SEO, so hiring managers can find it.
No prerequisites. No set class times. Take any course on its own before committing to the full certificate.
Weighing whether paid training is worth it? Here's an honest look at cost, time and pay. And see how a portfolio paid off for graduate Samantha Edington.
Three to five strong, varied samples are enough for most applications. Quality matters more than quantity.
Rewrite confusing public instructions, document a tool you already use, contribute to open source documentation or volunteer for a nonprofit. Recreated samples from scratch work well too.
A simple personal website, such as one built with WordPress, works for most people. GitHub Pages suits software roles. Keep PDF versions ready to attach to applications.
Only with permission, and never anything confidential or containing personal or health information. Recreating a similar sample from scratch is usually safer.
Clear, accurate writing that fits the job, variety across document types, evidence of editing judgment, and short notes explaining the audience, purpose and your role.
Ready to start?
The Free Intro to Technical Writing is self-paced and takes about 2 to 10 hours. Along the way, you'll write a technical memo. A solid first piece for your portfolio.
Want more free practice? Here are the best free technical writing courses.
Source: U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Technical Writers.