From grimoire
Conducts structured behavioral interviews using the STAR method with standardized questions and scoring. Useful during hiring to ask competency-based questions that predict job performance.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:run-behavioral-interviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conduct a structured behavioral interview using STAR probing (Situation, Task, Action, Result) so that candidate assessment is grounded in evidence of past behavior, not self-reported claims or hypothetical answers.
Conduct a structured behavioral interview using STAR probing (Situation, Task, Action, Result) so that candidate assessment is grounded in evidence of past behavior, not self-reported claims or hypothetical answers.
Adopted by: Google uses structured behavioral interviewing across all roles, documented in the re:Work hiring guide; Amazon's entire interview process is built around behavioral questions mapped to Leadership Principles using STAR; McKinsey, Bain, and BCG use structured competency-based interviewing; the US federal government mandated structured behavioral interviewing for civil service hiring in the 1980s Impact: Schmidt & Hunter's landmark 1998 meta-analysis (85 years of selection research) found structured behavioral interviews have a validity coefficient of 0.51 for predicting job performance — roughly 2× the predictive power of unstructured interviews (0.38); the improvement comes entirely from standardization: same questions, same scoring rubric, independent evaluation before group discussion Why best: Unstructured interviews — conversational, improvised, rapport-driven — are dominated by the "halo effect" (one strong impression colors all other ratings), affinity bias (interviewers rate similar candidates higher), and first-impression anchoring; hypothetical questions ("what would you do if...") produce polished, socially desirable answers, not evidence; behavioral questions ask for specific past examples because past behavior under real conditions is the strongest predictor of future behavior in similar conditions
Sources: Schmidt & Hunter, Psychological Bulletin (1998); Google re:Work "Structured Interviewing" (rework.withgoogle.com); Campion, Palmer & Campion "A Review of Structure in the Selection Interview" (Personnel Psychology, 1997); SHRM "Behavioral Interviewing" knowledge center
Each question must map to a specific competency required for the role. Prepare this before any candidate is interviewed — not improvised in the room.
For each competency, write 1–2 behavioral questions:
Competency: Influencing without authority
Question: "Tell me about a time you needed to get buy-in from stakeholders
who did not report to you. What was the situation, and how did you approach it?"
Competency: Handling ambiguity
Question: "Describe a situation where you had to make an important decision
without having all the information you needed. What did you do?"
Behavioral question format: starts with "Tell me about a time...", "Describe a situation where...", or "Give me an example of..." — never "What would you do if..."
Cap at 3–5 competencies per interview. Shallow coverage of many competencies produces no signal; deep coverage of 4 competencies produces real evidence.
In panel or multi-round interviews, assign each interviewer to own 1–2 competencies exclusively. This prevents all interviewers from asking the same questions and creates MECE coverage of the role's requirements.
Document the assignment before the first interview in the series:
Interviewer A: Problem-solving, analytical reasoning
Interviewer B: Influencing, communication
Interviewer C: Team collaboration, conflict resolution
Hiring manager: Career trajectory, motivation, values alignment
After asking the question, most candidates answer in summary form. Your job is to extract the specific details using STAR probes:
| STAR element | What to probe for | Example probe |
|---|---|---|
| Situation | Context, stakes, timeline | "What was the situation? What were the constraints?" |
| Task | Their specific role vs the team's | "What were you specifically responsible for?" |
| Action | Their personal actions, not the team's | "What did you do? Walk me through your thinking." |
| Result | Measurable outcome, what they learned | "What was the result? How did you measure success?" |
The most important probe: "What did you specifically do?" — candidates often describe what "we" did; STAR requires individual attribution.
If an answer is hypothetical ("I would typically...") redirect: "I'm looking for a specific example. Can you think of a time when you actually did this?"
Immediately after the interview, score each competency on a consistent rubric before discussing with other interviewers. A simple 4-point scale:
1 — Strong No Hire: example demonstrates the opposite of the competency,
or no specific example provided
2 — No Hire: example demonstrates partial competency with significant gaps
3 — Hire: example demonstrates the competency as expected for this role level
4 — Strong Hire: example demonstrates exceptional competency beyond role level
Write your evidence summary: one paragraph per competency citing the specific example the candidate gave. Do not summarize impressions — cite what they said.
Bring scores and written evidence into the debrief. Protocol:
The debrief produces a hiring recommendation, not a vote. If there is meaningful disagreement on evidence, identify whether another interview round is needed.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireGenerates structured interview plans with competency-based questions, scorecards, panel assignments, and debrief templates for consistent candidate evaluation.
Design interview processes that assess actual capability, reduce bias, and provide good candidate experience. Use when building hiring practices or expanding the team.
Generates structured interview scorecards with competencies, behavioral questions, and scoring guidance for any role to reduce hiring bias.