Step one is to pick a failure. Don’t try to weasel your way out of this by talking about that one time you got a B in a college class. You’re not fooling anyone. At the same time, you probably also want to shy away from any colossal failures related to the kind of work you’re applying for. If the interviewer specifically asks for something related to work, try to at least pull the story from something that happened a long time ago. Choose a story in which something fairly important didn’t go right due to your personal actions (or lack of actions).
Note that I said “something” and not “everything”—the reason people so frequently trip up on this question is because they’re looking for a situation in which everything went wrong. You only need one thing to go wrong for your answer to work.
The reason why you don’t need to talk about some immense failure in which everything goes catastrophically and comically wrong is because you’re going to spell out why you felt this situation was a failure.
After you’ve picked your story, define failure in a way that works for it. Once failure is defined, your story no longer needs to be an obvious failure; it just has to be whatever you define failure to be.
As a manager, I consider it a failure whenever I’m caught by surprise. I strive to know what’s going on with my team and their work.
Now that you’ve established how you evaluate failure, tell the story that you chose. Try not to spend too much time setting the stage, and get to the punch line quickly. Interviewers don’t ask this question to see you squirm, they want to know how you handle setbacks—so get to the part where you’re dealing with the failure as quickly as possible.
Start with the situation, and explain why it was challenging. Then go into what you specifically did to try and rectify it. Presumably, since this is about failure, you will not be successful or will only be partially successful. That’s fine. Do not try to cover up the fact that things didn’t all go as planned. It’s impossible to do well in an interview if the interviewer doesn’t believe what you’re saying, so don’t try to sugar coat things.
Finally, at the end of your response, after you relay the awful outcome of your story, you get to the good stuff. You want to wrap up with your lessons learned.
Talk about why you think things went badly, maybe what you would have done in hindsight, and, of course, what you’ll be doing going forward.
What This Sounds Like
Our big problem was assuming that we would be able to get clean data from users. It’s one of my biggest takeaways from the experience: Never make assumptions about the data. I haven’t made that mistake again.