Where DevRel Came From and Why It Matters

Arjun, Rainkit's product manager, is planning next year's budget. "Why pay for a developer advocate?" he asks. "We could buy ads instead." To answer him, Meera needs two things: a sense of where her job came from, and a clear reason it still exists.

The rule

Developers pick tools by trying them, so DevRel earns trust, not attention.

The job grew in three rough eras, and each one added a new verb.

1. Evangelism: persuade. In the 1980s and 1990s, a new computer or operating system was only worth buying if good software ran on it. Platform companies such as Apple and Microsoft hired people called evangelists to convince software makers to build for their platform. The work was mostly persuasion: demos, visits, conference stages.
2. Advocacy: represent. Web APIs and open source changed who made the decision. A developer could sign up for a service or install a free library and ship it before any manager had heard of it. Companies that sold to developers began hiring advocates who wrote code, answered questions in public, and spoke for developers inside the company.
3. Developer experience: improve. Today many DevRel teams also care about the whole path a developer takes: docs, onboarding, SDKs, error messages, community. The question grew from "have they heard of us?" to "was it quick and pleasant to succeed?"

Why does this matter for a product like Rainkit?

• Bottom-up adoption. Developers often choose the tools and their managers approve later. One developer's good first hour with Rainkit can bring it into a company of hundreds.
• Scepticism. Developers tend to ignore ads and trust peers, working code and people who admit limits.
• Platform value. An API is worth what developers build with it. Every app that warns "rain likely at 4 pm" is both proof and promotion.
• Early warning. An advocate hears about problems in public channels long before they show up as cancelled accounts.

The shortcut

To place any DevRel activity, name its verb: persuade, represent or improve. Modern DevRel still does all three. The later verbs were added to the job, not swapped in, and they are what make the persuading believable.

The trap is thinking DevRel is old-style evangelism with a new name. Pure persuasion rarely works on developers. It is the representing and the improving that earn their trust.

Drills

Answer fast — trust the rule.

Remember

• Developers pick tools by trying them, so DevRel earns trust, not attention.
• Shortcut: persuade, represent, improve. Modern DevRel does all three.
• Trap: treating DevRel as advertising with a friendly face. Developers trust proof and people.