14-Day English Crash Course for DevOps/SRE Engineers
Intensive Sprint

This crash course is for DevOps and SRE engineers who need focused, fast improvement in technical English — before a new role, a technical interview, or when joining an international team. It covers the 14 highest-priority vocabulary and communication areas for DevOps and SRE work.

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 English, not general English from scratch. If you are unsure of your level, try Day 1 — if the vocabulary feels completely unfamiliar, build general English skills first.

Each day is designed for 20–30 minutes: roughly 10 minutes on vocabulary and 15 minutes on the communication or technical exercise. The intensive format keeps sessions focused and efficient — every day is tied directly to tools and scenarios you encounter on the job.

The course covers Docker and containerisation vocabulary, Kubernetes and orchestration language, CI/CD pipeline terminology, infrastructure as code language, monitoring and observability vocabulary, alerting and on-call phrases, incident response language, SLO/SLA/error budget terminology, cloud cost and FinOps vocabulary, postmortem language, and technical interview and salary negotiation phrases.

Yes. Days 3 and 4 focus specifically on Kubernetes vocabulary — including pods, deployments, services, ingress, namespaces, resource limits, and the English used when discussing cluster configuration, scaling, and troubleshooting in team discussions and documentation.

Yes. Day 10 covers SLO, SLA, and error budget vocabulary — including service level objectives, error budgets, burn rates, and the English phrases used when discussing reliability targets with product managers and engineering leadership.

Yes. Day 9 focuses specifically on incident response language — the vocabulary and phrases used during active incidents: declaring incidents, providing status updates, coordinating mitigation, and writing postmortem summaries. Day 12 covers blameless postmortem language and writing. See /exercises/incident-response/ for the exercises.

The 14-day crash course covers the 14 highest-priority areas in a condensed format. The 30-day path goes deeper — adding advanced topics like distributed systems, chaos engineering, capacity planning, multi-cloud vocabulary, and a comprehensive week of communication and leadership language.

Yes. Days 13 and 14 focus on DevOps/SRE technical interview speaking and salary negotiation phrases — covering system design discussion language, on-call experience vocabulary, and the phrases used when negotiating compensation at engineering job interviews. See /exercises/speaking/technical-interview-speaking/.

After the crash course, move to the 30-day DevOps/SRE path for deeper coverage of advanced infrastructure, reliability engineering, and leadership communication. You can also explore the full exercise library at /exercises/ or the DevOps vocabulary set.