Devrel Team Structure

by samber98ed86da8babMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Designs the developer relations org - which function DevRel reports to (marketing, product, engineering, CEO, sales) and what that line starves, the shape (centralized, split, embedded, hub-and-spoke), the coverage map across advocacy, community, docs and education, the interlocks with product, docs, support and sales, and the trigger for the next re-org. Use whenever someone asks where DevRel should sit, who DevRel should report to, how to structure or restructure a devrel team, which devrel roles to staff at this size, whether to embed advocates in product teams, why devrel keeps getting pulled into other teams' work, or how devrel and docs divide ownership - even if they only say the team feels wrong. Not the budget split - use samber/developer-relations-skills@devrel-budget-allocation.

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json32.6 KBapplication/json
references/org-design-brief-example.md8.5 KBtext/markdown
references/reporting-line-tradeoffs.md5.3 KBtext/markdown
references/sourced-numbers.md7.4 KBtext/markdown
references/team-shapes-and-interlocks.md5.8 KBtext/markdown
SKILL.md25.2 KBtext/markdown

Source and attribution

Source:samber/developer-relations-skillsinskills/devrel-team-structureat commit98ed86d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal