How to get hired in DevRel: roundtable with industry leaders
summary
Companies recruit from active user communities, top docs contributors, GitHub and Stack Overflow top answerers, meetups and referrals; one program has ~80 open roles and another recruiter mentions screening ~800 resumes. Hiring processes emphasize a presentation (20–25 minutes) round, role-specific coding or product exercises for DPEs, and behavioral-based interviews that probe empathy, community impact, and how applicants would relay hard product feedback. Vanity follower counts matter less than sustained craft (regular blog/video history), persistence, and demonstrated community trust.
AI-written summary · about
chapters (10)
- 0:00Introduction to hiring
- 1:31Diverse roles in DevRel
- 5:37Finding unique candidates
- 9:51The importance of networking
- 14:28Showcasing your craft
- 20:47Strategic engagement signals
- 24:53Innovation in virtual events
- 29:11Empathy in communication
- 32:00Essential professional traits
- 37:27Navigating interview processes
related talks
01h 10mLife as a DevRel Panel
40mForging Your Career in DevRel Advocate to Exec
27mDevRel Leadership: all the pieces matter
22mReactive versus proactive strategies for developer relations
33mThe Strategic Power of DevRel: From Community to Business Impact
28mBuilding Thriving Communities in Platform Engineering: Collaboration, Innovation, and Growth
22mA CEO's perspective on dev rel, dev experience and ROI
41mBut what is a DevRel for?