Building a DevRel Team

While I was reading, the writer used a mall as an example saying, “Draw your mall map”

This map will help identify where you’re as a company, where you’d like to be, and what you might encounter along the way.

This led to, while building the DevRel team there are some things you need to spell out:

1. What’s in the name? Developer Advocates, Developer Evangelist, Developer Relation Managers, etc.

This helps you identify who they are and what they bring to the table in the team.

2. Team Title: Developer Relations. The team title can be as stated above because there are many roles involved in the team, so a name that covers everyone is needed.

3. Strategic Lead: Developer Relation Manager Someone who oversees the affairs of the team, understands what works, whom to relate to who, and addresses a need as it arises. (NB: it’s broader than I explained)

4. Technical Contributor: Developer Advocate

5. Full-time Engineer: in the DevRel team, a dedicated developer is needed for the team, he helps fixes bug that the engineering team are not prioritizing but

is needed for the community, and maybe a program is needed to be developed for an event, etc.

Other roles are also needed in the DevRel team as you try to build one for your company.

Now that you know what you need and it’s time to hire, how do you then do it? First, look within your company (maybe there’s a fit), look to your community, or look outside the community. Once someone is gotten, look for a common characteristic between the role and the individual.

Find someone who is self-driven, flexible, has good communication skills, has a full understanding of the role, and has the willingness and desire to learn. With the aforementioned, you’re setting yourself up to build a great DevRel Team for your company.