devrel-hiring

Builds scorecards, interview loops, portfolio evaluations, and ramp plans for DevRel hires.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill devrel-hiring-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devrel-hiring
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/devrel-hiring
Command: npx skills add https://github.com/samber/developer-relations-skills --skill devrel-hiring-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? DevRel has no standard job description or career ladder, so hiring managers often publish gatekeeper or pit-trap postings, run unstructured interviews, and judge candidates by resume instead of shipped work. This Skill produces the four artefacts a hiring manager needs to recruit developer advocates, community managers, educators, and DX engineers with rigor. ## Core Features & Use Cases - Role scorecard and posting: Generates a mission line naming the funding driver, 3-8 quantified ranked outcomes, and 5-7 weighted competencies, then audits the posting against the gatekeeper and pit-trap failure patterns. - Interview loop and question bank: Selects 3-5 formats from the field's verified set (presentation round, take-homes, DevRel-opinion round) matched to the target sub-role, with independent evidence-noted scoring combined mechanically against pre-set weights. - Portfolio and work-sample evaluation: Scores candidates against the six-signal rubric (public writing, speaking, code, community, teaching, developer voice), names negative signals explicitly, and designs paid work samples instead of unpaid spec work. - Use Case: A Series A founder drafting a founding Developer Advocate posting gets it flagged as a pit trap, rewritten with stated resources, ladder, and twelve-month goal, plus a 30-60-90 ramp anchored on a day-30 friction log. ## Quick Start Ask the assistant to design a hiring scorecard and interview loop for your first developer advocate hire at your company stage.

Frequently Asked Questions about devrel-hiring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a developer advocate job posting?

Start from a scorecard with a mission naming the funding driver, 3-8 quantified ranked outcomes, and 5-7 weighted competencies for the target sub-role. Then audit the posting against the gatekeeper and pit-trap patterns before publishing.

What interview loop should I use for a DevRel hire?

There is no standard DevRel loop, so pick 3-5 formats that test the role's pillar mix: presentation rounds for outreach advocates, coding take-homes for product-focused advocates and DX engineers, plus a DevRel-opinion question. Place portfolio evaluation before any new candidate work.

How do I evaluate a developer advocate candidate's portfolio?

Score six signals on a 0-3 scale: public writing, public speaking, code in public, community evidence, teaching artefacts, and developer-voice artefacts, weighted by the target sub-role. Name negative signals like follower counts without substance or ghostwritten content explicitly.

Can I ask DevRel candidates to do unpaid take-home work?

No. When a public portfolio already exists, evaluate that shipped work first instead of requesting new unpaid spec work. When the portfolio is thin, design a short, scored, paid work sample matched to the sub-role, such as a lightning talk or a support-thread review.

When should I not use this DevRel hiring skill?

Do not use it for candidate-side interview preparation or portfolio building, which belongs to the devrel-career skill, or for deciding where DevRel reports and how the team is structured, which belongs to devrel-team-structure. It also does not cover non-DevRel roles like backend engineers or product managers.