DevRel Scribbles
  • What are Scribbles?
  • Index
  • Developer Advocacy
  • Developer Advocates
  • Life as a developer advocate
  • Modernising Red Hat’s enterprise developer program
  • Engaging 9-year-old software developers
  • Making 22-year-olds love 26-year-old software
  • Dogfooding developer products: gathering insights from internal hackathons
  • How far does your ethical responsibility stretch for the tech your devs create?
  • Outside the lecture theatre
  • How do you design programs for diversity?
  • Build the Platform Your Developers Actually Want
  • Measuring dev rel programs far beyond marketing activities
  • Developer Evangelism
    • Developer Evangelists
    • How to rock a technical keynote
    • The Art of Slide Design
    • The Art of Talk Design
    • The Art of Story Design
    • Dev events beyond 2021
  • Developer Experience
    • The Power of Content
    • Building a Developer Community in an Enterprise World
    • How to lose a dev in three ways
    • Developer relations, why is it needed?
    • The hierarchy of developer needs
    • GitHub is your documentation landing page
    • Docs as engineering
    • Commit messages vs. release notes
    • A11y pal(ly)- crafting universally good docs
    • Inspiring and empowering users to become great writers, and why that’s important
    • Solving internal technical documentation at Spotify
  • Community Management
    • Building community flywheels
    • DevRel = Community Management?
    • Creating high-quality communities
    • How to grow a healthy Open-Source community?
    • Managing communities at scale
    • Using community to drive growth
    • Useful community success metrics
    • Communities aren't funnels
    • How to mobilise your community during a pandemic
  • Managing a DevRel Team
    • Developer Relations + Product
    • Distributed developer relations
    • Understanding company goals
    • DevRel Qualified Leads (DQL)
    • Path to success for DevRel
    • How to move up in your organization
    • Four pillars of DevRel
    • Building your DevRel dream team
    • Managing the burnout burn-down
    • I messed up and I’m going to get fired
    • How to report on community relationships without being creepy about it
    • How to scale a developer relations team
  • Misc
    • Is developer relations right for you?
    • Tooling your way to a great DevRel Team
    • Planning your DevRel career
    • Success metrics as narratives
    • Get executive buy-in or else
    • Introduction to the AAARRRP devrel strategy framework
    • Strategy for developer outreach
    • Connecting dev rel and product
    • Performance DevRel
    • Ultimate cheat codes for healthier travel
Powered by GitBook
On this page
  • Summary
  • Scribbles
  • Key roles of DevRel team
  • Evangelist
  • Educator/Facilitator
  • Organizer

Was this helpful?

Export as PDF
  1. Managing a DevRel Team

Building your DevRel dream team

Let's take a look into knowing the key elements required to make a "DevRel dream team".

PreviousFour pillars of DevRelNextManaging the burnout burn-down

Last updated 3 years ago

Was this helpful?

Summary

  • Understanding the key roles of DevRel team

  • What each and every key role does

  • One of them is the facilitator

  • Community managers and organizers are often involved in outreach and community events alongside evangelists, both online and offline.

  • Evangelists are involved in the community events, however, they need to be very familiar with the product being the first point of contact for new developers and businesses.

  • They (evangelists) also are responsible for getting back to the community with answers from the product teams.

  • Developer educators, or facilitators end up working mostly online and behind the scenes for the event, offline interactions and technical workshops are their forte'.

  • Seeing how to structure the DevRel teams as well as knowing how each role fits into core pillars of developer relations is important.

  • Building a team around those ⬆️ helps in setting the right metrics for each team.

Scribbles

Key roles of DevRel team

  • The Evangelist

  • The Facilitator/ Educator

  • The Organiser

  • Those ⬆️ key elements will make sure you have the right mix to pull off great DevRel adventures.

  • If you are starting out as the sole DevRel, then you might need to fill that very spot yourself.

  • Once you are expanding, you will have to find out great people to fill in your weak spots.

Evangelist

  • Person who will stand on the stage and preach to the thousands of developers.

  • Attends various conferences and meetups to share info about the product

  • Collecting feedbacks

  • Showing off the killer presentation with a pinch of memes

Educator/Facilitator

  • Provides the support/acts as a backbone for developers

    • Documentation

    • Quick start guides

  • Running technical training events

  • Speaking at workshops

  • Helps in making complex topics digestible

Organizer

  • Community folks who bring developers together

  • Fuel to the community

  • Helps in maintaining peace and prosperity in the community

  • Making sure any issues raised are sorted out ASAP

  • Having the right mix of people always helps brings a balance to the team

  • Leads to kinds of activities that the developer relations often participates in

    • Outreach

    • Community

    • Product

    • Education and Support

The real key to building a great team is finding people who understand one another. It might go too far to say that this is the golden ratio of building the ultimate dev rel team but it’s a place to start.

Building a dream dev rel teamDeveloperRelations.com
Blog
Logo