Hire a community manager if developers already show up somewhere and nobody's tending it. Hire a technical writer if support tickets keep asking questions your docs should already answer. Hire DevRel only once both of those are stable and you need someone to go find developers who don't know you exist yet.
Most founders get this backwards. They hire a DevRel person first because "developer relations" sounds like the senior, strategic title, then hand them a half-written docs site and a dead Discord and wonder why pipeline doesn't move in the first two quarters.
What each role actually does
A technical writer's job is precision: accurate docs, working code samples, a changelog nobody has to ask about in Slack. Judge the hire by whether support tickets about "how do I do X" drop within 90 days.
A community manager's job is presence: someone answers questions in your Discord or forum within hours, not days, and turns lurkers into people who post their own solutions. Judge the hire by response time and by how many answers come from other developers instead of your team.
A DevRel person's job is distribution: conference talks, sample apps, partnership content, the stuff that gets a developer who has never heard of you to try the product. Judge the hire by qualified signups traced back to a specific talk, repo, or piece of content, not by follower count or how many events they attended.
The confusion happens because all three eventually touch "developer experience," and a good DevRel hire can do surface-level versions of the other two. That's exactly the trap: they'll write a stopgap doc and answer a few Discord threads, look busy, and you still won't have addressed the underlying gap because DevRel's real job is external, not internal.
The order that actually works, and why
Community management goes first because it's infrastructure. Hiring an evangelist before you have a working answer engine for developer questions means every talk they give sends traffic to a support queue that's already three days behind. You're paying someone to drive people to a parking lot with no attendant.
Technical writing is the other prerequisite, for a blunter reason: DevRel content amplifies whatever's already true about the product. If the docs are wrong or thin, a great conference talk just gets more people to hit that wall faster. Fix the wall first.
Once both are in reasonable shape, DevRel earns its keep. Not before. The sequence isn't about seniority, it's about which failure mode is currently costing you the most: an unanswered Discord (community manager), a support queue full of doc gaps (technical writer), or genuine invisibility to developers who'd use your product if they knew it existed (DevRel).
There are two exceptions worth naming. If you're product-led and self-serve activation is the whole model, a generalist "technical content" hire who can write docs and run community part-time often beats hiring any of the three as a dedicated specialist until you're past a few hundred active developer accounts. If you're enterprise or sales-led, a developer advocate who can hold their own in a technical sales call becomes valuable earlier, because their job isn't top-of-funnel awareness, it's closing technical credibility gaps in deals already in motion.
The three-question test
Before opening a req for any of these roles, answer this:
- When a developer asks a question in your community channel or forum, how long until it's answered, and by whom? If the answer is "days, and usually by an engineer pulled off other work," you need a community manager before anything else.
- Pull your last 20 support tickets. How many are answerable by docs that don't currently exist or are wrong? If it's more than a third, hire a technical writer before you hire anyone whose job is to bring in more developers.
- Are developers who'd genuinely use your product simply unaware you exist? If your docs are solid and your community is responsive but growth has flattened because nobody outside your existing users has heard of you, that's the DevRel gap, and it's real.
Most early-stage teams answer yes to question 1 or 2 and assume they have a question-3 problem, because "we need more developers to know about us" feels like the ambitious answer. It's usually not the accurate one.
What this costs to get wrong
The most common failure pattern: hire DevRel first, at $130K-$180K loaded cost for a mid-level hire, and six months later realize the actual bottleneck was always doc quality or community response time, something a $70K-$90K technical writer or community manager hire would have fixed for less money and faster.
The reverse mistake is rarer but real: staying in "founder does everything" mode past the point where docs and community response time are visibly degrading, because none of the three roles feels urgent enough on its own to justify a hire. If you're already spending more than a few hours a week personally answering the same three doc questions, that time is the signal, not a future headcount plan.
Frequently asked questions
Can one person do all three roles at an early-stage startup?
Yes, up to a point. A single "technical content" hire who splits time between docs and community moderation works fine below a few hundred active developer users. Past that, response time and doc debt both start slipping simultaneously, which is the signal to split the roles.
Is a developer advocate the same as DevRel?
Developer advocate is usually one job title within the broader DevRel function, focused more on hands-on technical credibility (demos, sample code, technical sales support) than the broader mix of content, community, and events a "head of DevRel" might own.
What if we're pre-revenue and can't afford any of these hires yet?
Founders should do all three jobs themselves in the earliest stage: answer forum questions personally, write the docs, give the talks. The hiring question isn't "which role" until the founder's personal time on these tasks becomes the actual bottleneck to growth.
How do we measure a community manager's impact if it's not pipeline?
Track response time to developer questions and the ratio of community-sourced answers to team-sourced answers. A rising ratio means the community is becoming self-sustaining, which is the actual goal, not raw member count.
Should the first DevRel hire report into marketing or engineering?
Whichever function currently owns the credibility gap you're hiring to close. If the gap is developer awareness and top-of-funnel content, marketing. If it's technical trust in sales conversations, engineering or product usually fits better.
We already have a community manager and technical writer but growth is still flat. Is DevRel the answer?
Possibly, but confirm it's genuinely a question-3 problem first. Check whether developers who'd use the product are unaware of it, versus aware but unconvinced, which is a positioning problem no DevRel hire fixes on their own.
If you're staring at a job req right now trying to decide which of these three to open, run the three-question test above before you write the title. The role that sounds most impressive to hire is rarely the one your current bottleneck actually requires.