Mission

1. Ensure that the tools, components, and documentation MUI provides are of the highest possible quality, making it as easy as possible for developers to simply deploy amazing UIs.

   Supporting Provide operations bandwidth for Product Managers.

2. From 1. help spread the product everywhere.

   Supporting Provide GTM bandwidth to Product Managers for the open-source/IC audience.

Responsibilities

Sorted by priorities:

• Product
  • Live with the community: contribute to better tuning the product to the users based on their feedback. Be a voice of the MUI developer community inside the team.
  • Live in the shoes of users: raise the quality bar of the product by providing critical feedback on product changes.
  • Dogfooding the product.
  • Give feedback to product management to improve the product roadmaps based on developers' needs.
  • Live in 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.
  • (if needed) Contribute to the docs infrastructure and the docs website experience.
• Content
  • Write code where required to support how-to content, blog posts, and presentations.
  • Create materials (tutorials, how-to guides, demo apps) to help AI agents and devs of all skill levels.
  • Educate users on the product.
• Community
  • Create relationships with fellow ecosystem influencers and open-source leaders.
  • Serve as a "voice" of the company through social media, conferences, meetups, and other ecosystem events.
  • 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 & produce events (podcasts, roundtables, hackathons).
  • Manage the sponsorships of events, newsletters, etc.

Key performance indicator

• Improve the KPIs - DevEx
• 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 to 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: ?

Why this role exists

Benchmarks

• 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

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