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.
Start Week 1 →Phase 1 (Weeks 1–4): Foundations
HTTP, APIs & REST Vocabulary
Databases & SQL Language
Basic Communication Patterns
Phase 2 (Weeks 5–8): Intermediate
Advanced Collocations & Phraseology
Writing: Emails, PRs & Documentation
Presentation & Explanation Skills
Phase 3 (Weeks 9–13): Advanced
Incident Response & Monitoring Language
Leadership & Mentoring Language
Negotiation & Salary Language
Conference-Level English & Final Review
Advanced phrases you will master in 90 days
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.