Start here
How to get into DevRel
Four steps, in order, built from data this site keeps current: what to read, who to learn from, where to speak, and what the market is actually hiring for. No course, no waitlist.
1 · Read these in order
Not the order the documentation lists them in. This sequence puts personas before strategy, because a strategy written without an audience in mind is a plan aimed at nobody.
- 01What Developer Relations actually isStart here so the rest has a shape to hang on. The word covers four or five different jobs.
- 02Why companies fund itKnowing what the budget is for tells you which of those jobs a given company is really hiring.
- 03How the roles differAdvocacy, community, and docs are separate crafts. This is where you pick which one you are aiming at.
- 04Who you are actually servingRead this before strategy, not after. A strategy written without a persona is a plan aimed at nobody.
- 05Turning that into a programNow the strategy guide has something to work with: a role you want and an audience you understand.
2 · Learn from practitioners
11 communities, newsletters, and podcasts that an automated check confirmed are still reachable. Dead invite links are the norm in this space, so the dates matter.
3 · Speak somewhere
Speaking is the fastest way to build the public track record this field hires on. Soonest deadlines first.
4 · What the market is actually hiring
Of the 36 open DevRel roles listed right now, none are junior.
That is the normal state of this field rather than a bad week. DevRel is rarely an entry-level job, because it is usually funded on the assumption you already have credibility with developers. Most people arrive sideways: from engineering, from support, from technical writing, or from community work they did unpaid first. Aim at mid-level postings and expect your previous craft to be the qualification.
11 mid · 8 senior · 4 staff · 13 leadership