The credential most technical writing roundups still recommend no longer exists. The Society for Technical Communication, which developed the Certified Professional Technical Communicator scheme, announced in January 2025 that it was dissolving and ceasing all activities, including certification courses and exams. Its site now shows only a maintenance notice. If you were planning to sit that exam, you need a different plan.
That closure matters beyond one exam. It removed the field's only association-backed standard, which means every remaining option is either university continuing education, vendor training, or an independent course provider. None of them carry professional accreditation, so the useful question is no longer which certification is official. It is which one produces evidence a hiring manager can check.
My first technical writing job was documenting video editing software at twenty-three, interviewing editors who had cut top-tier films and learning their vocabulary well enough to write tutorials in it. Nothing on my resume proved I could do that. A work sample did. I keep that in mind whenever I look at a course fee. I verified the issuer, format, hours, and listed price for every program below against official pages, and I have not personally enrolled in each one, so treat this as researched public information rather than firsthand student reviews.
The Technical Writing Certifications I Would Consider
Certificate in Professional Technical Writing from the University of Washington: Best instructor-led university program
Technical and Professional Writing Certificate from the University of Delaware: Best stackable self-paced university option
Certificate in Technical Writing from Dalhousie University: Best structured Canadian certificate
Technical Writing Certificate Program from Kansas State University Salina: Best budget microcredential
Certified Technical Writer from Technical Writer HQ: Best low-cost self-paced credential
API Documentation Path from Postman Academy: Best free specialization for API work
The spread here is intentional. The cheapest option on the list is free and the most expensive is over four thousand dollars, and the difference is not quality of instruction so much as structure, feedback, and how much institutional weight the name carries. Decide which of those three you are buying before you compare prices.
My Reviews of the Best Technical Writing Certifications
Each review covers who issues the credential, the format and time commitment, the current listed fee, and the reader I think it fits. Course fees and start dates change every term, so confirm them on the official page before enrolling.
University of Washington: Best Instructor-Led University Program
The University of Washington Professional and Continuing Education Certificate in Professional Technical Writing is a three-course online program listed at $4,195, delivered in the evenings over about eight months, with a next start date of September 30, 2026. The program expects roughly seven to nine hours of work each week including class time, and the current curriculum includes applied AI tools and publishing workflows alongside traditional documentation skills.
There are entry requirements, which is unusual on this list and is part of the value. Applicants need either four years of college plus two years of work experience or two years of college plus four years of work experience, along with working knowledge of authoring tools such as Microsoft Word. That screening keeps the cohort at a level where peer feedback is worth something.
I would only spend this much in two situations. The first is an employer paying for it. The second is a career change where you need a recognized university name on your resume to explain the pivot, in which case the school also publishes scholarship options worth checking before you enroll.
University of Delaware: Best Stackable Self-Paced University Option
The University of Delaware Division of Professional and Continuing Studies offers a noncredit Technical and Professional Writing Certificate built with the university's English department. It runs as three stackable self-paced courses, each listed at $950 with thirty-six contact hours and four months of access, or $1,990 for the full certificate. Learners earn digital badges per course and a digital certificate of completion at the end.
The stackable structure is the reason it is on my list. You can buy the foundations course alone, find out whether the work suits you, and stop without wasting two thousand dollars. The syllabus also reaches beyond prose into document design, data visualization, usability, and digital accessibility, which reflects what the job now involves.
Note the practical terms. The later courses require the foundations course first, access expires after four months per course, and refunds are limited to five days from registration with an administrative fee. That is a reasonable policy, but it means you should start a course when you actually have the hours available.
Dalhousie University: Best Structured Canadian Certificate
Dalhousie University offers a Certificate in Technical Writing through its continuing education arm, requiring four courses and seventy-two hours, with a listed certificate fee of $2,316 at the time of writing. The required course is Technical Writing Essentials, and electives include project management documents, writing clear technical reports, and writing effective emails, each delivered online and self-paced across scheduled terms.
What I like here is the deliverable focus. Report writing and project documentation are the artifacts that pile up in engineering, government, and consulting work, and a program organized around document types tends to leave you with samples rather than notes. If you want a sense of the output standard, these examples of well formatted documentation show what reviewers look for.
The constraint is scheduling. Courses open in specific terms rather than on demand, so the completion timeline depends on when your electives are offered. Check the current term calendar before assuming you can finish in a particular year, and confirm whether the fee is charged in Canadian or US dollars at checkout.
Kansas State University Salina: Best Budget Microcredential
Kansas State University Salina runs a fully online Technical Writing Certificate Program built from four-week courses at $149 each, with one course free when you register for all four at the same time. No previous experience is required, learners can take a single course for a microcredential, and completing all four earns a badge.
This is the option I would point a curious beginner toward. Four weeks and under two hundred dollars is a small enough bet to find out whether you enjoy documenting a process, which is the real test. Plenty of people like the idea of technical writing and dislike the actual work of chasing an engineer for the third time to confirm a parameter.
Keep expectations proportional to the price. A short university microcredential signals initiative, not seniority, and it will not outweigh a portfolio in a competitive applicant pool. Use it as a structured excuse to produce your first two samples.
Certified Technical Writer: Best Low-Cost Self-Paced Credential
Technical Writer HQ runs the Certified Technical Writer course, an online self-paced program listed at $299 with lifetime access. The official page describes ninety-five video lessons with assignments and quizzes, a capstone project, and a study pace of about four hours a week over ten weeks. It ends with a certification exam and a capstone submission, and the credential is hosted on the issuer's own site.
I need to disclose that I founded Technical Writer HQ, so read this entry as a disclosure rather than an impartial review. What I can say neutrally is why the format exists. It was built for people who need a structured path and a portfolio artifact quickly without committing several thousand dollars, which is the most common situation I saw when people asked me how to break into the field.
The tradeoff of any self-paced program at this price is that the accountability is yours. There is no cohort waiting on your draft and no weekly deadline. If you have historically needed a scheduled class to finish anything, pay more for one of the instructor-led programs on this list instead of saving money on a course you will abandon in week three.
Postman Academy API Documentation Path: Best Free Specialization
Postman Academy publishes a free API Documentation Path made of short modules covering Postman fundamentals, an introduction to API documentation, building organized collections from an API definition, and writing documentation for internal and external audiences. Each module runs from roughly fifteen to forty minutes, and the path is delivered by the vendor whose tooling many API teams already use.
API documentation is where the pay premium sits, and this is the cheapest credible entry into it. Learning the tool your future team already runs is also a shortcut into the conversation, because you can open a collection, read a request, and ask a specific question instead of a general one. My roundup of tools teams use to publish API references covers what sits around it in a real stack.
Be clear about what it is not. This is vendor training, not an independent certification, and it will not teach you documentation strategy or information architecture. Pair it with one of the broader programs above, or with a real open-source project where you can document endpoints someone else has to use.
The Free Foundation Almost Everyone Should Start With
Before spending anything, work through Google's technical writing courses, which are published free for engineers and anyone in an engineering-adjacent role. They are the same courses Google engineers take, they assume only basic writing proficiency in English, and they teach the habits that separate usable documentation from correct-but-unreadable documentation.
There is no certification attached, which is the point. If you cannot get through free structured material on your own time, a paid program will not fix that. If you can, you will arrive at the paid course already able to recognize a bloated sentence, which means you spend the tuition on feedback rather than on basics. Pair it with the worked examples of technical documents so you can see the formats you will be graded on.
How I Would Choose Between Them
Match the program to the obstacle in front of you. If nobody will interview you because you have no samples, buy the cheapest option that forces you to produce documents. If you are already writing but stuck in a junior band, buy the program with graded feedback and a named institution. If you want to move into higher-paying developer documentation, specialize in APIs and prove it with published work.
Then check four terms that quietly decide value. Find out whether a human assesses your work or a quiz does. Find out how long you keep access to the material. Find out whether the program produces a portfolio artifact you can publish. And find out whether the credential expires, because renewal obligations are easy to miss at purchase and annoying later.
Compare the total against the salary you are targeting rather than against other courses. Current pay ranges for technical writers vary widely by industry and seniority, and a four-thousand-dollar program is easy to justify against a senior software documentation role and hard to justify against a first junior position you could win with two good samples.
What Certifications Do Not Solve
The hardest part of this job is not writing. It is extracting accurate information from busy subject matter experts and fitting documentation into a development cycle that was planned without you. I learned both the slow way, by sitting with engineers and editors until I understood their language well enough to write in it. No course grades that skill, because it only shows up under deadline pressure with a real product.
Certifications also will not tell you which specialty to enter, and that choice affects your income more than any credential. Software, hardware, medical, and financial documentation reward different backgrounds and pay differently. Reading through the usual progression from junior writer to documentation lead is a better use of an afternoon than comparing two more syllabi.
So here is the order I would follow. Work through the free Google courses, publish two real documents, ideally by contributing to an open-source project that needs a clear setup guide, then buy the smallest paid program that closes your remaining gap. If you want a wider view of paid options before committing, my comparison of structured technical writing courses covers the training market that sits underneath these credentials.
Conclusion
Choosing the right technical writing certification depends on your goals, skill gaps, and budget. Certifications can enhance expertise, demonstrate technical fluency, and help build portfolio samples, but they can't replace clear, practical work. Start with free resources like Google’s technical writing courses for basics, then invest in programs that address specific gaps.
For beginners, options like Kansas State’s microcredential or Technical Writer HQ’s Certified Technical Writer help create portfolio samples affordably. Advanced professionals can consider university-led programs, such as the University of Washington’s certificate, or specialized training like Postman Academy’s API path for higher-paying roles. Focus on certifications that provide feedback, deliverables, and actionable skills to complement hands-on experience.
Related Resources
Frequently Asked Questions
Here are the most frequently asked questions about technical writing certifications.
Is the STC certification still available?
No. The Society for Technical Communication announced in January 2025 that it was dissolving and ceasing all activities, explicitly including certification courses and exams. People who already hold the credential keep their badge, but new candidates cannot currently sit the exam, and any roundup still recommending it as a live option is out of date.
Do employers require a technical writing certification?
Almost never. Job postings usually ask for writing samples, documentation experience, and enough technical comfort to work with engineers. A certification helps you get read when your background is in another field, and it helps you learn faster, but a portfolio of clear documents is what moves you through the process.
How much do technical writing certifications cost?
The programs reviewed here range from free vendor training and about $149 for a single university short course to roughly $4,195 for an eight-month instructor-led certificate. Self-paced independent courses sit in the low hundreds, and multi-course university certificates generally fall between two and four thousand dollars.
How long does it take to get certified?
Plan on four weeks for a single short course, two to three months for a self-paced certification at a few hours a week, and six to twelve months for a multi-course university certificate delivered across terms. Self-paced programs finish faster on paper and slower in practice, because nothing enforces the schedule.
Which certification is best for API documentation?
Start with free vendor training on API tooling, then prove the skill on something public. Documenting a real endpoint set, including authentication, request examples, and error responses, demonstrates far more than a certificate. Add a general technical writing program if you also need structure, style, and information architecture.
Are university certificates better than online courses?
They are different purchases. University continuing education buys scheduled instruction, human feedback, entry screening, and a recognizable name, which helps most during a career change. Independent online courses buy speed and a low price. Neither is accredited as a professional license, so judge them on assessment and output.