14-Day English Crash Course for Frontend Developers
Intensive Sprint

This crash course is for frontend developers who need focused, fast improvement in technical English — before a new job, a technical interview, or when transitioning to an international team. It covers the 14 highest-impact vocabulary and communication areas for frontend 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 exercise. The intensive format keeps each session focused and practical. Optional blog reading adds another 10–15 minutes if you want more context.

The course covers HTML, CSS, and JavaScript vocabulary, browser API and DOM terminology, React and framework language, IT collocations, performance and optimisation terms, accessibility vocabulary, design system and component language, CSS layout collocations, testing vocabulary, code review phrases, design handoff communication, standup phrases, and interview and negotiation language.

Yes. Day 3 focuses on React and modern framework vocabulary — including terms like props, state, hydration, virtual DOM, reconciliation, hooks, and the English phrases used when discussing component architecture in code reviews and standups.

Yes. Day 6 covers accessibility (a11y) vocabulary — including ARIA roles, semantic HTML language, keyboard navigation terminology, WCAG compliance phrases, and how to discuss accessibility requirements with designers and QA engineers in English.

The 14-day crash course covers the 14 highest-priority areas in a condensed format. The 30-day path goes deeper — adding CSS architecture, state management vocabulary, build tooling language, advanced component API communication, and a full week of interview and career preparation. Start with 14 days for a quick sprint; use 30 days for comprehensive coverage.

Yes. Day 11 focuses on design handoff and client communication — the English phrases used when receiving designs from Figma, asking clarifying questions to designers, and communicating implementation constraints to non-technical stakeholders.

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

After the crash course, move to the 30-day frontend path for deeper coverage of CSS architecture, state management, build tools, and advanced interview preparation. You can also browse all exercises at /exercises/ or start the QA Engineer 14-day path if your role overlaps with testing work.