“Tell me about a time when…” There are hundreds of these and they are mostly the same eight questions wearing different clothes.
What they are testing
The premise is that what you did before predicts what you will do next. So the interviewer is not really listening to the story — they are listening for whether you did something specific, whether you can describe your own contribution honestly, and whether anything actually changed as a result.
This is why “we” is a problem. If every sentence is “we decided” and “we built,” the interviewer genuinely cannot tell what you did. Say “I” about your own part. It feels boastful and it is not.
The themes underneath
| Theme | Questions that are really this | What they want to see |
|---|---|---|
| Influence | Changed someone’s mind · disagreed with your manager · sold an unpopular idea | That you used evidence rather than seniority, and that you named the actual objection |
| Failure | A mistake · a project that failed · feedback that was hard to hear | That you can say what went wrong without blaming, and that something changed afterwards |
| Pressure | Too much to do · a tight deadline · competing priorities | How you decided what not to do. That is the whole question. |
| Conflict | A difficult colleague · a disagreement · a team that would not cooperate | That you addressed it directly and did not simply wait it out |
| Initiative | Above and beyond · improved a process · nobody asked you to | Something concrete and small usually beats something vague and large |
| Ambiguity | No clear direction · had to decide without enough data · changing requirements | That you made a decision and said so, rather than describing a process |
Prepare six stories, not thirty answers
You cannot prepare an answer for every phrasing, and trying to produces something brittle. Six well-understood stories can be pointed at any of the themes above, and most good stories cover two or three at once.
Write down, for each: what the situation was in one line, what you personally did, and what the result was. Write the result first. If you cannot state it, the story is not ready and no amount of rehearsing the wording will fix that.
The mistakes that cost the most
- No result. The single most common failure. The story stops at “and it went well” or “they came around.” Go and find the actual outcome, even if it is not a percentage.
- Ninety seconds of background. Cut the setup to two sentences. Nobody has ever been rejected for giving too little context.
- “We” all the way through. If the interviewer cannot locate you in the story, the story does nothing for you.
- A failure story that is secretly a boast. “I care too much about quality.” They have heard it. Pick a real one with a real lesson; it builds far more trust than a safe one.
- Answering a judgement question with a story. “What would you do if…” wants a decision, not a memory.
On the follow-up
A good interviewer will push once: “what did they object to?” or “what would you do differently?” This is not scepticism, it is the point of the format — it is how they find out whether the story is yours.
Prepare for one level deeper than feels necessary on each of your six. If you can only tell the story at headline level, the follow-up will expose that, and it is an uncomfortable thing to discover in the room.