Mission

Build a thriving and connected developer community around the product. The person is at the interface between the product and the people who use it. We could summarize the mission like this: To help developers be better at their jobs when using the product.

Responsibilities

• Product
  • Give feedback to product management, to influence the product roadmaps based on developers' needs
  • Follow GitHub issues to understand where developers face frustration and develop strategies to overcome these. This could be suggesting or implementing documentation updates, or proposing or contributing code changes that solve the core issue.
• Docs
  • Seek out and implement improvements to the documentation
  • (engineering) Contribute to the docs infrastructure and the docs website experience
• Content
  • Create educational materials (tutorials, how-to guides, demo apps) for devs of all skill levels.
  • Write code where required to support how-to content, blog posts, and presentations.
• Community
  • Nurture ongoing connections with user group members to build personal relationships and deeply understand their needs, usage, journeys, and barriers to adoption
  • Serve as the "voice" of the company through social media, conferences, meetups, and other ecosystem events
  • Create & produce events (podcasts, roundtables, hackathons)
  • Manage the sponsorships of events, newsletters, etc
  • Help other team members grow at engaging with the community. For instance by encouraging and providing critical feedback on the blog posts they create, or by keeping track of the health of community contributions
  • Create relationships with fellow ecosystem influencers and open-source leaders
• Be the voice of the MUI developer community inside the team.
• Be the voice of the MUI outside, to the community.

Performance indicators

• Improve the DevEx KPIs
  • Lagging: Improve NPS during the annual developer survey
    • Improve the developer experience. It's close to a product and engineering role. The objective is to build, nurture, and sustain a happy, engaged, loyal developer community. Possible activities are around improving the documentation, creating tutorials, and making sure the feedback on the top Stack Overflow questions is "leveraged" by the product. Adding a rating widget on the docs, and creating a dashboard to share the results with the team. Creating video courses.
  • Lagging: Improve the adoption rate of the library in the market. It also comes with increasing the number of monthly active developers on the documentation.
• Leading indicators: ?

Benchmarks

• https://www.swyx.io/measuring-devrel
• Measuring developer relations: Rey Bango https://www.youtube.com/watch?v=NRTUA0cSMnQ&t=1756s

Benchmark (initiatives)

• Vercel, Lee Robinson https://twitter.com/leeerob/status/1608900031859527682

  My 2022 by the numbers:

  • 2,280 tweets • 2,835 commits / 433 PRs merged • 12 podcasts • 10 YouTube videos • 9 live streams • 5 conference talks

• https://www.swyx.io/measuring-devrel

Levels

Engineering levels