The Interview Question That Reveals Everything
There is a question I ask in every IT leadership interview that is not on any standard interview question list, that does not appear in the "top 50 behavioral interview questions for IT managers" articles that populate the first page of search results, and that consistently produces more signal about a candidate than the preceding forty-five minutes of structured conversation. The question is this: tell me about a time you were wrong about a technical decision, and what happened as a result.
The question is not a trap, though it functions as one for candidates who interpret every interview question as an opportunity to demonstrate strength rather than insight. The candidates who immediately pivot to a story where they were initially wrong but ultimately correct, where the mistake was minor, where the outcome was positive despite the error and largely through their own subsequent brilliance, have answered a different question than the one that was asked. They have answered "tell me about a challenge you overcame," which is a fine question with a well-rehearsed answer that tells you relatively little about how a person processes failure, updates their beliefs, or communicates uncertainty to their teams.
The candidates who answer the actual question, who describe a technical decision that was genuinely wrong, where the cost was real, where the impact on the team or the organization was significant, and who can walk through that experience with specificity and intellectual honesty, are telling you something much more valuable. They are demonstrating that they have a clear-eyed relationship with their own fallibility, which is a prerequisite for building teams that can surface problems early rather than managing them in the direction that makes the leader look best. They are demonstrating the ability to examine a failure analytically rather than emotionally, which is what the post-incident review requires. And they are demonstrating that they have had enough real experience to have been genuinely wrong about something that mattered, which is not the same as the carefully managed challenge that appears in the standard behavioral answer.
The follow-up question is equally revealing: what did you do differently after that? The candidates who describe specific, behavioral changes, different evaluation processes, new stakeholder consultation habits, explicit checkpoints they added to their decision-making, are demonstrating that the experience produced learning rather than just a story. The candidates who describe abstract lessons, "I learned to be more careful," "I realized the importance of communication," without the behavioral specificity of what more careful actually looks like in practice, have processed the experience emotionally but not operationally. Both responses tell you something true about the candidate. Only one of them predicts the behavior you actually want.
The willingness to be honestly wrong in an interview setting, where the incentive structure is entirely oriented toward presenting as strong and capable as possible, is a reasonable proxy for the willingness to be honestly wrong in an environment where the stakes are higher and the audience is a team rather than a hiring panel. Hire the people who can tell you about the time they got it wrong. They are the ones who will tell you when they are getting it wrong next time, which is the only version of that information that is actually useful.
