Markdown Editor

Technical Interview Rubric and Structured Interview Kit Template

Competencies mapped to ladder levels, interview loop, question bank, anchored 1 to 4 scale, scorecard, debrief protocol, bias and legal controls, retention

KarriereVollständigStructured-interview good practice; Acas guidance; US Uniform Guidelines (29 CFR 1607)technicalinterviewrubric

Anleitung: Use it when you hire engineers or engineering managers and want consistent, job-related decisions. Fill the competency mapping and coverage matrix first, then the loop, question bank and anchors before the first candidate. The main pitfall is discussing candidates before independent scorecards are written.

Vorschau

Technical Interview Kit: [Role title, level]

Structured interview kit for hiring software engineers and engineering managers: the competencies assessed and their mapping to career-ladder levels, the interview loop, a question bank with probes per competency, an anchored 1 to 4 rating scale with behavioural anchors, the interviewer scorecard, the calibration and debrief protocol, bias and legal-compliance controls (job-relatedness, consistency, accommodations), candidate experience and data retention. There is no formal standard for technical interviews; the kit follows widely published structured-interview good practice and fair-selection guidance such as UK Acas recruitment guidance and the US Uniform Guidelines on Employee Selection Procedures (1978). All questions and anchors are original text. Replace every [bracketed] value and every row marked Example. This is a documentation format, not legal advice.

Document control

FieldValue
Document ID[IKT-001]
Version[1.0]
Status[Draft / Approved / In use / Retired]
Owner[@hiring-manager]
Approvers/reviewers[@head-of-engineering], [@talent-acquisition-lead], [@people-partner], [@legal-counsel]
Role and family[Backend Engineer, software engineering family]
Target levels[L2 to L3]
Career ladder version[LAD-001 v1.0]
Requisition IDs[REQ-2026-031]
Locations and jurisdictions[Countries where candidates are hired]
Last updatedYYYY-MM-DD
Next reviewYYYY-MM-DD
Classification[Internal; question bank Confidential]

Approvals

RoleNameDecisionDate
Hiring manager[@name][Approve / Approve with conditions / Reject]YYYY-MM-DD
Head of Engineering[@name][Decision]YYYY-MM-DD
Talent acquisition lead[@name][Decision]YYYY-MM-DD
People partner or legal reviewer[@name][Decision]YYYY-MM-DD

Revision history

VersionDateAuthorChange summary
0.1YYYY-MM-DD[@name]First draft
1.0YYYY-MM-DD[@name]Example: Approved for Corvid Commerce backend hiring after a mock-loop pilot
1.1YYYY-MM-DD[@name]Example: Retired question Q-TEC-004 after it appeared on a public forum; added Q-TEC-006

Contents

1. Purpose, scope and principles

1.1 Purpose

This kit makes hiring decisions for [Role title] consistent, job-related and defensible. Every candidate for the role meets the same stages, is asked questions drawn from the same bank, and is rated on the same anchored scale by trained interviewers who write evidence before they discuss the candidate.

1.2 Scope

In scope: all interview stages from the technical screen to the debrief, levelling within the target band, and the records produced. Out of scope: sourcing, the offer and negotiation, background checks and reference checks, which follow [linked People procedures].

1.3 Principles

IDPrinciple
INT-P01Job-related. Assess only what the role needs, as written in the job description and the ladder level.
INT-P02Consistent. Same competencies, same stage order, same question set per stage and same scale for every candidate for the same kit.
INT-P03Evidence before opinion. Interviewers record what the candidate said and did, then rate, then discuss.
INT-P04Independent ratings. No interviewer sees another's ratings before submitting their own.
INT-P05Accessible. Every candidate is asked about adjustments and receives them where reasonable.
INT-P06Respectful. Candidates are treated as future colleagues; time is limited and candidates are never asked to do unpaid work that resembles real product work.
INT-P07Proportionate data. Collect only what the decision needs and keep it only as long as stated (section 11).

2. Roles and responsibilities

