Esc
↑↓ navigate   Enter open   Esc close
📄 Technical Writer

90-Day English Deep Dive for Technical Writers

A comprehensive 3-month programme that takes you from solid plain-language vocabulary to full professional fluency in technical writing English. Over 13 weeks you will master the Diataxis framework and documentation types; develop API documentation, docs-as-code, and Git collaboration vocabulary; build confident SME interview and content strategy skills; and reach advanced fluency for UX writing, cross-team advocacy, and career interviews.

Advanced 90 days · 13 weeks · 3 phases · 1–2 hrs/week · Full role guide →
Start Week 1 →
1
Foundations
Weeks 1–4
Plain language, the Diataxis framework, knowledge base writing, and daily async communication
2
Technical Depth
Weeks 5–8
API documentation, code comments, Git/docs-as-code workflows, and CI/CD pipeline language
3
Advanced
Weeks 9–13
SME interviews, changelog writing, UX microcopy, content strategy, and interview preparation

Phase 1 (Weeks 1–4): Foundations

Phase 2 (Weeks 5–8): API Documentation & Technical Depth

Phase 3 (Weeks 9–13): SME Collaboration, Content Strategy & Career

Advanced phrases you will master in 90 days

Diataxis
"This page mixes reference and how-to modes — following Diataxis, I'd split it into two documents."
content debt
"We have significant content debt in the webhooks section — three guides describe a deprecated flow."
docs as code
"We migrated to docs as code — every page goes through the same PR review as our application code."
SME (subject matter expert)
"I need 20 minutes with the SME to confirm the retry behaviour before I finish this section."
restate for confirmation
"Let me restate that back to confirm I've understood the retry logic correctly before writing it up."
breaking change
"This is a breaking change — the changelog needs a migration note, not just a one-line description."
progressive disclosure
"We use progressive disclosure — the basic config is inline, advanced options are collapsible."
single-sourcing
"We single-source the rate-limit warning so it stays in sync across the quickstart and reference."
microcopy
"The microcopy on this error state needs to explain the fix, not just state that something failed."
content audit
"We're running a content audit before the redesign — flagging anything outdated or duplicated."
Technical Writer — 30 Days
The 30-day foundation path — complete this before or alongside the 90-day programme
Backend Developer — 90 Days
Build the API and architecture vocabulary that complements your documentation work
Technical Writer Guide
Comprehensive reference guide for all areas of technical writing English — use alongside this path

Frequently asked questions

Who is the 90-day Technical Writer English deep dive designed for?

This programme is designed for technical writers at all levels who work in English-speaking teams or with international engineers, product managers, and readers. It covers the specific vocabulary of documentation frameworks, API reference writing, SME collaboration, content strategy, and UX microcopy.

What English level is required for the 90-day Technical Writer path?

You should be at B2 level or above. The path builds from plain-language and Diataxis foundations in Phase 1 to advanced content strategy and career communication in Phase 3. If you can write a clear how-to guide but struggle with SME interviews or PR reviews, this path will close that gap.

How much time per week does the 90-day path require?

Each week has 4 resources, each taking approximately 20–30 minutes. Total weekly commitment is 1.5–2 hours, spread across 4 sessions. This is sustainable alongside a full-time technical writing role.

What API documentation language is covered in this path?

Weeks 5 and 6 cover the complete API documentation vocabulary: endpoint and parameter description language, OpenAPI spec conventions, versioning language, and code comment/docstring writing for developer-facing reference documentation.

Does the path include docs-as-code and Git workflow vocabulary?

Yes. Weeks 7 and 8 focus on docs-as-code vocabulary: Git and version control terminology, writing documentation pull requests, responding to code review comments, GitHub platform vocabulary, and CI/CD pipeline language for automated docs builds.

Is SME (subject matter expert) interview training included?

Yes. Week 9 is dedicated entirely to SME interview technique: funnel questioning, restating answers for confirmation, stakeholder management, and onboarding/knowledge transfer writing.

Does this path cover UX writing and content strategy?

Yes. Phase 3 includes dedicated weeks on UX writing, microcopy, and accessibility (week 11) and content strategy and cross-team advocacy (week 12). These weeks cover the English for error messages, empty states, style-guide governance, and influencing engineering teams on documentation priorities.

What changelog and release note vocabulary is covered?

Week 10 covers changelog and release note writing in depth: "Keep a Changelog" conventions, breaking-change communication, developer advocacy content writing, and technical content creation for tutorials and blog posts.

What should I do after completing the 90-day Technical Writer path?

After completing this path, explore the Technical Writer guide for comprehensive reference material. Consider also completing relevant weeks from the Backend Developer or DevOps path to build the engineering vocabulary for the systems you document most closely.

Ready for the deep dive?

Begin Week 1 and commit to 90 days of structured English mastery.

Start Week 1 → 30-day path first All learning paths