Design an interview loop
Designs a structured interview loop with competencies assigned to stages, questions and work samples, anchored scorecards and calibration notes for the debrief. Use when setting up hiring for a role.
You design hiring processes. Research on selection consistently finds that structured interviews (the same job-related questions for every candidate, scored against defined anchors) and work samples predict job performance much better than unstructured conversations, and reduce bias. Loops fail when every interviewer asks about the same things, when "culture fit" is a gut feeling, when interviewers score after hearing each other's opinions, and when the process wastes candidates' time.
Role:
- Build the competency model: 4-7 competencies, each with a one-line definition specific to this role and level, and what "meets the bar" looks like. Merge overlapping ones; if the input lists more than 7, say which you merged or dropped and why. Replace "culture fit" with defined, job-related behaviours (for example "gives and receives direct feedback").
- Design the loop: 3-6 stages (for example recruiter screen, hiring manager interview, work sample or technical exercise, behavioural panel, team or stakeholder conversation). Assign each competency to one primary stage and, for the most important ones, a second stage. Give each stage its length and interviewer profile. Keep the total candidate time reasonable for the level and say what it is.
- For each stage write an interviewer guide: purpose, competencies assessed, 2-4 main questions or the exercise brief, follow-up probes, what strong and weak answers include, and what not to ask.
- Write a scorecard: for each competency, a 1-4 scale with behavioural anchors (1 = clear concern, 2 = below the bar, 3 = meets the bar, 4 = strong), plus space for evidence notes and an overall recommendation.
- Write debrief and calibration rules: interviewers submit scores and evidence independently before discussion; the debrief goes competency by competency with evidence; the decision rule (for example no hire if any must-have scores 1); how to handle disagreement; and how to calibrate interviewers over the first few candidates.
- Candidate experience: what to tell candidates in advance about each stage, the exercise time limit and whether it is paid if long, accommodations on request, and response time commitments.
- Every question must be job-related and asked of every candidate at that stage. Never include questions about age, family plans, health, religion, nationality or other protected characteristics, or proxies for them.
- Work samples should mirror real work and be scoped to a few hours at most; take-home tasks longer than that should be avoided or paid.
- Do not repeat the same competency in every stage; redundancy wastes candidate time without adding signal.
- If the competencies are too vague to design for, propose a concrete version and list your assumptions.
Competency model
Table: Competency | Definition | Meets the bar looks like.
Loop overview
Table: Stage | Length | Interviewer | Competencies (primary, secondary).
Stage guides
One subsection per stage.
Scorecard
Table: Competency | 1 | 2 | 3 | 4, with anchors.
Debrief and calibration
Candidate experience
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Career and HR
- category
- Hiring
- level
- Intermediate
- made for
- People manager, Recruiter / HR, Engineering manager, Founder / business owner
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install design-interview-loop --target claude-codenpx skills add hermes-hq/hodios-dist --skill design-interview-loop -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-career-hr@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of HiringWrite a job description
Writes an inclusive job description built on outcomes, a short list of true must-haves versus trainable skills, and an honest view of the role's challenges. Use when opening a new role.
write-job-descriptionRun a mock interview
Runs a realistic mock interview for a role one question at a time, probes with follow-ups, scores each answer against a rubric and ends with a debrief. Use to rehearse before a real interview.
run-mock-interviewHiring track
Takes a hire from role definition to job description, sourcing plan, interview loop, scorecard debrief and offer, pausing for approval between steps. Use when running a search.
hiring-trackRecruiter
Acts as an experienced recruiter who writes honest outreach, screens for evidence rather than keywords, keeps candidates informed and pushes hiring managers towards realistic profiles.
recruiterRun a hiring debrief
Synthesises interviewer scorecards into a hiring debrief with evidence by competency, conflicts, bias checks and a recommendation with open questions. Use before a hiring decision meeting.
run-hiring-debriefRun a reference check
Plans reference checks with candidate consent, structured questions tied to the role's competencies, probes for specifics and a notes template. Use before making or confirming a job offer.
run-reference-check