ActivityHiring managerRecruiterInterviewersDebrief facilitatorPeople partnerHead of Engineering
Define competencies and loopACCCCI
Approve question bankAIRCCI
Schedule and brief candidate, ask about adjustmentsIRIICI
Conduct interview and submit scorecardIIRIII
Run debriefCCCRII
Hiring and level decisionACCCCI (escalations)
Adverse-impact and quality reviewCRICAI

R = Responsible, A = Accountable, C = Consulted, I = Informed.

Debrief facilitator. A trained interviewer who is not the hiring manager, ideally from another team (sometimes called a bar raiser). The facilitator enforces the protocol in section 8 and may block a decision that is not supported by the written evidence, escalating to the Head of Engineering.

3. Competencies and level mapping

3.1 Competencies assessed

Competency (ladder ID)Requirement for this role (Example)Must-haveL2 barL3 bar
CMP-01 Technical skill: codingWrites correct, tested, readable code in [language]YesSolves a scoped problem with clean structure and testsAlso handles edge cases unprompted and explains trade-offs
CMP-01 Technical skill: designDesigns services with data model, interfaces and failure handlingYes (L3), No (L2)Designs a single component with guidanceDesigns a service end to end and defends trade-offs
CMP-02 DeliveryBreaks work into increments, manages riskYesDescribes delivering a feature in safe stepsDescribes leading a multi-person project to completion
CMP-04 Collaboration and communicationExplains reasoning, gives and receives feedbackYesCommunicates clearly when promptedDrives a discussion to a decision, handles disagreement
CMP-05 Leadership and mentoringHelps others growNo (L2), Yes (L3)Has helped a peerHas mentored with visible results
CMP-06 Operational and security ownershipOwns services in production, secure designYesDebugs systematically; knows basic secure codingHas led incident response; considers threats in design

CMP-03 Impact and scope is inferred from the evidence of the other areas and from the experience interview; it is not scored separately for L2 and L3 roles.

3.2 Coverage matrix (traceability)

CompetencyTechnical screenCoding exerciseSystem designDebugging and operationsExperience interviewObservations
CMP-01 codingXX2
CMP-01 designXX2
CMP-02X1 + design follow-up
CMP-04XXX3
CMP-05X1 (L3: add design probe)
CMP-06XX2

Every must-have competency needs at least two observations by different interviewers. Where the matrix shows one, the kit adds a follow-up probe in another stage (CMP-02 and CMP-05 in this Example).

4. Interview loop design

4.1 Stages

Stage IDStageLengthFormatInterviewer levelCompetencies
STG-1Recruiter conversation30 minVideoRecruiterLogistics, adjustments, motivation (not scored on the rubric)
STG-2Technical screen60 minVideo, shared editorL3 or aboveCMP-01 coding
STG-3Coding exercise60 minPair programming in candidate's chosen language from an allowed listL3 or aboveCMP-01 coding, CMP-04
STG-4System design60 minWhiteboard or diagram toolL4 or above (L3 for L2 roles)CMP-01 design, CMP-04, CMP-06
STG-5Debugging and operations60 minPrepared broken service with logs and dashboardsL3 or above with on-call experienceCMP-06
STG-6Experience interview60 minStructured behavioural questionsHiring manager or M3+CMP-02, CMP-04, CMP-05, CMP-01 design

Total candidate time after the recruiter conversation: 5 hours (Example). Offer the loop on one day or split across two, at the candidate's choice.

4.2 Level variations

Target levelChange to the loop
L1Replace STG-4 with a guided design discussion; STG-6 focuses on learning and collaboration
L4 and aboveAdd a technical leadership interview (cross-team influence, CMP-03 and CMP-05); system design uses an ambiguous multi-team scenario
Manager track (M3)Replace STG-3 with a code and design review exercise; add a people leadership interview and a delivery and operations interview

4.3 Exercise policies

  • Take-home work. Optional alternative to STG-3 only, time-boxed to [two hours], with the same rubric. Never ask for work that resembles real product work, and never use candidate output in production.
  • AI coding assistants. State the policy to the candidate in advance: Example: "Allowed in STG-3 for syntax and documentation look-ups; explain any generated code you keep." Interviewers assess understanding and judgement, not typing speed.
  • Languages and tools. Candidates choose from [list]. Do not penalise unfamiliarity with internal tools.
  • Recording. Interviews are not recorded unless the candidate agrees in writing in advance and there is a stated purpose (section 11).

