Esc
↑↓ navigate   Enter open   Esc close

Choose Your IT Role

108 curated learning paths — each focused on the vocabulary, exercises, and scenarios specific to your job. A DevOps engineer and a PM have very different daily English needs.

Prefer to practice by skill type? Browse all exercises →

Not sure which path fits you?

Take the 5-question role quiz and get a personalised recommendation in under 2 minutes.

Take the role quiz →

Role Comparison — Skills & First Steps

Not sure what to focus on? This table maps the core IT roles to their most critical English skills and the best exercises to start with.

Role Key language skills Start here Est. path time
🖥️ Frontend Reading docs, writing PR descriptions, code review phrasing Vocabulary → Frontend · Writing → PR descriptions ~4 h
⚙️ Backend API docs, system design language, async written communication Vocabulary → Backend · Writing → API docs ~5 h
☁️ DevOps Runbooks, post-mortems, deployment announcements, incident calls Writing → Post-mortem · Speaking → Incident call ~5 h
🛡️ SRE Incident communication, SLO/SLA writing, status updates Writing → Runbook · Numbers → SLA uptime ~4 h
🔍 QA Bug reports, test plans, acceptance criteria, no-go decisions Writing → Bug report · Reading → Bug report ~4 h
📱 Mobile Release notes, App Store language, crash report reading Writing → Release notes · Reading → Crash report ~3 h
🤖 Data / ML Research summaries, model explanations, data storytelling Vocabulary → Data Science · Writing → Model summary ~5 h
🔒 Security CVE advisories, incident reports, compliance documentation Writing → Security advisory · Reading → CVE ~4 h
🏛️ Architect ADRs, RFCs, trade-off presentations, design review facilitation Writing → ADR · Speaking → Architecture presentation ~5 h
📋 PM / PO Status reports, user stories, stakeholder escalation, meetings Writing → Status report · Email → Stakeholder update ~4 h
🔄 Full-Stack End-to-end system language, API contracts, cross-team communication Vocabulary → Frontend + Backend · Writing → PR + API docs ~6 h
📄 Tech Writer Doc structure, plain language, API reference, changelog conventions Grammar → Active voice · Writing → API docs ~5 h
⛓️ Blockchain Dev Smart contract docs, audit reports, DAO proposals, whitepaper English Vocabulary → Blockchain · Tech-to-Business ~4 h
🧠 AI / ML Engineer Model cards, RAG architecture language, responsible AI communication AI Prompting · Writing → Model card ~5 h
🏗️ Data Engineer Pipeline design docs, data contracts, schema documentation Vocabulary → Database · Writing → Data contract ~4 h
🎮 Game Developer GDD writing, patch notes, bug reports, GDC-style presentations Writing → Patch notes · Presentations ~3 h
🔌 Embedded / IoT Firmware docs, datasheet reading, hardware constraint communication Reading → Datasheet · Writing → Firmware changelog ~4 h
🗄️ DBA Incident communication, query optimisation reports, recovery runbooks Incident Response · Writing → Runbook ~4 h
🏉 Scrum Master Ceremony facilitation, sprint goal writing, agile metrics communication Meetings → Retro facilitation · Sprint Demo ~4 h
👔 Eng. Manager Performance reviews, hiring docs, strategy presentations, 1:1 coaching Mentoring · Presentations → All-hands ~5 h
📋 Business Analyst User stories, requirements docs, workshop facilitation, gap analysis Writing → User stories · Meetings → Workshop ~4 h
☁️ Cloud Architect Cloud ADRs, FinOps presentations, cost estimation language Writing → ADR · Tech-to-Business → FinOps ~5 h
🌐 Network Engineer Change requests, outage communication, network design documentation Incident Response · Writing → Change request ~4 h
💼 Freelance Dev Client proposals, scope negotiation, invoice language, status updates Email → Client communication · Negotiation ~3 h

All exercises are cross-listed — a Backend developer can and should do Grammar and Speaking exercises too. The paths above are starting recommendations, not restrictions. Browse the full list of 79 paths above to find your exact role.

Browse all exercises by category

Prefer to explore by exercise type rather than role? Vocabulary, Writing, Grammar, Reading, Listening, Speaking, Interview Prep, and more — all organised by skill.

Browse all exercises →

Frequently Asked Questions

What is a role-based learning path?+

A role-based learning path is a curated sequence of vocabulary sets, exercises, and reading materials tailored to the English needs of a specific IT job. A Frontend Developer path focuses on browser APIs and accessibility; a DevOps path covers infrastructure and incident response vocabulary. Instead of generic English, you learn what you'll actually use at work.

How many learning paths are available?+

There are 108 role-based learning paths covering every major IT specialism: Frontend, Backend, Full-Stack, Mobile, DevOps, SRE, QA, Data Engineering, Data Science, Security, Cloud Architecture, AI/ML, Blockchain, LLMOps, Platform Engineering, and many more. Each path includes vocabulary modules, exercises, and key phrase guides.

Which learning path should I start with?+

Start with the path that matches your current job title or the role you're targeting. If you're a backend developer, start with the Backend Developer path. If you're transitioning into DevOps, start the DevOps Engineer path. If unsure, the Full-Stack Developer path covers the broadest range of daily vocabulary.

How long does a learning path take?+

Each path contains 20–40 hours of material if studied comprehensively. However, most learners focus on the highest-priority modules first and return to the rest over time. Spending 30 minutes per day for 4–6 weeks produces noticeable improvement in meetings, code reviews, and written communication.

Can I use multiple learning paths?+

Yes. Many professionals have hybrid roles — a Backend Developer who does DevOps, or a Data Scientist who also manages projects. You can follow multiple paths simultaneously. The recommended approach is to complete 70–80% of your primary role path before adding a secondary one.

Are the learning paths suitable for senior engineers?+

Yes. Senior engineers often have strong technical vocabulary but struggle with communication patterns: writing RFCs, running retrospectives, presenting to stakeholders, or negotiating salary in English. The paths include advanced communication modules specifically for senior-level scenarios.

Do the learning paths include interview preparation?+

Every role path includes role-specific interview question modules with model answers and key phrases. The Security Engineer path includes OWASP Top 10 explanation exercises; the SRE path includes SLO/error budget discussion scenarios. There's also a dedicated Interview Practice hub covering general interview skills.

What is the difference between Topics and Exercises?+

Topics are learning path hubs — they organise vocabulary, reading, and activities by role and theme. Exercises are individual interactive drills. Topics tell you what to study; Exercises give you the practice. Both are linked from within each learning path.

Are there learning paths for non-engineering roles?+

Yes. There are paths for: Technical Writer, Project Manager / Product Owner, Business Analyst, UX Designer, DevRel Engineer, Solutions Architect, and more. These focus on communication vocabulary for documentation writing, stakeholder presentations, and requirements gathering.

How often are the learning paths updated?+

Learning paths are updated when new technologies become mainstream in the industry. New vocabulary modules are added as emerging roles (LLMOps, Platform Engineering) establish their own terminology. Subscribe to the CoderSlingo blog to be notified of major additions.