Use when building or overhauling a hiring process for a role to reduce bias and improve quality-of-hire
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill design-hiring-process --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Design Hiring Process?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-design-hiring-process)More formats (shields.io, HTML) on the badges page.
---
name: design-hiring-process
description: Use when building or overhauling a hiring process for a role to reduce bias and improve quality-of-hire
source: Laszlo Bock "Work Rules!" (2015); Google's Project Oxygen hiring research; Schmidt & Hunter meta-analysis (1998)
tags: [hiring, recruiting, structured-interviews, bias-reduction, talent-acquisition, leadership]
verified: true
---
# Design Hiring Process
Create a structured, repeatable hiring process that predicts job performance and reduces bias.
## Why This Is Best Practice
**Adopted by:** Google (Project Oxygen), Stripe, Airbnb, and organizations following Schmidt & Hunter's 80-year meta-analysis of hiring validity
**Impact:** Structured interviews have 2× the predictive validity of unstructured ones (Schmidt & Hunter, 1998); Google's data-driven hiring reduced bad hires by 25% after removing brain-teasers and adding structured rubrics
**Why best:** Unstructured hiring defaults to affinity bias — interviewers hire people like themselves. A structured process defines what "good" looks like before meeting any candidate, forcing evaluation against a common standard.
## Steps
1. **Write the job scorecard** — Before opening the role, define 4–6 competencies required for success in the first year. Each competency has a behavioral definition and an "A-player" example. This is not a job description; it is the evaluation rubric.
2. **Map the interview stages** — Assign each competency to one interviewer. No competency is assessed by more than two people. Typical stages: recruiter screen → technical/skills screen → structured panel → executive calibration.
3. **Write structured questions** — For each competency, write 2–3 behavioral questions ("Tell me about a time when…") and 1 work-sample prompt. Behavioral questions are more predictive than hypotheticals.
4. **Define the scoring rubric** — Use a 1–4 scale per competency: 1 = clear no, 2 = leaning no, 3 = leaning yes, 4 = clear yes. Write behavioral anchors for 2 and 4 so scorers calibrate consistently.
5. **Train interviewers** — Run a 60-minute calibration session before the first candidate. Interviewers practice scoring on a sample response. Standardize how the debrief will run.
6. **Run independent scoring** — Each interviewer submits a written score before the debrief. Verbal-only debriefs allow the first person to speak to anchor everyone else.
7. **Debrief with data** — Facilitator reads scores aloud. Discuss only competencies with disagreement (≥2 point gap). Make a hire/no-hire decision tied to scorecard, not gut feel.
## Rules
- The scorecard must be written before sourcing begins, not after the pipeline fills.
- Interviewers cannot discuss the candidate with each other before submitting written scores.
- Every candidate for a role must answer the same core questions — no improvisation per interviewer.
- Reference checks are mandatory for final candidates; ask open-ended performance questions, not yes/no.
- Track outcomes: review quality-of-hire at 6 months to calibrate the scorecard over time.
## Examples
Stripe's engineering hiring process assigns one interviewer exclusively to "cross-functional communication" — a competency not covered by technical rounds. This catches technically strong candidates who create coordination debt, a failure mode common in fast-scaling engineering orgs.
## Common Mistakes
- **Job description as scorecard** — Listing 20 requirements produces no shared evaluation standard; interviewers still evaluate on vibes.
- **Group debrief without pre-scores** — The loudest voice or most senior person anchors the group; quiet dissent disappears.
- **Skipping reference checks** — The best signal on how someone handles failure comes from prior managers, not from the candidate.
## When NOT to Use
- Do not apply this process for a one-off contractor or freelancer engagement where speed matters more than predictive validity and no scorecard infrastructure exists.
- Do not use structured behavioral interviewing for roles where the team is so small that every hire is a relationship hire requiring cultural co-founder judgment beyond a rubric.
- Do not run a full structured process when backfilling an identical role with an internal transfer who has already demonstrated the competencies in the same environment.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!