Recruitment

---
name: recruitment
description: "Use when an org role acts as recruiter and must source, screen and move candidates through a hiring pipeline, balancing speed, candidate experience and signal. Covers role specs, referral channels, few purposeful interview stages, structured scorecards, fast feedback and stage conversion tracking."
tags: ["leadership","operations","people"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Recruitment — Best Practices

## Focus
Sources, screens, and moves candidates through a hiring pipeline — for technical or general roles — balancing speed, candidate experience, and signal quality.

## Best practices
- Write the role spec (must-haves vs nice-to-haves, leveling, success criteria) before sourcing starts — vague requirements produce vague pipelines.
- Prioritize referrals and warm channels alongside outbound — referred candidates convert faster and with better signal than cold outreach alone.
- Be explicit and fast with candidates: tell them what stage they're at, what's next, and when they'll hear back — silence is the top driver of candidate drop-off.
- Screen for evidence, not credentials alone — real projects, specific examples, and work samples beat pedigree as a signal.
- Keep interview stages few and purposeful — each stage should test something the previous one didn't, not repeat it.
- Debrief immediately after each interview while detail is fresh, using structured notes tied to the role's actual requirements.
- Track pipeline conversion by stage (applied -> screened -> interviewed -> offer -> accepted) to find where candidates are actually being lost.

## Common pitfalls
- Sourcing in volume without a clear spec, producing a pipeline that "sounds right" but doesn't map to what the role needs.
- Letting candidates go silent between stages — slow or vague follow-up loses strong candidates to faster processes elsewhere.
- Over-indexing on credentials/pedigree instead of concrete evidence of the actual skill needed.
- Treating every interview stage as pass/fail on "vibes" instead of structured, comparable signal.

## Tools & techniques
- Structured interview scorecards tied to specific role requirements, filled out immediately post-interview.
- Funnel/conversion tracking by stage to diagnose where the pipeline leaks.
- Sourcing channel mix: referrals, community platforms (GitHub, technical forums), and targeted outbound — not one channel alone.
- Fast feedback loops (same-day or next-day updates to candidates) as a default SLA, not an exception.