What is Developer Relations and What are Common Roles?
Tags: devrel
Published: 2020-05-27 15:14:53

---
title: "What is Developer Relations and What are Common Roles?"
published: true
description: "Developer Relations is a broad area covering product, advocacy, and evangelist. What are the differences?"
tags: devrel
canonical_url: https://www.moesif.com/blog/developer-relations/definition/What-is-Developer-Relations-and-What-are-Common-Roles/
cover_image: https://dev-to-uploads.s3.amazonaws.com/i/pjyu1h5e3xq2r6y7sbvt.png
---

Developer Relations is not simply a role or department at API-first companies. Developer relations is a mindset of getting developers adopt a platform and making them successful with their initiatives rather than attempting to sell to those developers.

This makes developer relations different from traditional sales and marketing roles. However, if you ask "What is Developer Relations?", you may get many ambiguous responses as developer relations is a catch all phrase for a variety of different roles and titles.

Some titles include "Developer Advocate" and Developer Evangelist", but can also include other newer titles like "Developer Experience Manager."These roles vary company to company and even across teams within a company. 

This post outlines some of the different roles within devrel, such as:

- Developer Evangelist
- Developer Advocate
- Developer Experience
- Developer Marketing

## Overview

The art of developer relations is to actually build authentic relationships within your community without selling or marketing to them. This can be done in-person, online, or through other methods. Any communication with developers usually falls under devrel requiring great technical communication skills regardless of role. Some developer relations roles are focused on community engagement and getting the word out. Other devrel roles are focused on product management and developer experience. 

![Runscope test editor](https://blog.moesif.com/images/posts/developer-relations/definition/companies-by-first-api-call.png)

## Developer Evangelist

When engineers hear developer relations, the developer evangelist role (also known as technical ambassador) comes to mind because it's one of the most vocal and outbound focused. 

A developer evangelist is focused on "getting the word" out. This can mean speaking at conferences, attending meetups, and hosting hackathons. Their calendars get filled up quickly with commitments and may be on the road more than in the office. Yet, they also spend a large time online creating code samples, webinars, and hosting virtual office hours.

Evangelists have to be technically minded, but do not have to be engineers themselves. Most of their time is acting as a brand ambassador for the company. 

## Developer Advocate

Unlike a developer evangelist, a developer advocate's goal is not creating buzz and telling the world about your platform. Instead, a developer advocate's role is more of a blend between customer success and product. Their goal is to enable developers to successfully leverage your platform and APIs while advocating for their requirements to internal product teams.

They are effectively a liaison between the greater community and the various internal product teams. They may collect feedback, create demos and code examples, or find solutions to product issues and product bugs. In some companies, they may behave like a "Sales Engineer" or "Solutions Consultant" and are usually more technical than an evangelist.

## Developer Experience

Just like mobile apps require good user experience, good APIs require a good developer experience (DX).

A dedicated developer experience team behaves like the de facto product owner for anything the developer's use.

They may own onboarding flows, SDKs/API design, and documentation. In some companies, the developer relations resides within the product organization and own the entire developer experience. In other companies, devrel may be aligned to marketing, causing developer experience to be owned by another team such as the product teams or a dedicated developer experience team.

## Developer Marketing

It's rare marketing is ever included in under the devrel umbrella, yet devrel does work closely with developer marketing warranting its inclusion. Developer marketing has traditional marketing goals such as marketing Qualified Leads (MQLs) and driving acquisition.

However, marketing to developers is very different from traditional B2B or B2C marketing. Much if it revolves around the principles of "inbound marketing" and creating a brand that pulls people in rather than pushing a brand onto developers. Developer marketing almost always involves a heavy content syndication strategy, but also paid channels like Ad Words, along with event sponsorship. Developer marketing may sponsor a conference that one of their company advocates are speaking at. 

## Closing thoughts

DevRel is an existing and new area to be in. If you're an API first or platform company, having a devrel team can help build relationships with developers without seeming too pushy on the marketing or sales side.

---

Looking for a complete customer-centric API analytics solution? [Check out Moesif!](https://www.moesif.com/?utm_source=devto&utm_medium=blog&utm_campaign=placed-article&utm_term=devrel-common-roles)

---

This article was written by Moesif founder and CEO Derric Gilling for [the Moesif blog](https://www.moesif.com/blog/developer-relations/definition/What-is-Developer-Relations-and-What-are-Common-Roles/?utm_source=devto&utm_medium=blog&utm_campaign=placed-article&utm_term=devrel-common-roles).