Vocabulary for Developer Advocates
DevRel vocabulary explained: developer evangelism, developer experience, community engagement, feedback loop, developer journey — with usage examples for DevRel professionals.
Developer Relations (DevRel) is a field that sits at the intersection of engineering, marketing, and community building. Developer advocates — also called developer evangelists or developer experience engineers — represent companies to developer communities and represent developer communities to companies.
For non-native English speakers entering or working in DevRel, the vocabulary can be surprising: it blends technical terms, marketing language, and community-building concepts. This guide explains the key terms with definitions and usage examples.
The Core Role Vocabulary
Developer Advocacy
Developer advocacy is the practice of promoting a technology platform, API, or tool to developers — through talks, tutorials, blog posts, and community engagement. Advocates are credible because they are themselves technical.
“The developer advocacy team runs workshops, speaks at conferences, and creates sample code to help developers adopt our platform.”
Developer Evangelist
Developer evangelist is an older term for a similar role — an engineer who champions a technology externally, spreading adoption through enthusiasm and education.
“She joined as a developer evangelist and spent her first year at every major conference explaining the platform’s capabilities.”
Note: “Evangelist” has religious connotations (from the word for spreading a gospel). In tech it is widely used, but some companies now prefer “advocate” as a more neutral term.
Developer Relations (DevRel)
DevRel is the broader function that includes advocacy, community management, developer experience, and technical writing. It can also refer to the team or department.
“The DevRel team manages our GitHub community, runs the annual developer conference, and maintains the official SDKs.”
Developer Experience (DX)
Developer Experience
Developer experience (DX or DevEx) is the overall quality of the experience a developer has when building with a product — including documentation, SDKs, APIs, error messages, sample code, and support.
“Our NPS surveys show that developers find the API intuitive, but onboarding is painful — improving DX there is our top priority.”
Developer Journey
The developer journey maps the stages a developer goes through when discovering, evaluating, adopting, and advocating for a technology.
“We map our content strategy to the developer journey: awareness content for discovery, tutorials for evaluation, reference docs for adoption, and case studies for retention.”
Time to Hello World
Time to Hello World (TTHW) is the time it takes a new developer to get a working example running with your product — a key metric for developer experience.
“Our goal is a time to Hello World under ten minutes. Right now it’s 35 minutes, which is too high.”
Community Concepts
Community Engagement
Community engagement is the practice of actively participating in, nurturing, and growing a developer community — through forums, Discord servers, meetups, conferences, and social media.
“Our community engagement strategy focuses on responding to every GitHub issue within 48 hours and maintaining an active presence in the Discord server.”
Champion / Ambassador
A champion or developer ambassador is a highly engaged community member who promotes the technology voluntarily — often in exchange for recognition, early access, or financial support.
“We have 40 developer ambassadors globally who run local meetups and create content about our platform. They are invaluable for community growth.”
Ecosystem
The ecosystem refers to the broader network of tools, libraries, partners, and communities built around a technology platform.
“We measure ecosystem health by the number of third-party integrations, community-maintained libraries, and active Stack Overflow questions.”
Feedback and Metrics
Feedback Loop
A feedback loop in DevRel is the process by which feedback from the developer community is collected, communicated internally, and acted upon by the product team.
“One of the most valuable things a developer advocate does is maintain a tight feedback loop between external developers and the internal product and engineering teams.”
“The feedback loop broke down when we stopped attending community forums. Developers were raising bugs that we didn’t hear about for months.”
Funnel
The developer funnel maps how developers move from awareness to active usage of a product.
“We track the developer funnel: impressions at the top, sign-ups, first API call, first successful integration, and monthly active developers at the bottom.”
North Star Metric
A north star metric is the single most important metric that captures the core value the product delivers.
“Our north star metric is ‘weekly active developers’ — we believe that weekly usage is the best indicator of true adoption and value.”
Content and Communication Vocabulary
Technical Tutorial
A technical tutorial walks a developer step by step through building something specific. It is outcome-focused: by the end, the reader has accomplished a concrete goal.
“The tutorial teaches developers how to build a real-time notification system using our WebSocket API, from setup to deployment.”
Sample Code / Code Snippet
Sample code is working example code that developers can use as a starting point or reference. Snippets are shorter, illustrative code fragments.
“We maintain a GitHub repository with fully working sample applications for each major use case.”
SDK (Software Development Kit)
An SDK is a collection of tools, libraries, and documentation that helps developers build on a platform.
“We ship first-party SDKs for JavaScript, Python, Go, and Java. Community-maintained SDKs exist for Ruby and PHP.”
Useful Phrases for DevRel Professionals
Explaining DevRel’s Value Internally
“DevRel is how we scale our relationship with the developer community beyond what our sales and support teams can cover.”
“A developer advocate can reach thousands of developers through a conference talk or a widely shared blog post. The same content continues to work for months or years.”
Talking About Community Health
“Community health metrics include response time, active contributors, open issue age, and developer satisfaction scores.”
“We’re seeing strong organic growth — developers are discovering us through community word-of-mouth rather than paid channels.”
Giving Feedback to the Product Team
“Based on what I’m hearing from the community, the authentication documentation is the biggest friction point. Three separate developers at the conference mentioned getting stuck on the same step.”
“Developers are asking for a Python SDK — this is the third most-requested feature in our community forum. I’d like to propose we build it in Q3.”
Developer advocacy is a role where language and technical credibility combine. The best developer advocates communicate authentically with developers, represent that community’s needs clearly internally, and create content that genuinely helps people succeed. This vocabulary is your foundation for doing all three.