5. Question bank

5.1 Rules for questions

  1. Each question has an ID (Q-AREA-NNN), a competency, the levels it suits, a main prompt, two to four probes and signals.
  2. Interviewers ask the main prompt as written and use only listed probes or neutral follow-ups ("tell me more", "what happened next").
  3. Questions about protected characteristics, family plans, health, age, nationality beyond right to work, religion or political views are never asked (section 9.2).
  4. A question is retired when it leaks publicly, when its pass rate shows it does not discriminate between levels, or when it shows unexplained adverse impact.

5.2 Technical skill: coding (CMP-01)

IDLevelsMain promptProbesStrong signalsWeak signals
Q-TEC-001 (Example)L1 to L3"Write a function that merges overlapping booking time slots for one warehouse and returns the free windows for a given day."What inputs would break this? How would you test it? How does it scale with 10,000 slots?Clarifies inputs, handles boundaries and time zones, writes tests, explains complexityStarts coding without clarifying, misses overlaps at boundaries, no tests
Q-TEC-002 (Example)L2 to L4"Here is a 60-line function that calculates order discounts. Refactor it so a new discount type can be added safely."What would you change first? How do you know behaviour is preserved?Adds characterisation tests first, small safe steps, names concepts clearlyRewrites everything at once, changes behaviour silently
Q-TEC-003 (Example)L2 to L3"Implement a rate limiter for an API client that allows N calls per rolling minute."What happens with concurrent callers? How would you observe it in production?Correct algorithm choice explained, concurrency considered, metrics suggestedFixed-window bug unnoticed, no thought for concurrency

5.3 Technical skill: design (CMP-01, CMP-06)

IDLevelsMain promptProbesStrong signalsWeak signals
Q-DES-001 (Example)L2 to L4"Design a service that sends order-status notifications by email and SMS to customers of an online shop."Expected volume and peaks? What if the SMS provider is down for an hour? How do you avoid duplicate messages? Which data is sensitive?Clarifies requirements, queues and retries with idempotency, considers failure and privacy, sketches data modelSingle synchronous call chain, no failure handling, no requirements questions
Q-DES-002 (Example)L3 to L5"Our product catalogue search is slow at peak and the team disagrees on whether to add a cache or a search engine. Walk me through how you would decide."What data would you gather? How would you roll the change out? What would make you reverse the decision?Frames decision criteria, measures first, staged rollout, considers operational costPicks a technology by preference, no measurement or rollout plan

5.4 Operational and security ownership (CMP-06)

IDLevelsMain promptProbesStrong signalsWeak signals
Q-OPS-001 (Example)L2 to L4"This checkout service returns errors for 5% of requests since the last deployment. Here are the logs and dashboards. Find out what is happening."What do you check first? Would you roll back now? How would you prevent a repeat?Hypothesis-driven, checks recent changes, weighs rollback early, proposes alert and test improvementsRandom exploration, ignores the deployment, no prevention ideas
Q-OPS-002 (Example)L2 to L4"A user-supplied file name is used to build a storage path in this code. What risks do you see and how would you fix them?"How would you test the fix? Where else could this pattern appear?Identifies path traversal, validates and normalises input, suggests tests and a search for similar codeMisses the issue or proposes a blocklist only

5.5 Delivery, collaboration and leadership (CMP-02, CMP-04, CMP-05)

