Home › Blog › IT Leadership

IT Leadership

The Interview Question I Added After Two Expensive Hires

Early in a hyper-growth phase, I hired two senior engineers back to back for the same kind of role, and lost both within eight months. Same pattern each time: dazzling interview, weak first ninety days, quiet resignation.

The third time I was about to make the same hire, I stopped and actually called the previous managers instead of just the references. Both times, the same phrase came up, almost verbatim: "brilliant alone, brittle in a team."

I'd been interviewing for technical depth and completely skipping how someone behaves when they're wrong in front of people. So we rebuilt the interview loop around a single new question: describe a time your first solution was wrong, and who told you. The answers sorted candidates faster than any whiteboard exercise ever had.

Daniel Kahneman's Thinking, Fast and Slow warns that we're far too confident in judgments formed from very little information. Two bad hires were exactly that: a confident judgment built on too little.

Building an IT and security organisation from scratch at Verse Innovation is where this lesson got expensive enough to actually stick.

What good answers sound like

  • A specific, recent example, not a hypothetical.
  • The person who corrected them is named with respect, not blamed.
  • What they changed in how they work afterwards.

Want the book behind the idea? Bookworm has lens-based summaries of leadership and decision-making classics.

What's an interview question you added only after it cost you not to have it?

First shared on LinkedIn in September 2026. Join the conversation there.

hiringinterview questionsengineering hiringteam buildingtalent acquisitionleadership