⚙️ Backend Developer

90-Day English Deep Dive for Backend Developers

A comprehensive 3-month programme that takes you from solid technical vocabulary to full professional fluency in backend engineering English. Over 13 weeks you will master the language of APIs, databases, and architecture; develop confident written communication for PRs, emails, and documentation; and build the advanced vocabulary for system design discussions, leadership, negotiation, and conference presentations.

Advanced 90 days · 13 weeks · 3 phases · 1–2 hrs/week · Full role guide →
Start Week 1 →
1
Foundations
Weeks 1–4
Core vocabulary, HTTP/APIs, databases, basic communication
2
Intermediate
Weeks 5–8
Architecture vocabulary, collocations, writing (emails, PRs, docs), presentation skills
3
Advanced
Weeks 9–13
System design vocabulary, leadership language, negotiation, conference-level English

Advanced phrases you will master in 90 days

blast radius
"We need to minimise the blast radius if this service fails — isolate it with circuit breakers."
thundering herd
"After a cache miss, the thundering herd of requests brought the database to its knees."
back-pressure
"The queue is applying back-pressure — consumers can't keep up with the producer rate."
fan-out
"This write operation fans out to twelve downstream services — consider event sourcing."
two-phase commit
"Two-phase commit guarantees atomicity but introduces latency — is that an acceptable trade-off?"
toil
"Automating deployments reduced our toil by about four hours per sprint."
north star metric
"Our north star metric is p99 latency for checkout — everything else is secondary."
RFC
"I've written an RFC for the new caching strategy — please leave comments by Friday."
DRI
"The DRI for this migration is Sarah — all decisions go through her."
runbook
"The on-call runbook covers the five most common incident scenarios for this service."

Frequently asked questions

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

This programme is designed for mid-to-senior backend developers who already have a working knowledge of technical English but want to reach fluency in system design discussions, architecture reviews, leadership communication, and conference-level presentations. It builds on the vocabulary from the 30-day path.

What level of English do I need to start the 90-day path?

You should be at B2 level or above — able to communicate confidently in English technical discussions. This path advances your vocabulary into C1 territory: nuanced negotiation language, complex architecture vocabulary, and the precise English needed for technical leadership roles.

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

Each week is structured for 1–2 hours of focused study spread across the week: 3–5 resources per week averaging 20–30 minutes each. You can fit this into a busy schedule by spreading the resources across weekday evenings.

How is the 90-day path structured differently from the 30-day path?

The 30-day path is organised by individual days covering core vocabulary and communication patterns. The 90-day path is organised by weeks with themes that build toward advanced fluency: Phase 1 establishes foundations, Phase 2 develops intermediate communication and writing skills, and Phase 3 covers system design, leadership, and conference-level English.

Does the 90-day path cover technical writing?

Yes. Week 7 focuses specifically on technical writing: professional emails, pull request descriptions, and documentation language. Phase 2 throughout develops written communication skills so you can write clear, professional technical content for both internal and external audiences.

What vocabulary does Phase 3 (Weeks 9–13) cover?

Phase 3 covers the most advanced vocabulary for backend engineers: system design and distributed systems language, incident response communication, leadership and mentoring vocabulary, negotiation and salary discussion language, and the presentation skills needed for conference talks and architecture reviews.

Can I do the 90-day path without completing the 30-day path first?

Yes, if your English is already at B2+ and you have experience in backend development roles. Phase 1 of the 90-day path revisits foundation vocabulary at a faster pace. However, if you are unsure, completing the 30-day path first will give you a stronger base to build on.

Is there content for architects and staff engineers in this path?

Yes. Phase 3 is specifically aimed at senior and staff-level engineers. Weeks 9 and 10 cover system design and architecture vocabulary, week 11 focuses on leadership and mentoring language, and weeks 12 and 13 cover negotiation and high-stakes technical communication — all areas where architects and staff engineers need precise English.

What makes the 90-day path different from just browsing exercises?

The 90-day path provides a curated sequence — each phase builds on the previous one, vocabulary compounds over time, and the progression from foundations through intermediate to advanced follows a deliberate pedagogical order. Browsing exercises randomly misses the cumulative effect of structured, sequential learning.

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

After completing the 90-day path, you will have covered all core and advanced English for backend development. Next steps: maintain active vocabulary by applying it in real work, explore the Backend Developer guide at /guides/backend-developer/ for reference, contribute to open source projects in English, or explore the DevOps/SRE 90-day path to complement your skills.

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