DevRel Glossary

The moment a new developer first gets real value from your product, such as a successful API call or a working integration. It is defined per product, and it is usually a better signal than sign-ups.

Why developers sign up but never call your API

The share of developers who sign up and then reach your defined activation event within a set window. Pick one event and one window and keep them fixed, so the trend means something.

Developer experience that also works for an AI agent acting without a human interpreting it. That means clear docs and specs, machine-readable entry points, a safe way to try the product, and errors that say what to do next.

Agent-Ready DX Teardown

The complete, exact description of every endpoint, parameter, response, and error. It answers what a call does, while guides and tutorials answer how to get a task done.

Connecting a developer's sign-up or usage back to the content, event, or community touchpoint that influenced it. Developers often arrive by word of mouth, so attribution is partial, and teams usually pair tracked sources with a simple "how did you hear about us" question.

Selling a product that developers evaluate, adopt, or influence the purchase of. It differs from conventional B2B because developers trust docs, peers, and hands-on trial more than advertising or sales outreach.

Developer GTM consulting

A structured program that recognizes and supports your most helpful community members and customers so they teach, answer questions, and speak about your product. Typical benefits are early access, direct lines to the team, and public credit.

How to build a developer community

A dated, public record of what changed in your product, API, or SDKs. A good one flags breaking changes clearly and links to the docs for each change.

How well a community is functioning, judged by signals such as how fast questions get answered, how many answers come from members rather than staff, and how many people return. Raw member counts say little on their own.

The person who runs your developer community spaces, such as Discord, forums, or GitHub Discussions. They set the rules, welcome newcomers, moderate, run programs and events, and report what members are asking for.

Developer community building

A growth approach where an engaged community drives awareness, support, and adoption, so new developers arrive through peers rather than ads. It takes steady investment and a person inside the company who owns it.

How to build a developer community

A DevRel role that represents developers to the company and the company to developers. Advocates create content, give talks, build demos, support the community, and carry feedback back to product and engineering.

DevRel vs developer advocacy

An older title for a role focused on promoting a platform to developers, often through talks and events. Many companies now use developer advocate instead to stress two-way communication, including taking developer feedback back to the product team.

The overall experience a developer has when finding, learning, and using your product, from the first search to production. It covers docs, APIs, SDKs, tooling, onboarding, error messages, and support.

Developer experience services

The stages developers pass through, usually awareness, evaluation, sign-up, activation, and ongoing use. It is a simplification, since developers move back and forth, but it shows where the drop-offs are.

Developer journey audit checklist

The path a developer takes from first hearing about your product to using it in production and recommending it. Mapping it shows which step loses people, whether that is finding the docs, getting credentials, or making a first request.

Developer journey audit checklist

A marketer who works on positioning, content, and campaigns aimed at developers. The job is to be specific and technically honest, since developers quickly dismiss vague claims.

Developer content creation

A Net Promoter Score survey sent to developers, asking how likely they are to recommend your product or platform. Pair the score with a free-text question, since the comments explain what to fix.

Everything that takes a new developer from sign-up to a first working result: account setup, credentials, quickstart, and first request. It is where many developer products lose people.

Docs to first value diagnostic

A single site where developers find docs, API reference, keys, usage data, and support. It is the home base for your developer experience.

The share of activated developers who are still using the product after a set period, such as 30 or 90 days. It shows whether first value led to a habit or a one-off trial.

A go-to-market approach where developers adopt a product first, often on their own, and that bottom-up usage later turns into team or company purchases. DevRel, docs, and a free or low-friction entry point usually carry most of the load.

Developer GTM consulting

The work of helping developers discover, understand, adopt, and succeed with a technical product. It combines documentation, education, community, and product feedback.

What is DevRel

An engineer on the DevRel team who builds the technical assets developers rely on, such as sample apps, SDK examples, integrations, and demos. The title is used loosely, so check whether a role is mostly engineering or mostly public-facing.

A developer or account that DevRel work has surfaced and that shows real buying or adoption intent, such as a team using the API heavily or asking about production limits. Sales and DevRel should agree on the criteria before anyone counts them.