IDCompetencyLevelsMain promptProbesStrong signalsWeak signals
Q-DEL-001 (Example)CMP-02L2 to L4"Tell me about a piece of work that turned out bigger than planned. What did you do?"When did you notice? Who did you tell? What did you cut or change?Early detection, transparent communication, scope trade-off with stakeholders, lessons appliedBlames others, notices late, no change in approach
Q-COL-001 (Example)CMP-04All"Describe a technical disagreement with a colleague. How was it resolved?"What was their strongest argument? What did you learn?States the other view fairly, uses evidence, commits to the decisionDescribes winning, cannot state the other view
Q-LEA-001 (Example)CMP-05L3 to L5"Tell me about someone you helped become more effective at their job."What did you do specifically? How did you know it worked?Concrete actions over time, measurable growth of the other personGeneric advice, no evidence of outcome
Q-LEA-002 (Example)CMP-05M3"Tell me about a time a team member's performance dropped. What did you do?"How did you find out? What support did you offer? What was the outcome?Early conversation, clear expectations, support and documentation, fair outcomeAvoids the conversation or escalates without support

6. Rating scale and behavioural anchors

6.1 Scale

RatingLabelGeneral anchor
1Strong noClear evidence the candidate does not meet the bar, or a serious concern (for example dismissive of security or of colleagues)
2Below barSome relevant evidence, but gaps that would need significant support at the target level
3Meets barEvidence matches the ladder descriptor for the target level in this competency
4Above barEvidence matches the next level's descriptor in this competency

Ratings are relative to the target level stated on the scorecard. The same answer can be a 3 for L2 and a 2 for L3. "Not assessed" is recorded when the stage did not produce evidence; it is not a 2.

6.2 Behavioural anchors per competency (target level L3, Example)

Competency1 Strong no2 Below bar3 Meets bar4 Above bar
CMP-01 codingCannot produce working code for the core caseWorking core case; edge cases and tests only with heavy promptingCorrect solution with tests and edge cases; explains complexity and trade-offsAlso improves the problem framing, anticipates production concerns, code is exemplary
CMP-01 designNo coherent designPlausible design for the happy path; failures and data handled only when promptedComplete design with data model, interfaces, failure handling and rollout; defends trade-offsFrames options for a multi-team context and shows when to revisit the decision
CMP-02 deliveryNo example of owning deliveryDelivered own tasks; little planning or risk managementLed a multi-person project, managed scope and risk, communicated proactivelyLed delivery across teams; changed how the group plans
CMP-04 collaborationDismissive or unclearClear when prompted; struggles with disagreementExplains reasoning clearly, listens, resolves disagreement constructivelyAligns several parties and adapts message to audience
CMP-05 leadershipNo example of helping othersOccasional help to peersMentored others with visible growth; contributes to hiring or standardsGrew senior people or leaders; shaped team practices
CMP-06 operations and securityNo systematic debugging; ignores securityFinds the issue slowly; security only when promptedHypothesis-driven debugging, rollback judgement, threat awareness in design, prevention actionsImproves systems and teams so the class of problem does not recur

7. Interviewer scorecard

7.1 Scorecard fields

FieldContent
Candidate ID[CAN-NNNN] (pseudonymous ID; no name in the rating file)
Kit and version[IKT-001 v1.0]
Stage and question IDs[STG-4, Q-DES-001]
Interviewer and date[@interviewer], YYYY-MM-DD
Target level[L3]
Evidence notes per competencyWhat the candidate said and did, with short quotes or descriptions
Rating per competency1 to 4 or "Not assessed"
Overall recommendationStrong no / No / Yes / Strong yes, for the target level
Level signal[Below / At / Above target level]
Adjustments provided[None / description, no health details]
SubmittedWithin [24 hours] and before the debrief

7.2 Worked example

FieldEntry
Candidate IDCAN-0187 (Example)
Stage and questionSTG-4, Q-DES-001
Target levelL3
CMP-01 design: evidenceAsked about volume (peak 40 messages per second at sale events), proposed a queue with per-channel workers and idempotency keys, sketched message table and status transitions
CMP-01 design: rating3
CMP-06: evidenceOn SMS outage: retries with backoff, dead-letter queue, alert on queue age; flagged phone numbers as personal data with restricted logging
CMP-06: rating3
CMP-04: evidenceSummarised trade-offs before choosing; adapted when I challenged cost of the second provider
CMP-04: rating3
OverallYes, at L3

8. Calibration and debrief protocol

8.1 Interviewer calibration

