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 made a biased snap judgment and needs to be more self-aware and open-minded in future interviews. Better training will fix the problem. The 'candidate presentation' narrative ignores that the interviewer's brain is a 'corrupted sensor' that shouldn't be trusted.
Structural analysis: The interview was an unstructured, single-evaluator process with no scoring rubric, no blind review, and no systemic check on first-impression anchoring. These conditions reliably produce confirmation loops regardless of the evaluator's intentions or training history. Mira's intervention was an accident of collegial culture, not a designed safeguard. The 'fundamental attribution error' is correct but misses the 'Anchoring' — the error isn't just about the person; it's about the 'timing' of the first signal.
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.
