Software Development
DevRel Team Structure
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.
- Publisher / source
- samber/developer-relations-skills (found on skills.sh)
- Upstream record
- samber/developer-relations-skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication
- Content fingerprint
ac76de549436532bdfdd1c567b42fd4577d1392ee5a07c6427da40bf686e68b2