I’ve interviewed a lot of senior engineering and engineering leadership candidates over the years, and the pattern I’ve noticed in how those conversations go is fairly consistent. The first thirty minutes are almost always fluent — people come prepared, they have good stories about scale and complexity and the hard technical decisions they navigated. They’ve thought about leadership principles, they can talk about team development and conflict and cross-functional alignment. They’ve done the preparation, and the preparation shows.
And then, usually somewhere in the second half, I ask the question.
I won’t build too much mystique around it. The question is roughly this: “Tell me about a time when you were convinced you were right about something important — a technical decision, an organizational call, a direction you wanted to take — and you were wrong. Not wrong because new information arrived that no one could have had, but wrong in a way you could have seen if you’d been thinking about it differently.”
What I’m listening for has almost nothing to do with the story they choose. The story is almost always fine. What I’m listening for is what happens in the candidate around the edges of the story — whether they can actually hold themselves accountable in the past tense without leaking defensiveness into it, whether they’ve genuinely learned something that changed how they operate or whether the story ends with “and that’s when I learned the importance of communication” (which is the professional equivalent of answering a different question than the one I asked), and whether they can name the specific failure mode in their own thinking without attributing the outcome primarily to circumstances.
Most people can tell a story about being wrong. Fewer people can tell a story about being wrong in a way that implicates their actual thinking rather than the context they were operating in. The version I’m listening for sounds something like: “I made the following assumption, and I made it because of this in how I was framing the problem, and here is the specific way my framing was off — not just that it turned out to be wrong, but why I couldn’t see it at the time.” That’s an order of magnitude harder to produce than a failure narrative, and it tells me something genuinely useful about how the person processes uncertainty and complexity.
The question isn’t on interview prep lists, I think, because it doesn’t have an obvious right answer to optimize toward. It’s not “tell me about a time you handled conflict” or “describe your approach to roadmap prioritization” — both of which have fairly legible shapes and can be prepared for fairly mechanically. The accountability question is harder to rehearse because the authentic version of it requires you to actually have done the reckoning that produces the insight. If you haven’t done the work of genuinely understanding where your thinking broke down, you’ll describe the situation accurately and the lesson vaguely, and that vagueness is the signal.
I want to be clear that this isn’t a gotcha. I’m not sitting across from a candidate hoping to catch them in something. I’m asking because I think the capacity for honest, specific self-assessment in retrospect is one of the most reliable indicators I’ve found of how someone will handle ambiguity going forward. Leaders at senior levels spend a significant portion of their time making decisions in conditions of genuine uncertainty, with incomplete information and competing pressures. The ones who can examine their own reasoning clearly — who have enough distance from their past selves to say “there it is, that’s where I went wrong” — tend to be the ones who can hold their current reasoning with appropriate looseness, rather than defending their position because they’ve committed to it.
What I’ve learned from years of asking this question is also something about leadership more generally: the people who are most capable and most trustworthy at senior levels are usually the people who have made significant mistakes and metabolized them, not the people who have managed to avoid significant mistakes. Experience isn’t just time; it’s time plus reckoning. The question is just a fast path to finding out which kind you’re talking to.
The strong answer isn’t the most dramatic story or the most impressive recovery. It’s the one where I can hear that the person actually changed something in how they think, not just in what they do. That’s the difference, every time.