Developer Advocate / DevRel
Developer advocates live between engineering and marketing, translating complex technical concepts into compelling content, talks, and tutorials for developer audiences. Success requires precise vocabulary for describing APIs and developer experiences, strong written English for blog posts and documentation, and persuasive spoken English for conference talks and community calls. This path builds all three, with a focus on authentic technical communication.
Topics covered
- technical content creation
- conference talks
- CFP writing
- developer community management
- API developer experience
Vocabulary spotlight
4 terms every Developer Advocate / DevRel should know in English:
Developer Relations — a function responsible for building relationships between a company and the external developer community
"The DevRel team acts as a two-way bridge: they bring developer feedback into the product and take the product out to developers."
Call for Proposals (or Call for Papers) — an invitation from a conference for speakers to submit talk ideas
"I submitted three talk abstracts to the CFP before one was accepted."
The sequence of steps a developer takes from first discovering a product to becoming a power user
"We mapped the developer journey and found most drop-off happened during the first API call."
Active promotion of a technology or platform to build awareness and adoption within a developer community
"His evangelism at regional meetups helped grow our community by 40% in one year."
Net Promoter Score measured specifically among developers; a metric for how likely developers are to recommend a platform
"Our developer NPS dropped after the API breaking change, so we prioritised the migration guide."
A structured progression of content (awareness → consideration → activation) that guides developers from discovery to using a product
"The blog post sits at the top of the content funnel; the quickstart guide is where developers activate."
📚 Vocabulary Reference
Key terms organised by category for Developer Advocate / DevRels:
Content
Community
Metrics
DevRel Strategy
Recommended exercises
Real-world scenarios you'll practise
- Writing a conference talk abstract that makes the programme committee want to accept it immediately.
- Creating an API quickstart guide that gets a developer to their first successful call in under five minutes.
- Presenting a live coding demo at a meetup where the code breaks and you need to recover gracefully.
- Writing an engineering blog post that is genuinely useful to developers, not a thinly veiled product pitch.
Recommended reading
Frequently Asked Questions
What English skills do Developer Advocate / DevRels most need to improve?+
Developer Advocate / DevRels most commonly need to improve: technical vocabulary (the correct English terms for domain concepts), collocation accuracy (using the right verb for each action), written communication (bug reports, PR descriptions, technical docs), and spoken communication for standups, code reviews, and stakeholder meetings.
How long does the Developer Advocate / DevRel learning path take?+
The Developer Advocate / DevRel learning path contains 20–40 hours of material studied comprehensively. 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 workplace English.
What vocabulary should a Developer Advocate / DevRel prioritise first?+
Start with the vocabulary that appears most in your daily work — terms you read in documentation, use in commit messages, and hear in meetings. The Developer Advocate / DevRel path begins with the most frequent vocabulary clusters before moving to advanced communication patterns.
Are there interview exercises for Developer Advocate / DevRel roles?+
Yes. The Developer Advocate / DevRel path includes role-specific interview question modules with model answers and key phrases — the actual questions interviewers ask and the vocabulary needed to answer them fluently. There is also a dedicated Interview Practice hub for general interview skills.
Does this path include pronunciation help?+
Yes. The path links to pronunciation exercises for the technical terms most commonly mispronounced in this domain. The Pronunciation hub includes drills for acronyms, silent letters, word stress, and minimal pairs — all in IT context.
What are the most common English mistakes Developer Advocate / DevRels make?+
The most common mistakes: incorrect collocations (using the wrong verb with a technical noun), false friends from L1, tense errors when narrating past incidents or walkthroughs, and using overly formal or overly casual register in written communication.
How do I improve my English for code reviews?+
Learn the standard code review collocations: approve a PR, request changes, leave a nit, address feedback, block a merge, resolve a conversation. Use hedging language for suggestions: "This might be cleaner as…", "Have you considered…?". The Collocations section includes a dedicated Code Review set.
Can I use this path alongside my daily work?+
Yes — the path is designed for working professionals. Each exercise set takes 10–15 minutes. The most effective approach is to study a vocabulary module before a meeting or task where you'll use that vocabulary, then practise immediately after. Context-linked practice produces much faster retention.
Is the content free?+
Yes, completely free. No registration required, no payment, no time limit. All vocabulary modules, exercises, glossary entries, and learning path guides are open access.
How do I track my progress through this path?+
Progress is tracked in your browser's local storage — completed exercise sets are marked with a checkmark when you return. No account is needed. You can bookmark specific modules and use the exercises overview to see which sets you've completed.