# DevRel Career Paths Have a Glass Ceiling Problem The breadth that makes Developer Relations exciting also caps your career growth. Lewko and Parton identify a pattern: engineers who move into DevRel can't find their way back to engineering to advance. Developer Advocates don't see clear paths into other departments. The reasons are structural, not personal. First, the "jack of all trades" nature of DevRel means practitioners often lack the deep expertise needed to progress from an individual contributor role into a specialized department. You're good at many things but not expert-level at any one. Second, DevRel teams are typically small and practitioners are self-starting, so people management opportunities are limited -- you can't build management experience when there's nobody to manage. Third, the broader organization often doesn't understand what DevRel roles involve or what skills they represent, making lateral moves harder to negotiate. The numbers underscore the problem: 27% of DevRel professionals have less than two years of experience, and 47% less than five. There's no formal training pipeline -- 82% learn on the job. This means the field is young, unstructured, and operates without the career scaffolding that engineering, product, or marketing teams have built over decades. Combined with the burnout pressures (high travel, public-facing visibility, the stress of representing a company to a skeptical audience), you get a field where people burn bright and burn out fast. The fix requires intentional organizational design. DevRel leaders need to create IC ladders that reward deepening expertise (not just breadth), establish clear promotion criteria tied to impact rather than activity volume, and build bridges to adjacent departments. The practitioner's responsibility is to resist the "do everything" pull and deliberately cultivate depth in one or two areas -- whether that's technical writing, community strategy, product feedback loops, or public speaking -- rather than staying perpetually generalist. <!-- atomicity: 1 idea ✓ --> ## Why This Matters A field that can't retain experienced practitioners loses institutional knowledge every 2-3 years. The glass ceiling isn't just a career problem for individuals -- it's a program sustainability problem for companies. If your best DevRel people keep leaving because they see no path forward, you're rebuilding from scratch on a cycle that guarantees you never reach maturity Stage 3 or 4. ## Links - [[3. Resources/Literature Notes/Women Rising – How to Succeed in Community Management]] — evidence-for: gendered gaps in recognition, pay, and senior representation show how the career ceiling operates in adjacent community roles. - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — evidence-for: unclear advancement paths turn sustained role breadth into a structural exhaustion and retention problem - [[3. Resources/Permanent Notes/DevRel Maturity Is a Five-Stage Progression Not a Binary State]] — applies-in: a program cannot mature if its experienced practitioners have no credible path to deepen or advance - [[3. Resources/Permanent Notes/DevRel as Railroad Infrastructure]] — extends: connective work is hard to promote because organizations depend on the infrastructure while crediting the departments that travel over it - [[3. Resources/Literature Notes/The Importance of Career Laddering]] — offers Slack's explicit senior, staff, and principal expectations as a concrete counterexample to the missing DevRel scaffolding this note diagnoses - [[3. Resources/Literature Notes/Purpose of the 2023 Developer Relations Report]] — evidence-for: compensation and culture benchmarks make structural career differences visible across a geographically broader profession. - [[3. Resources/Literature Notes/Raising the Next Generation of DevRel]] — applies-in: deliberate depth in one skill is a practitioner response to broad DevRel roles that lack explicit advancement ladders. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists this note under Community + Sustainability. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists this note under DevRel Operations & Measurement. ## Source - [[3. Resources/Literature Notes/DevRel at Scale - Operations Measurement and Organizational Design - Literature Note]] - [[3. Resources/Readwise/Books/Developer Relations]] - [[3. Resources/Readwise/Books/Engineering Management for the Rest of Us|Engineering Management for the Rest of Us]]