14-Day English Crash Course for Technical Writers
Intensive Sprint

This crash course is for technical writers, documentation engineers, and developers moving into technical writing who need focused, fast improvement in professional English — before a new role, a portfolio review, or when joining an international documentation team. It covers the 14 highest-priority vocabulary and communication areas: from plain language and the Diataxis framework to API documentation, SME interviews, and interview preparation.

The course is designed for B1–B2 English learners (intermediate). You should be able to hold basic conversations in English. The course improves your professional and technical writing English, not general English from scratch.

Each day is designed for 20–30 minutes: roughly 10 minutes on vocabulary and 15 minutes on the exercise. The intensive format keeps sessions focused — every day is tied directly to vocabulary and scenarios from real technical writing work.

Yes. Day 2 focuses specifically on the Diataxis documentation framework — the vocabulary for distinguishing tutorials, how-to guides, reference material, and explanation, and the English used to diagnose when a document has drifted between modes.

Yes. Days 4 and 5 cover API documentation vocabulary and hands-on practice writing endpoint and parameter descriptions — the precise, structured English used in OpenAPI-based reference documentation.

Yes. Day 8 focuses on SME interview technique — funnel questioning, restating answers for confirmation, and tactfully pushing engineers for precision without being adversarial. See /exercises/meetings/ for the practice exercises.

Yes. Day 10 covers docs-as-code workflows — writing documentation pull request descriptions, requesting the right kind of review from engineers, and responding to review comments professionally using code review language.

The 14-day crash course covers the 14 highest-priority areas in a condensed format. The 30-day path goes deeper — adding UX microcopy, style guide governance, content strategy vocabulary, developer advocacy writing, and a full week of career and portfolio communication.

Yes. Days 13 and 14 cover technical writer interview speaking and salary negotiation phrases. See /exercises/interview/technical-writer-questions/ for the full exercise set.

After the crash course, move to the 30-day Technical Writer path for deeper coverage of UX writing, style guides, and content strategy. You can also read the full Technical Writer guide or browse all exercises.