Technical Writer / Documentation Specialist

1. 1
   Complete Google's Technical Writing Courses — Free

   Google's Technical Writing One and Technical Writing Two courses (free at developers.google.com/tech-writing) are the most respected free technical writing resources available. Technical Writing One covers: clear sentences, active voice, lists and tables, paragraphs, and audience analysis. Technical Writing Two covers: self-editing, organizing documentation, illustrating, and creating sample code. Complete both before any other investment — they represent industry best practices from the world's largest developer documentation team.

   Google Technical Writing One and Two — free
2. 2
   Learn Docs-as-Code Tooling

   Modern technical writing uses a "docs-as-code" approach — documentation is written in plain text (Markdown or reStructuredText), version-controlled in Git, and built with static site generators. Core tools: Markdown (the universal plain text markup format), Git and GitHub (version control — technical writers work alongside developers in the same repositories), static site generators (MkDocs, Docusaurus, Sphinx — the most common documentation platforms), and Jekyll or Hugo for API reference sites. Building a documentation site from scratch using one of these tools is the most practical first portfolio project.

   Markdown + Git + MkDocs or Docusaurus
3. 3
   Develop API Documentation Skills

   API documentation is the highest-paying technical writing specialty — used by developers integrating with software platforms. Skills: understanding REST APIs (endpoints, methods, request/response structure, authentication), reading OpenAPI/Swagger specifications, writing endpoint reference documentation, and creating quickstart guides and SDK documentation. Practice: find an open API (Stripe, Twilio, or any public API), read its existing documentation critically, and write improved documentation for 3 endpoints as a portfolio exercise. The Postman API Fundamentals Student Expert certification is a useful free credential.

   REST API documentation + OpenAPI/Swagger + Postman
4. 4
   Build a Documentation Portfolio

   Technical writing portfolios contain samples of documentation work: a user guide for a software product, an API reference for a real or hypothetical API, a quickstart tutorial, and a troubleshooting guide. Use real open-source projects — contribute documentation improvements to projects on GitHub (this builds both portfolio content and open-source contribution history, visible on your GitHub profile). GitHub contributions to well-known open-source projects are strong portfolio signals to tech company hiring managers.

   Documentation portfolio + open-source contributions
5. 5
   Pursue STC CPTC or Google Developer Documentation Cert

   STC Certified Professional Technical Communicator (CPTC) from the Society for Technical Communication ($500–$700 depending on STC membership) is the professional credential for the technical writing field. Google's Developer Documentation Style Guide certification demonstrates familiarity with the industry-standard style guide used throughout the tech industry. For senior roles, DITA (Darwin Information Typing Architecture) expertise — the structured authoring standard used in aerospace, defense, and medical device documentation — commands significant premium.

   STC CPTC or DITA specialization

• 9:00 AMNew API endpoint documentation — the engineering team shipped the new Webhooks v2 API yesterday. Pull the OpenAPI spec, read the code comments, schedule 30-minute interview with the lead engineer to understand use cases and edge cases. Draft the endpoint reference: overview, authentication requirements, request parameters, response schema, error codes, and a curl example.
• 10:30 AMSME interview — 30 minutes with the engineer. Clarify: what's the difference between synchronous and asynchronous webhook delivery? What happens when the endpoint is unavailable — does it retry? How does the signature verification work? Fill in the gaps in the draft documentation.
• 11:00 AMQuickstart guide — write a 5-minute quickstart for new developers: how to create your first webhook subscription, verify the signature, and handle the event payload. Test each code example in Python and Node.js to verify it actually works as documented. Fix two errors discovered during testing.
• 12:00 PMLunch — 30 minutes.
• 1:00 PMPR review — documentation PR from a developer contributor. They've added documentation for the new rate limit headers but the description is technically accurate but unclear for the audience (external developers unfamiliar with our infrastructure). Rewrite the description with a plain-English explanation and a table showing the header values.
• 2:30 PMDocumentation audit — running a quarterly audit of the authentication section. Check every code example against the current API version. Find two deprecated parameter names still in the examples. Update and submit as a fix PR. Check internal links — three broken links to deprecated endpoints. Fix.
• 4:30 PMDeveloper feedback review — weekly review of developer forum questions tagged #docs. Three questions that reveal documentation gaps: the OAuth flow diagram is missing the token refresh step. Add to the backlog and estimate 2 hours to fix. Write a clarifying comment in the forum thread while the doc update is in progress.

Technical writing is one of the most directly disrupted fields by AI — LLMs can draft documentation, API references, and user guides quickly and competently. The resilient tier is the technical writer who deeply understands complex systems, manages documentation strategy, and ensures accuracy that AI hallucinations can compromise. Specialization in complex domain expertise is the strongest defense.