A developer advocacy program educates and empowers developers to become advocates for your product—through content, community, events, and peer influence. When done well, it builds relationships and drives adoption. This post outlines best practices and draws on case studies from GitHub, Google, and Microsoft so you can design a program that fits your goals and resources.
1. Define your goals
Clearly define goals for the program so you can measure success and align effort. Goals might include: increasing developer engagement, driving product adoption, building a community of advocates, improving feedback loops, or supporting revenue. DevRel and advocacy guides stress that goals should be specific and tied to metrics you can track. Without clear goals, programs drift and impact is hard to prove.
2. Identify and empower advocates
Identify people—inside your organization or in the community—who are passionate about your product and willing to speak, write, or support others. Empower them with resources, early access, training, and recognition. Developer advocates need to be credible with developers; give them the tools and freedom to create content and represent the product authentically. Orbit’s community resources and DevRel book offer frameworks for identifying and scaling advocates.
3. Create valuable content
Valuable content is the backbone of developer advocacy: tutorials, webinars, technical blog posts, code examples, and documentation. Content that educates and informs helps developers succeed and positions your advocates (and your company) as trusted sources. Google’s E-E-A-T guidance applies: content should be accurate, useful, and where possible experience-based. Invest in quality and depth; thin or promotional content undermines advocacy.
4. Host events and meetups
Events and meetups bring developers together and create opportunities to learn, network, and provide feedback. DevRel and community practice show that in-person and virtual events build loyalty and advocacy when they’re genuinely useful. Host or sponsor meetups, workshops, and conferences; use them to showcase advocates and strengthen community. HubSpot’s community marketing guide emphasizes that events are a key touchpoint for relationship-building.
5. Leverage social media
Social platforms—Twitter/X, LinkedIn, GitHub—are where developers discover content and engage with peers. Share content and engage with developers regularly; use advocates to amplify and add authenticity. Social presence supports awareness and community; keep the tone helpful and substantive rather than purely promotional.
6. Measure and iterate
Use data and analytics to understand how the program performs and what resonates with developers. Track engagement, adoption, content performance, and advocate activity. Iterate based on actionable metrics; avoid vanity metrics that don’t inform decisions. DevRel measurement often combines quantitative signals with qualitative feedback from community and advocates.
Case studies
GitHub
GitHub runs a strong developer advocacy and relations program: a dedicated DevRel team, community forum, documentation, learning paths, and events. Resources and community are central; advocates and community members contribute content and support. The program supports adoption and retention by making it easy to learn and succeed on the platform.
Google’s developer programs include documentation, certifications, Google Developers Groups (GDG), Google Cloud Next, and I/O. Resources, events, and initiatives help developers learn, build, and grow with Google’s technologies. Community-led GDG and large-scale events create touchpoints and advocacy at scale. The model is applicable in principle even at smaller scale: invest in education and community, and empower advocates.
Microsoft
Microsoft’s developer advocacy and relations include documentation, learn paths, events, and community programs. Resources and events help developers learn and build with Microsoft technologies. Like Google and GitHub, Microsoft combines content, community, and events to drive adoption and advocacy.
Conclusion
Creating a developer advocacy program works when you define goals, identify and empower advocates, create valuable content, host events and meetups, leverage social, and measure and iterate. GitHub, Google, and Microsoft show that programs that are relevant, useful, and community-oriented resonate with developers and drive adoption. For more, see creating a developer advocacy program and building a DevRel team.