Extended definition
An interview kit operationalises structured, competency-based interviewing for one role. Instead of every interviewer making independent decisions about what to ask and how to score, the kit provides everything in one place.
A senior software engineer kit specifies the four competencies that matter, the two behavioural and one situational question per competency, the scoring rubric for each, which interviewer in the loop owns which competencies, and what each interview is supposed to focus on. Kits are usually built once per role family and reused, with quarterly reviews to keep questions fresh and competencies aligned to evolving role needs.
Modern interview intelligence platforms surface kits inside the interview itself.
Key elements of an interview kit
A complete kit contains six things:
- Role overview — What the role is, who it reports to, what success looks like, why someone would join. Gives interviewers shared context before reading the candidate’s CV.
- Competencies — The 3-6 competencies the role is being assessed against, with definitions and behavioural anchors so interviewers share understanding of what each competency means in practice.
- Question library — 2-3 questions per competency — usually behavioural and situational — with suggested probes. Pre-written so interviewers don’t reinvent each cycle.
- Scoring rubrics — For each question or competency, an anchored rubric describing what a 1, 2, 3, 4, and 5 answer looks like. Specific behavioural descriptions, not abstract scales.
- Interviewer assignments — Who in the loop covers which competencies, with rationale. Avoids overlap and ensures full coverage.
- Loop structure — The order of interviews, what each interview is for (initial screen, technical depth, manager fit, executive interview), and how outputs roll up into the debrief.
Kits are built collaboratively: hiring manager, recruiter, and often a senior IC contribute. They’re version-controlled, dated, and reviewed regularly. Without that discipline, kits decay — questions become stale, competencies drift from current role needs, scoring rubrics get reinterpreted differently by new interviewers.
Why interview kits matter
Kits are how structured interviewing scales beyond a single hire. Without a kit, every new interviewer for a role makes their own assumptions about what to ask and how to score, and consistency collapses.
With a kit, every candidate for the same role goes through the same interview, scored against the same rubric, with the same competency coverage. For hiring managers, kits also reduce preparation time — instead of designing an interview from scratch each cycle, they pull the kit and adapt at the margins.
For VPs of TA, kits are the unit of compounding: investing in one strong kit per role family produces faster, more consistent hiring across hundreds of future interviews.
Common mistakes and misconceptions about interview kits
- Building kits and never updating them — A kit from 18 months ago likely uses competencies that have shifted, questions candidates have memorised, and rubric anchors that don’t reflect the current bar. Quarterly review is the minimum cadence.
- Building generic kits across role families — A “senior individual contributor” kit covers too many actual roles to be useful. Kits should be specific enough that one role family — senior backend engineers, enterprise account executives — fits cleanly.
- Treating the kit as the hiring manager’s document — Kits work when the recruiter, hiring manager, and senior ICs co-own them. Hiring-manager-only kits become idiosyncratic to one person’s preferences.
- Skipping the rubric — Pre-written questions without scoring rubrics produce inconsistent scoring. The rubric is what makes the kit operational rather than a question list.
- Letting interviewers ignore the kit — If individual interviewers freelance their own questions, the kit fails. This is usually a calibration and culture problem, not a tooling problem — leaders need to enforce kit usage as the standard.
Frequently asked questions
What is an interview kit?
An interview kit is the bundle of materials that defines how a specific role is interviewed — competencies to assess, questions to ask, scoring rubrics, interviewer assignments, and the order of the loop. It's the operating manual for hiring a particular role. Instead of every interviewer making independent decisions about what to ask and how to score, the kit provides everything in one place.
What's the difference between an interview kit and an interview scorecard?
An interview kit is the role-level package — competencies, questions, rubrics, interviewer assignments, loop structure. The scorecard is the per-interview form interviewers complete after each interview. The kit defines how the role is interviewed; the scorecard captures the evidence from each conversation.
Who builds the interview kit?
Recruiter, hiring manager, and often a senior IC together. Recruiters bring market knowledge and process discipline; hiring managers bring role context; senior ICs bring depth on the technical or functional competencies. Kits built by one person tend to be either too generic or too idiosyncratic.
How often should interview kits be updated?
At minimum quarterly for actively-used kits, plus a refresh whenever the role's responsibilities change materially or the team structure shifts. Questions get memorised by candidates over time; competencies drift; rubrics become misaligned. Kits aren't write-once artefacts.
Where do interview kits live?
Ideally inside the ATS or interview intelligence platform so they surface at the right moment for the right interviewer. Kits stored in shared docs or wikis tend to drift, get duplicated, and not get used at the moment of interview. Embedded kits are the operational standard.