New interviewers shadow two interviews and reverse-shadow two more before interviewing alone. Every [quarter], interviewers rate the same recorded mock interview (with consenting actors) and compare scores; a spread of more than one point on the same competency triggers a calibration discussion of the anchors.

8.2 Debrief sequence

The facilitator runs the debrief in the order below so that the hiring manager and senior interviewers do not anchor the discussion.

8.3 Debrief rules

  1. Hold the debrief within [two working days] of the last interview. Nobody discusses the candidate before submitting a scorecard.
  2. Discuss evidence by competency, not by interviewer. Ratings may change only with a stated reason recorded in the notes.
  3. Comments not tied to evidence on the scorecard, or not job-related (accent, appearance, school name, "culture fit", career gaps without job relevance), are stopped by the facilitator.
  4. Decision rule (Example): hire when every must-have competency has a calibrated rating of 3 or 4, no competency is rated 1, and at least half of the overall recommendations are Yes or Strong yes. Any rating of 1 must be discussed and either upheld with evidence or revised with a reason.
  5. Level decision. Level is set by the profile of calibrated ratings against the ladder's expectations matrix. When evidence sits between two levels, offer the lower level and record the evidence that supports an early review.
  6. Record the decision, level, rationale and any dissent in the applicant tracking system within one working day.

8.4 Worked debrief outcome

CompetencySTG-2STG-3STG-4STG-5STG-6Calibrated
CMP-01 coding343
CMP-01 design333
CMP-02333
CMP-043323
CMP-05333
CMP-06333

Example for candidate CAN-0187 at target L3. The CMP-04 rating of 2 in STG-6 was discussed; the interviewer noted short answers but no negative evidence, and the panel calibrated to 3 based on stronger evidence in two other stages. The STG-4 ratings for CMP-02 and CMP-05 come from the follow-up probes required by section 3.2 (rollout plan and how the candidate would guide a less experienced engineer through the design), so every must-have has two observations by different interviewers. Overall recommendations: 4 Yes and 1 Strong yes (5 of 5 at Yes or above). All must-haves are at 3 or above and no rating is 1: hire at L3.

9. Bias and legal-compliance controls

9.1 Controls

IDControlOwnerEvidence
BIA-001Job-relatedness: every competency traces to the job description and ladder; every question traces to a competency (section 3.2)Hiring managerCoverage matrix
BIA-002Consistency: same stages, question sets and scale for all candidates on a kit version; deviations recorded with reasonRecruiterApplicant tracking records
BIA-003Adjustments: every candidate is asked before the loop whether they need adjustments, and reasonable requests are met (for example extra time, captioning, a different exercise format, breaks)RecruiterAdjustment log without health details
BIA-004Independent scoring before discussionFacilitatorScorecard timestamps
BIA-005Diverse panels where possible, at least two interviewers per must-have competencyRecruiterPanel list
BIA-006Interviewer training on structured interviewing, anchors and common biases before first interview and annuallyPeople partnerTraining records
BIA-007Prohibited topics list (9.2) briefed to every interviewerPeople partnerBriefing record
BIA-008Stage pass-through rates monitored by group where lawful; investigate when a group's impact ratio (selection-rate ratio) is below [0.8] (Example screening threshold); in small samples ratios are unstable, so combine several periods or use a statistical test before concludingPeople partnerQuarterly report
BIA-009Automated or AI tools used in screening or scoring are approved by People and legal, disclosed to candidates and never the sole decision maker. Never use tools that infer emotions from candidates' face, voice or other biometric data (prohibited in the EU workplace context under AI Act Art. 5(1)(f) since 2 February 2025)Talent acquisition leadTool register

9.2 Prohibited and restricted topics

Interviewers do not ask about or record: age, marital or family status, pregnancy or plans for children, religion or belief, sexual orientation, gender identity, race, ethnicity or national origin, disability or health, trade union membership or political opinions. Right-to-work questions are asked by the recruiter, of every candidate in the same way, at the stage set by local law. If a candidate volunteers such information, do not record it or discuss it in the debrief.

