Skip to content

benmonopoli/open-recruit / skills/marketing-hiring/marketing-hiring-developer-relations-devrel

marketing-hiring-developer-relations-devrel

Verified

Developer relations professionals bridge a company and its developer audience — through technical content (tutorials, documentation, blog posts), conference speaking, community engagement, and API/SDK adoption. For companies whose users or

Developer Relations / DevRel — Hiring Guide

How to Use This Guide

  • Sourcing: Use the title synonyms and Boolean strings in each section
  • Screening: Skill tiers: T1 = must-have, T2 = differentiator, T3 = rare upside
  • Interviewing: Use the assessment approach to design your interview loop
  • Benchmarking: Comp ranges are US market, growth-stage (Series B–D). Adjust for location, company stage, and current market

Universal Seniority Framework

LevelTypical YoEWhat they ownScope
Coordinator / Associate0–2 yearsExecutes defined tasks, supports campaignsSelf
Manager / Specialist2–5 yearsOwns a channel or programme end-to-endChannel / function
Senior Manager / Senior5–8 yearsDrives strategy for a channel, leads small teams or agenciesTeam / function
Director8–12 yearsOwns a marketing function (e.g. demand gen, brand), manages managersDepartment
VP / Head of Marketing12+ yearsFull marketing function ownership, budget, exec reportingCompany
CMO15+ yearsCompany-wide marketing strategy, board-level, often P&L exposureCompany + external

Marketing-specific promotion signal: Moving from execution to strategy. The jump from Senior to Director is often the hardest — it requires comfort with ambiguity, managing through influence, and operating with incomplete data.


Developer Relations / DevRel

What This Role Does

Developer relations professionals bridge a company and its developer audience — through technical content (tutorials, documentation, blog posts), conference speaking, community engagement, and API/SDK adoption. For companies whose users or buyers are developers — including SEO tools with technical users, developer tools, APIs, and infrastructure products — DevRel is a growth function, not just a marketing one. The best DevRel engineers are practitioners first: they write real code and engage authentically.

Titles & Synonyms

LevelCommon titles
JuniorDeveloper Advocate, Junior DevRel Engineer
MidDeveloper Advocate, Developer Relations Engineer
SeniorSenior Developer Advocate, Senior DevRel Engineer
DirectorHead of Developer Relations, Developer Relations Director, VP DevRel
AdjacentDeveloper Experience Manager (DX), Technical Community Manager

Skill Tiers

Tier 1 — Must-have:

  • Technical credibility: can write real code in at least one language; has built and shipped something
  • Technical content: tutorials, code samples, blog posts, documentation — can produce content that a developer trusts
  • Developer empathy: understands the developer experience from the inside — setup friction, API design, documentation gaps
  • Public speaking: comfortable presenting at conferences and meetups — technical talks, not generic marketing presentations
  • Developer community presence: GitHub activity, Stack Overflow, Discord, Hacker News — is a participant in developer culture

Tier 2 — Differentiator:

  • Developer content at scale: YouTube channel, blog following, podcast, newsletter — an owned developer audience
  • SDK/API advocacy: driving adoption through integrations, tutorials, and sample applications
  • Community programme management: developer ambassador or champion programmes
  • Product feedback loop: structured process for turning developer pain points into product improvements
  • Open source experience: contributions to or maintenance of relevant open source projects

Tier 3 — Bonus:

  • Framework or tool authorship
  • Keynote speaking experience at major developer conferences (KubeCon, PyCon, JSConf, etc.)
  • Strong personal brand in a developer community
  • Multilingual technical content creation

Sourcing Strings

# LinkedIn X-Ray
site:linkedin.com/in/ ("developer advocate" OR "developer relations" OR "DevRel" OR "head of developer relations" OR "developer experience") -recruiter -talent -jobs

# Technical depth signal
site:linkedin.com/in/ ("developer advocate" OR "DevRel") ("open source" OR API OR SDK OR "technical content" OR "developer community") -recruiter

# GitHub — active in developer community
site:github.com "developer advocate" OR "DevRel" "joined on" followers:>50
site:github.com "joined on" ("developer advocate" OR "developer relations") followers:>30

# Conference speakers
site:sessionize.com "developer advocate" 2024 OR 2025
site:papercall.io "developer relations" "API"

Seniority Signals

  • Junior → Mid: Creates content independently; presents at meetups without scaffolding; generates real developer engagement
  • Mid → Senior: Has an owned developer audience; drives measurable API/SDK adoption; influences product roadmap based on developer feedback
  • Senior → Director: Builds the DevRel function and team; connects developer engagement to business metrics; represents the company in the developer ecosystem at a strategic level

Red Flags

  • Technical credibility is thin — "I talk about technical things" but can't write code
  • Content is polished but shallow — not written from genuine practitioner experience
  • Conference talks are about the company's product, not developer education
  • No GitHub presence or developer community activity
  • Cannot articulate how DevRel drives business outcomes (not just community goodwill)

Compensation (2025, US, Growth-Stage)

LevelBase salary range
Junior / Advocate$90k – $125k
Mid$120k – $165k
Senior$155k – $215k
Head / Director$195k – $275k+

DevRel commands near-engineering compensation — the technical bar is genuinely high. Expect competition from engineering roles for the same talent.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall