Loading...
Ren manages hiring for a mid-size tech firm. On March 12, a candidate named Kai walks in for a software engineering interview. Kai is nervous — he fumbles the handshake, sits down awkwardly, and takes a moment to collect himself. Within 30 seconds, Ren has already formed a judgment: 'Not confident enough for a senior role.' The interview lasts 45 minutes. Kai gives a strong answer on system design, but Ren focuses on the two seconds of hesitation before Kai began speaking. Kai mentions leading a team of eight engineers through a product launch, but Ren notes that Kai said 'we' instead of 'I' — proof, Ren decides, that Kai wasn't really in charge. When Kai solves the coding challenge correctly but uses an unconventional approach, Ren marks it as 'lacks standard methodology.' Every piece ...
Popular framing: Ren was just a bad interviewer; better interviewers would have hired Kai.
Structural analysis: Anchoring on a first impression converts subsequent evidence into raw material for confirmation — correct answers get re-scored as flaws, attribution shifts from situation to character. When the bias is named, the backfire effect strengthens conviction in the original judgement, because the criticism itself becomes evidence that others don't understand the 'instinct.' A halo (or anti-halo) cast in 30 seconds reliably propagates across 45 minutes regardless of who the interviewer is; the unstructured-interview architecture produces this distortion by design.
Focusing on Ren's individual bias keeps the organization's process design invisible and off the hook. It also implies the solution is psychological (train Ren) rather than architectural (redesign the process). Until the process changes, the next evaluator will face identical pressures and produce identical outcomes — even if they've completed bias training.
