Difficulty:
Filter by role:

Where to start — by your role

New here? Pick your role and follow a focused 4-step path to fluency in your day-to-day English. Or explore full role-based learning paths →

Frontend Developer
  1. 1 Vocabulary — Frontend set
  2. 2 Reading — API docs & YAML configs
  3. 3 Writing — PR descriptions
  4. 4 Interview — Frontend questions
Backend Developer
  1. 1 Vocabulary — Backend + API sets
  2. 2 Writing — API endpoint docs
  3. 3 Interview — Backend questions
  4. 4 Speaking — System design talk-through
Full-Stack Developer
  1. 1 Vocabulary — Frontend + Backend sets
  2. 2 Writing — PR descriptions + API docs
  3. 3 Collocations — Developer daily actions
  4. 4 Interview — Full-stack questions
Mobile Developer
  1. 1 Vocabulary — Mobile set
  2. 2 Writing — Release notes
  3. 3 Reading — Crash report / App Store rejection
  4. 4 Interview — Mobile questions
DevOps Engineer
  1. 1 Vocabulary — DevOps + Cloud sets
  2. 2 Writing — Post-mortem, Runbook
  3. 3 Numbers & Data — SLA uptime
  4. 4 Interview — DevOps questions
SRE / Platform Engineer
  1. 1 Vocabulary — Cloud + DevOps sets
  2. 2 Writing — Post-mortem, Runbook
  3. 3 Speaking — Incident call phrases
  4. 4 Interview — SRE questions
QA Engineer
  1. 1 Vocabulary — QA & Testing set
  2. 2 Writing — Bug report, Acceptance criteria
  3. 3 Reading — Bug report reading
  4. 4 Interview — QA questions
Data Scientist / ML Engineer
  1. 1 Vocabulary — Data Science + AI/ML sets
  2. 2 Writing — Model summary for stakeholders
  3. 3 Reading — Research paper excerpt
  4. 4 Interview — Data Science questions
Security Engineer
  1. 1 Vocabulary — Security set
  2. 2 Writing — Security advisory, Incident report
  3. 3 Reading — CVE description
  4. 4 Interview — Security questions
Solution Architect
  1. 1 Vocabulary — Architecture set
  2. 2 Writing — ADR, RFC
  3. 3 Speaking — Architecture presentation
  4. 4 Numbers & Data — Capacity estimation
Project Manager / Product Owner
  1. 1 Vocabulary — Agile set
  2. 2 Writing — User story, Status report
  3. 3 Email & Communication — Stakeholder escalation
  4. 4 Interview — PM / PO questions
Technical Writer
  1. 1 Grammar — Active voice, Imperative mood
  2. 2 Writing — API docs, README
  3. 3 Reading — Docs types
  4. 4 Vocabulary — All technical sets
Blockchain Developer
  1. 1 Vocabulary — Blockchain & Web3 terms
  2. 2 Writing — Smart contract & DAO docs
  3. 3 Open Source — Community communication
  4. 4 Interview — Blockchain questions
AI / ML Engineer
  1. 1 Vocabulary — AI/ML terminology
  2. 2 AI & Prompt Engineering
  3. 3 Tech-to-Business — Explaining models to stakeholders
  4. 4 Interview — AI/ML Engineer questions
Data Engineer
  1. 1 Vocabulary — Database & pipeline terms
  2. 2 Incident Response — Pipeline failure communication
  3. 3 Tech-to-Business — Data concepts for stakeholders
  4. 4 Interview — Data Engineer questions
Game Developer
  1. 1 Code Review Language — PR comments & feedback
  2. 2 Writing — Release notes & patch docs
  3. 3 Sprint Demo — Presenting game builds
  4. 4 Interview — Game Developer questions
Embedded / IoT Developer
  1. 1 Vocabulary — Hardware & firmware terms
  2. 2 Writing — Technical specs & datasheets
  3. 3 Reading — Hardware documentation
  4. 4 Interview — Embedded/IoT questions
Database Administrator
  1. 1 Vocabulary — Database & SQL terms
  2. 2 Incident Response — DB outage communication
  3. 3 Tech-to-Business — Explaining downtime risk
  4. 4 Interview — DBA questions
Scrum Master
  1. 1 Vocabulary — Agile & Scrum terms
  2. 2 Sprint Demo & Releases language
  3. 3 Remote & Async Communication
  4. 4 Interview — Scrum Master questions
Engineering Manager
  1. 1 Mentoring & Coaching Language
  2. 2 Tech-to-Business — Communicating with leadership
  3. 3 Writing — Performance reviews & job descriptions
  4. 4 Interview — Engineering Manager questions
Business Analyst
  1. 1 Vocabulary — Agile & requirements terms
  2. 2 Tech-to-Business — Bridging business and tech
  3. 3 Writing — User stories & acceptance criteria
  4. 4 Interview — Business Analyst questions
Cloud Architect
  1. 1 Vocabulary — Cloud & DevOps terminology
  2. 2 Writing — Architecture Decision Records (ADR)
  3. 3 Numbers & Data — Capacity & cost estimation
  4. 4 Interview — Cloud Architect questions
Network Engineer
  1. 1 Vocabulary — Networking & infrastructure terms
  2. 2 Incident Response — Network outage communication
  3. 3 Tech-to-Business — Explaining network issues
  4. 4 Interview — Network Engineer questions
Freelance Developer
  1. 1 Email & Communication — Client correspondence
  2. 2 Writing — Proposals, estimates & invoices
  3. 3 Negotiation Language — Scope & rate discussions
  4. 4 Interview — Freelance client questions