I Bomb The Interview. Now What?

You know the night. The drive home, or the walk back to the lobby, when the answers you meant to give finally arrive. You can hear yourself talking too long. You can see the moment you guessed instead of saying you did not know. You already have a story about what it means.

It usually means less than the story.

I have sat on both sides of that table — recruiter, hiring manager, candidate — across corporate and agency searches. A bombed interview is information. It is not a verdict on your career, and it is not always a verdict on your fit. Sometimes the process was vague. Sometimes you were asked to perform chemistry instead of describe work. Sometimes you were simply unprepared for a question you should have seen coming.

First: write it down before it turns into folklore. What was asked. What you said. Where you went vague. Where you oversold. Do it the same day, while it is still ugly and useful.

Second: separate the performance from the evidence. If you could not speak to a specific example the job required, that is a gap you can close. If you were dinged for not “clicking,” that is a signal about their process as much as about you. You cannot coach yourself into being their kind of charming. You can get better at talking about the work.

Third: one note. Not a manifesto. Thank them. If there is a single clarification that is factual — a project, a result, a constraint you failed to mention — send it. Then stop. The night after is for your method, not for their inbox.

If you are the one running the interviews, this is your tell. Candidates who bomb in a sloppy process often did not fail the job. They failed an unstructured conversation. That is on you. Build an experience-based interview and you will still have people who are not the right hire. You will have fewer people who were never given a fair shot to prove they were.

Andrew L. Lee · Charlotte