The return on DevRel spend, measured by tying DevRel activity to adoption and revenue outcomes. It is rarely a single number, so most teams track a small set of leading and lagging metrics and report them against agreed goals.

How to measure DevRel ROI

Treating documentation like software: plain-text source in version control, reviewed through pull requests, and built and published by an automated pipeline. It lets engineers fix docs in the same workflow as code and keeps docs in step with releases.

Using your own product the way your customers do, for example building a sample app with your own API. It surfaces the rough edges that docs and tests miss.

A structured review of the developer experience that shows where developers get stuck and what to fix first. It usually walks the real path from discovery through sign-up to a first successful use.

Developer Adoption Audit

The network of developers, partners, integrations, tools, and content that grows around a product and makes it more useful. A developer ecosystem compounds when third parties build on your platform and each other's work.

How to Build Developer Ecosystems

The route by which developer problems and requests reach the product and engineering teams and come back as visible changes. A loop that never closes teaches developers to stop reporting issues.

A time-boxed event where developers build projects with your product, in person or online. It gets people hands-on and produces real feedback on the developer experience, but the value comes from the follow-up with participants.

The smallest working example that proves a developer's setup works, such as sending one request and getting a valid response. How quickly a newcomer reaches it is a core onboarding measure, covered under time to first call.

Time to first call

A proposed convention for a Markdown file at the root of a site that gives large language models a curated, link-first guide to the site's most useful content. Some documentation and developer sites publish one to make their content easier for AI tools to read.

Agent-Ready DX Teardown

An open protocol, introduced by Anthropic, that lets AI applications connect to external tools and data sources in a standard way. A product with an MCP server lets an AI agent call its capabilities directly.

Agent-Ready DX Teardown

The number of distinct developers who make meaningful use of your API or product in a month. Define what counts as active, for example at least one successful call, or the number will drift.

A recognition program for the most valuable community contributors, short for Most Valuable Professional. Microsoft's MVP program is the best-known example, and many companies run their own versions.

How to build a developer community

A recurring, scheduled session where developers can ask your team questions live. It builds trust and gives the team a steady stream of real questions to learn from.

The contributors, maintainers, and users around an open source project. For a commercial company, it is both a distribution channel and a group that needs honest, consistent maintenance.

A standard, machine-readable format for describing HTTP APIs. One spec can generate reference docs, SDKs, and test tooling, and it gives AI tools an exact description of what the API does.

A growth model where the product itself drives acquisition, conversion, and expansion, usually through free or self-serve access. Developer-led growth is the version of it where developers are the first users.

A short guide that takes a new developer to one working result in the fewest steps, usually in a few minutes. It should assume nothing beyond an account and link out for the details.

Docs to first value diagnostic

A cap on how many requests a developer can make in a given period. Clear limits, headers that report them, and errors that explain what to do next make for a better developer experience.

A small, working application that shows your product in a realistic use, with code a developer can run and copy. It teaches more than a snippet because it shows how the pieces fit together.

A safe environment, often with test data or test mode, where developers can try your API without real consequences such as charges or production changes. It lets people explore before they commit.

A package of libraries, tools, and examples that makes it easier to use a product from a specific programming language. A good SDK handles authentication and common errors so developers write less boilerplate.

Letting a developer sign up, try, and start using a product without talking to anyone. It depends on clear docs and pricing, and it is the basis of developer-led growth.

A writer who produces and maintains documentation such as guides, API references, and tutorials. The best ones work closely with engineers and test the instructions by following them.

How long it takes a new developer to go from sign-up to a first successful API call, also called time to hello world. A shorter time usually means the quickstart, credentials, and auth steps are working.

Docs to first value diagnostic

A step-by-step lesson that teaches a concept by building something concrete. It differs from a quickstart, which is shorter, and from a how-to guide, which assumes the reader already knows the basics.

A way for a service to send an HTTP request to your app when an event happens, so you do not have to keep polling. Good webhook docs cover the payload, retries, and how to verify the sender.