9.3 Legal context (check local law)

  • UK: the Equality Act 2010 protects nine characteristics and requires reasonable adjustments for disabled applicants; section 60 restricts questions about health and disability before a job offer, with limited exceptions (such as asking about adjustments needed for the assessment). Acas guidance recommends asking all applicants the same questions and using more than one interviewer where possible.
  • US: federal law (including Title VII, the ADA and the ADEA, enforced by the EEOC) prohibits discriminatory selection procedures; procedures with adverse impact must be job-related and consistent with business necessity. The Uniform Guidelines on Employee Selection Procedures (29 CFR Part 1607) describe impact monitoring and validation. As of October 2026 the EEOC has announced plans to rescind the Uniform Guidelines and a June 2026 Department of Justice opinion questions parts of them; they remain codified and private Title VII disparate-impact claims remain available. Check their current status.
  • EU: AI systems intended for recruitment or selection are listed as high-risk under the AI Act (Regulation (EU) 2024/1689, Annex III point 4, employment, workers' management and access to self-employment). After amendment by Regulation (EU) 2026/1744, the high-risk obligations for Annex III systems apply from 2 December 2027; check the consolidated text. Separately, Article 5(1)(f) has prohibited AI systems that infer emotions of people in the workplace (except for medical or safety reasons) since 2 February 2025, which rules out emotion-analysing video-interview tools. The GDPR applies to all candidate data (section 11).

This section is orientation only. Take advice from qualified counsel for each hiring jurisdiction.

10. Candidate experience

CommitmentTarget (Example)
Acknowledge applicationWithin 3 working days
Share loop outline, stage lengths, allowed languages, AI-assistant policy and preparation notesAt invitation to the technical screen
Ask about adjustmentsAt every scheduling message, in neutral wording
Decision after technical screenWithin 5 working days
Decision after loopWithin 5 working days of the last interview
Feedback offer to declined candidates after the loopShort written summary of strengths and gaps by competency, where local policy allows
Candidate surveySent after every loop, results reviewed quarterly

Interviewers start each stage by introducing themselves, stating the format and time, and leaving at least five minutes for the candidate's questions. Do not ask candidates to repeat a stage because of interviewer no-shows; reschedule promptly and apologise.

Communication template for the loop invitation. "You will meet [number] interviewers over [total time]. Each session covers one area: [list]. You may use [languages] and [AI-assistant policy]. If you need any adjustments for any part of the process, tell us at [contact] and we will arrange them. You do not need to tell us why."

11. Data protection and retention

11.1 Data inventory

DataLocationAccessRetention (Example)
Application and CVApplicant tracking system (ATS)Recruiter, hiring manager, panel[6 months] after the final decision for unsuccessful candidates, unless the candidate consents to longer talent-pool retention
Scorecards and debrief notesATS onlyPanel, facilitator, PeopleSame as above; moved to the employee file for hires per People policy
Exercise code and diagramsATS attachment or a time-limited repositoryPanelSame as above
Adjustment requestsATS restricted fieldRecruiter, PeopleSame as above, no medical details recorded
Recordings (only with consent)[Approved storage]Named reviewers[30 days] or end of the stated purpose
Aggregated fairness dataPeople analyticsPeople teamAggregates only, groups under [5] suppressed

Retention periods are Example values. Set them with People and legal counsel to cover the period in which a selection decision can be challenged in each jurisdiction, and no longer (GDPR Article 5(1)(e) storage limitation, where it applies).

11.2 Rules

  1. Notes are written only in the ATS scorecard. Personal notebooks, chat messages and private documents are not used for candidate evaluation.
  2. Notes are factual and professional, written on the assumption that the candidate may request a copy.
  3. Candidates are told in the privacy notice what is collected, why, for how long and how to request access or deletion.
  4. Requests for access, correction or deletion are routed to [privacy contact] and answered within the legal deadline.
  5. No candidate data is entered into external AI tools unless the tool is approved under BIA-009 and the privacy notice covers it.

12. Interviewer training and kit quality

12.1 Interviewer readiness

StepRequirement
TrainingStructured interviewing, this kit's anchors, prohibited topics, adjustments and data rules
ShadowingTwo shadow and two reverse-shadow interviews with an experienced interviewer
Sign-offHiring manager or facilitator confirms readiness
RefreshAnnual refresher and quarterly calibration exercise

12.2 Quality metrics

MetricFormulaTarget (Example)
Scorecard timelinessscorecards submitted within 24 hours / all scorecards≥ 95%
Inter-rater spreadshare of competencies where panel ratings differ by more than one point≤ 10%
Stage pass-throughcandidates advancing from a stage / candidates entering itTracked per stage; review sudden changes
Offer acceptanceoffers accepted / offers madeTracked trend
Candidate satisfactionmean survey score (1 to 5)≥ 4.0
Early hire successhires rated "meets" or better at the first performance review / all hires reviewed≥ 85%; compare by stage rating to test predictiveness
Impact ratio by grouppass rate of group / highest group pass rate, per stageInvestigate below 0.8; in small samples combine periods or use a statistical test

12.3 Review cadence

Review the kit every [six months] or after [20] completed loops, whichever is sooner: retire leaked or non-discriminating questions, add new ones with IDs, check anchors against recent debriefs, and update the revision history. Major changes (competencies, decision rule, stage list) are approved again by the approvers in Document control and apply only to candidates who start the process after the change.

13. Glossary and references

13.1 Glossary

TermDefinition
Adverse impactA substantially lower selection rate for one group than for another, which should trigger investigation
Impact ratioOne group's selection rate divided by the highest group's rate (four-fifths screening signal)
AnchorA written description of observable behaviour for one point on the rating scale
ATSApplicant tracking system
DebriefMeeting where the panel turns independent evidence into a decision
FacilitatorTrained interviewer who runs the debrief and enforces the protocol
Reasonable adjustment (accommodation)A change to the process that removes a disadvantage for a disabled candidate
Reverse shadowA new interviewer leads while an experienced interviewer observes
Structured interviewAn interview with predetermined, job-related questions, consistent administration and anchored scoring

13.2 References

ReferenceVersion or date checkedUse
Acas, Interviewing job applicants, acas.org.uk/hiring-someone/interviewing-job-applicantsPage updated 2026-06-30Same questions where possible, more than one interviewer, adjustments, secure notes
Equality Act 2010 (UK), sections 20 and 60, legislation.gov.ukCurrent consolidated textReasonable adjustments and pre-offer health questions
Uniform Guidelines on Employee Selection Procedures (1978), 29 CFR Part 1607Checked 2026-10-24; EEOC rescission planned and June 2026 DOJ opinion questions parts: check current statusImpact information (1607.4), validity (1607.5), documentation (1607.15)
US EEOC, Employment Tests and Selection Procedures fact sheet, eeoc.govFact sheet first issued 2007; check current pageJob-relatedness and business necessity, less discriminatory alternatives
Regulation (EU) 2016/679 (GDPR), Article 5(1)(e), eur-lex.europa.euCurrent textStorage limitation for candidate data
Regulation (EU) 2024/1689 (AI Act), Article 5(1)(f) and Annex III point 4, as amended by Regulation (EU) 2026/1744, eur-lex.europa.euArt. 5 applies since 2025-02-02; Annex III obligations from 2027-12-02; check consolidated textEmotion-recognition prohibition and high-risk classification of recruitment AI
Engineering Career Ladder (career/engineering-career-ladder)This collectionLevel and competency IDs

Standard and licence note

Structure aligned with widely published structured-interview good practice and with fair-selection guidance from UK Acas and the US Uniform Guidelines on Employee Selection Procedures (29 CFR Part 1607, a US government publication, whose rescission the EEOC has announced it plans), with legal orientation from the UK Equality Act 2010, the GDPR and the EU AI Act. These sources are cited for context only; no text is reproduced. All questions, anchors and examples are original text written for this collection. Check the current official versions and the law of each hiring jurisdiction before use. This is a documentation format, not legal advice. Template licence: MIT.

Ähnliche Vorlagen