Starting a Developer Relations role is exciting—and easy to waste. Unlike pure engineering or marketing, DevRel sits in the middle. You can spend ninety days “building relationships” and have nothing tangible at review time.
This checklist is for advocates, DevRel engineers, and community managers joining product or platform teams. Looking for your next role? Start with open DevRel jobs or filter Developer Advocate and DevRel Engineer listings.
Week 0: Set the game board
Lock expectations with your manager before you ship content:
- What does “success in 90 days” look like in one sentence?
- Which channels are sacred (docs, status, billing) vs. safe to experiment in?
- Who owns community moderation, docs PRs, samples, and event budget?
Write those answers down. Ambiguity is the default failure mode in DevRel orgs.
Month 1: Detective phase — understand reality
Run the product as a developer
Complete hello-world and at least three failure paths. Capture confusing errors, missing docs, and slow steps. File issues like a power user—not an employee with Slack access.
Map stakeholders
Short coffees with PM, eng leads, support, and marketing. Ask: “What do you wish the last DevRel hire had learned in month one?”
Audit communities
Read Discord/Slack, GitHub Discussions, forums, and social. Note top complaints, champions who answer before you do, and gaps in onboarding.
Month 2: Builder phase — ship a thin vertical slice
Pick one outcome that is visible and reversible:
- A tutorial or sample that removes a top friction point
- Five+ docs PRs from real community pain
- A weekly product feedback ritual with measurable tickets
- A small event or AMA with a clear CTA back to docs
Document the delta. DevRel without artifacts looks like vibes.
Month 3: Amplifier phase — make the system better for everyone
- Write an internal playbook: “How we turn community signal into product work”
- Identify 3–5 champions and deepen those relationships
- Propose a program or content roadmap tied to a metric
- Share a short demo of what you shipped and what you measured
Anti-patterns that waste your first quarter
- Conference travel before you understand the product’s sharp edges
- Launching a new Discord when an existing one is neglected
- Content calendars with no feedback loop to engineering
- Optimizing follower count instead of activation or support deflection
Career tip: keep a brag doc
Every Friday, log: problem, action, metric, link. That doc becomes your review narrative—and interview stories when you next browse remote DevRel roles or leadership openings.
FAQ
I am joining as a DevRel engineer. Does this still apply?
Yes—swap “tutorial” for “sample app / SDK improvement,” but keep the detective → ship → amplify arc and the feedback loop to product.
How technical should my first project be?
Technical enough to earn eng trust, small enough to finish. A measured docs/onboarding win beats an unfinished conference tour.
Where should I look for roles that match this skill set?
Use DevRel Jobs and filter by role category and experience. Pair applications with a public write-up of a program or sample you shipped.
