Developer relations is the discipline that builds trust and lasting working relationships between a company and the developers who use, integrate or recommend its product. It combines advocacy, education, community and product feedback, and its credibility rests on being useful before being promotional. For B2B companies with an API, an SDK or a platform, technical webinars run by developer relations are a core part of that work.
TL;DR
- Developer relations earns developers' trust through advocacy, education, community and honest product feedback.
- Good teams measure activation, community health and the product changes they influenced, not follower counts.
- Technical webinars work when they show real code, put engineers on the panel and leave room for hard questions.
- Developers notice a sales pitch dressed as a workshop, and they rarely come back after one.
Advocacy, education, community and the feedback loop
Most developer relations teams combine four strands of work. Advocacy means engineers who write, speak and build in public, showing how to solve real problems with the product. Education covers tutorials, sample code, workshops and much of the documentation experience. Community looks after forums, meetups and community engagement sessions where developers help each other. Developer experience feedback carries what developers struggle with back to product and engineering.
The feedback strand is what separates developer relations from developer marketing. A developer advocate who hears the same authentication complaint at every workshop has a duty to get it fixed, not just to explain it better.
Reporting into marketing, product or engineering
Developer relations reports into marketing in some companies and into product or engineering in others. The reporting line shapes the measures. A team under marketing is often asked for sign-ups and pipeline, while a team under engineering is asked about adoption and developer experience.
The roles are similar either way. Developer advocates create content and speak, community managers run forums and events, and developer educators own tutorials and workshops. A DevRel lead sets priorities and keeps the team credible with developers and the business alike, which sometimes means refusing a request to turn a workshop into a lead list.
Activation and influence instead of follower counts
Developer relations is easy to measure badly, because views, followers and registrations can rise without anyone building anything. Stronger measures follow developers into the product.
- Activation, such as how many developers make a first successful API call or deploy a sample project.
- Time to first success, from sign-up to a working integration.
- Community health, meaning returning contributors and questions answered by people outside the company.
- Product changes influenced by developer feedback the team gathered and argued for.
- Influenced revenue for commercial products, counted by a rule agreed with sales and treated with care.
Many of these need data from the product, not from the webinar or the forum. A team that reports only what its own tools count will struggle to show its value.
Technical webinars developers stay for
A short session on one change, migration or deprecation, with the exact steps developers need to take.
An engineer builds something real on screen, explains each decision and takes questions as they come.
A longer session on architecture, implementation or troubleshooting, often with two or three engineers on the panel.
An open session where developers bring their own problems, which doubles as product research.
Three things make these sessions work. The code is real and runs. The person answering questions built or maintains the feature. Resources such as the sample repository and the relevant documentation are shared during the session rather than promised afterwards. Recordings matter more than in most fields, because developers search for the exact explanation weeks later.
Our companion piece explains why cRUD Webinar is better for developer relations teams.
Scoping a technical session before it is announced
- Level. State whether the session is for newcomers or experienced users, and stick to it.
- Live or prepared code. Decide which parts are coded live and which use prepared branches, so a failed build does not consume the session.
- Who answers. Put an engineer who knows the feature on the panel, with a moderator to sort questions.
- Access and identity. Many developers register with personal addresses, so a business-email rule can exclude the people you most want.
- Follow-up. Agree in advance whether anyone from sales will contact attendees, and say so on the registration page.
An SDK migration workshop and twenty-three token questions
The figures are illustrative. A developer advocate at a mapping API provider needs developers to move from the old SDK to the new one before support for the old version ends. She runs a 90-minute live workshop with an SDK engineer, using open registration with no business-email rule because many of the developers use personal addresses.
A poll at the start shows that most attendees are still on the old SDK. During the migration walkthrough, 23 questions ask about a change in how authentication tokens are refreshed, more than any other topic. The engineer answers the first few live and the moderator collects the rest.
Afterwards, the developer advocate and the SDK engineering lead review the questions together. The engineering lead decides to add a token refresh section to the migration guide and a clearer error message in the new SDK. The advocate schedules a 30-minute follow-up on authentication alone, and nobody in the audience is passed to sales.
How a technical session loses its developers
A product pitch dressed as a workshop
Developers who registered to learn and were then sold to will not register again. Keep the pitch out, or label the session honestly.
Code that only works on the presenter's laptop
A demo that skips setup or relies on hidden configuration teaches the audience nothing. Show the real steps, including the awkward ones.
Questions left hanging
Unanswered technical questions read as evasion. Answer them afterwards in the documentation, the forum or a follow-up, and tell the people who asked.
Harvesting registrations
Treating a workshop as a lead list damages the trust developer relations exists to build. If sales follow-up happens at all, it should be something developers opt into.
Summary
Developer relations webinars are strongest when technical usefulness comes before lead capture. Developers need accurate demonstrations, honest limits, accessible examples and a route to continue learning. Questions and code-related evidence should remain connected to the session, while commercial follow-up should respect the purpose of the event and the participant choices made at registration.