DevRel Leadership: all the pieces matter
summary
Argues developer relations must combine concrete roles: acting as customer zero to catch product blindspots, practicing bi-directional advocacy between engineering and external developers, and choosing org structure (verticals vs regional) to match outcomes. Gives concrete failures and fixes—Python sample with stray semicolons, going to Slack/GitHub for support, and a four‑year effort on WhatsApp Drive backup that hits roughly 30% of active users. Stresses measurable goals, right metrics (not vanity), and tracking team happiness on a 1–10 scale.
AI-written summary · about
chapters (19)
- 0:00Introduction and context
- 1:30What is DevRel and its challenges
- 2:56Rock stars and cargo cults in DevRel
- 4:20Customer zero and feedback loops
- 6:03Bi-directional advocacy role
- 7:29Leadership in DevRel
- 8:58Articulating team purpose
- 10:02Mapping ecosystem and leverage points
- 11:45Scaling DevRel organizations
- 13:07Community-focused outreach
- 14:51Developer support strategies
- 15:54Large-scale integrations impact
- 16:58Team growth and transitions
- 17:39Growing DevRel team members
- 19:32Measuring team happiness
- 21:13Understanding stakeholders
- 22:39Metrics and the Hawthorne effect
- 24:07Acceptable ways of failing
- 25:09Building purposeful DevRel
related talks
33mThe Strategic Power of DevRel: From Community to Business Impact
30mDevRel is a lie
40mForging Your Career in DevRel Advocate to Exec
01h 10mLife as a DevRel Panel
32mThe Four Pillars of Support in Developer Relations
45mDeveloper Joy – How great teams get s%*t done
12mLeveraging Previous Work Experience to Start a DevRel Career
59m✊ Join the DEV-olution: A Culture of Empowered Developers