The Interview Worth Remembering
Thirteen questions, what a good answer actually looks like, and what each one should do to your decision.
A hiring manager gave me feedback on a candidate recently. He used the wrong name. Twice.
He had spent an hour with her.
I want to be careful here, because the easy conclusion is the wrong one. This is not a story about a careless leader. He runs a stretched function, he had four interviews that week on top of a delivery deadline, and he is genuinely good at his job. And rejecting a candidate after an interview is completely fine — that is what an interview is for. Not everyone we meet is right for the role.
But an hour is an hour.
For that candidate, those sixty minutes were the longest and closest look she will ever get at his organisation. She took a day's casual leave. She rearranged a client call. She will describe that hour to her peers for years, and what she describes is his employer brand, whether he intended it that way or not.
So the question I have been sitting with is not how do we get hiring managers to concentrate harder. It is this: what makes an hour worth remembering — for the person deciding, and for the person being decided about?
The answer, I have come to believe, is structure. And not for the reason most people assume.
Forgettable candidates are usually a process problem
Here is what actually happens in an unstructured interview.
Every conversation drifts somewhere different. With the first candidate you spend twenty minutes on their last project because they were interesting about it. With the second you get into a tangent about a shared ex-employer. With the third the conversation stays polite and general because neither of you found a hook. All three were pleasant. None of them are comparable.
And what isn't comparable isn't memorable. Six pleasant, differently-shaped conversations blur into one impression by Friday — which is exactly how you end up using the wrong name.
Now flip it. Ask every candidate the same four or five well-built questions. Suddenly each person exists in your memory as a distinct set of answers to the same prompts. You remember the one who asked what the budget constraint was before answering. You remember the one who couldn't name a single decision she'd got wrong. You remember them because you can finally tell them apart.
Structure is what makes candidates vivid. Drift is what makes them interchangeable.
This is the counterintuitive part. People resist structured interviews because they sound mechanical — a form to be filled, a script to be read. In practice the opposite is true.
Structure also makes the hour worth something to them. A candidate who is handed a real problem from your actual roadmap walks out knowing more about the job than when she walked in — even when the answer is no. That is the difference between an hour spent and an hour taken.
What you are actually assessing
Before the questions, the frame. Every interview is trying to answer three things, in this order:
- Can they do the job? Demonstrated skill, not claimed skill.
- Will they do the job? Motivation, ownership, appetite for the unglamorous eighty percent of the role.
- Will they be easy to work with? Judgement, ego, how they behave when they disagree.
Most panels spend ninety percent of the hour on the first, and then make the decision on the third — without ever admitting to themselves that this is what happened. That unexamined gap is where bias lives, and it is where "culture fit" gets used as a label for a decision nobody wants to explain.
You cannot remove judgement from hiring, and you shouldn't want to. But you can make it explicit enough to be argued with.
How to shape the hour
Direction starts before the first question. This is the part most interviewers skip, and it costs them the data they need.
| Time | What happens |
|---|---|
| 0–5 min | You talk. What the role exists to fix in the next six months, and what this hour will cover. |
| 5–15 min | Their story — but directed. "Walk me through your last two roles, focusing on the parts closest to this one." |
| 15–40 min | Four or five core questions, with two follow-ups each. Depth beats coverage. |
| 40–50 min | A real problem. Work on it together. This is the part they will remember. |
| 50–58 min | Their questions. Genuinely theirs — not asked while you are already standing up. |
| 58–60 min | What happens next, and by when. Then hold to that date. |
That first five minutes does more work than it looks like. A candidate who knows what you are solving for can show you relevance. A candidate who is guessing gives you her generic answers — and then there is nothing to remember, because generic answers are identical across every person you meet.
The 13 questions
Pick four or five, not thirteen. Ask the same ones to every candidate for a given role. And ask two follow-ups on each — the follow-ups are where the real answer lives, because most people have a rehearsed first answer and very little behind it.
Judgement — can they think, or only recite?
"Here's something we're actually stuck on this quarter. How would you approach it?"
Tests applied thinking, and how someone operates before they have all the facts.
"Walk me through how you'd spend your first 60 days."
Tests whether they have understood the role, or only the title.
Ownership — what did they actually do?
"Tell me about something you shipped that you're proud of. What was your specific part in it?"
Tests real contribution, as distinct from proximity to someone else's success.
"Tell me about a decision you got wrong."
Tests honesty, capacity to learn, and the size of the ego.
Trade-offs — can they choose?
"Six weeks. You can ship X or fix Y, not both. Which do you pick?"
Tests prioritisation, and willingness to decide on incomplete information.
"When did you last push back on your manager or a senior stakeholder?"
Tests spine — and whether they can disagree without leaving damage behind.
People — for anyone who will manage
"Tell me about someone you managed who wasn't performing."
Tests managerial courage, process discipline, and basic humanity.
"Who is the best person you've hired — and who did you get wrong?"
Tests talent judgement, and self-awareness about their own hiring.
Ambiguity — recovery beats perfection
"Tell me about a time the goalposts moved mid-project."
Tests adaptability, and how they handle ordinary organisational reality.
Ask one thing deliberately just outside their stated depth.
Tests recovery — the single most transferable senior trait.
Motivation and retention — ask these in round one, not at offer stage
"Which part of this role would drain you?"
Tests honesty, and whether they have actually understood the job.
"When you resign, what will your current employer do — and what will you do then?"
Tests seriousness of intent, and buyback risk.
"Why this role, and why now?"
Tests whether they are running toward something or away from something.
Three cues we get wrong in India
Fluency is not competence. We consistently over-reward polished English and under-reward technically stronger candidates from tier-2 and tier-3 backgrounds. If the role does not require client-facing articulation in English, do not let it drive the score. This is the single most common avoidable bias I see in Indian interview panels.
Career gaps tell you nothing. A return-to-work parent, a caregiving break, a venture that didn't work. Ask what they did with the time, listen to the answer, and move on. The gap is not data. The answer is.
Job-hopping is a pattern, not a count. Three eighteen-month stints with rising scope is ambition. Three lateral moves at the same level is restlessness. You cannot tell which is which from the CV, so ask.
The part everyone skips: scoring
The best questions in the world are wasted if the scoring happens on Friday from memory.
- Score within thirty minutes, before the next candidate walks in. Memory decays faster than anyone believes — which is precisely how you end up using the wrong name a week later.
- In a panel, score independently first, then compare. Discuss first and you have simply recorded the opinion of the most senior person in the room.
- Use a four-point scale with no midpoint. A middle option lets people avoid making a call, which is the entire purpose of the exercise.
- Write one sentence of evidence per score — something they actually said. "Good communication" is not evidence. "Reframed my badly-worded question before answering it" is.
- Close the loop within a week with every candidate, including rejections. Your employer brand is built almost entirely by the people you did not hire.
What this is really about
The most common hiring failure I see is not a bad candidate. It is a good candidate assessed by an unprepared panel, rejected on a hunch, and then explained away afterwards as "culture fit."
Structure does not make hiring impersonal. It makes it defensible — and defensible hiring is the only kind that still looks right two years later, when you're asked why you passed on someone who went on to do the job brilliantly somewhere else.
You will forget the candidates you processed. You will not forget the ones you actually interviewed.
Both Sides of the Table
All thirteen questions in one guide — each read twice, once from the interviewer's chair and once from the candidate's. If you're hiring, it tells you what to listen for. If you're interviewing, it tells you what a strong answer must contain.
Download the guide →
