Short answer: Don't summarise a whole project. Find the single moment where something changed - a decision or a reversal - and build your answer around it: what was true just before, what you chose, what it cost, and what it bought. That turn is what makes an example a story instead of a fog.
"Tell me about a time you…" questions trip people up because we answer them like a status report: lots of context, many stakeholders, tight timelines, and somehow no actual event. The interviewer is left with nothing to follow and nothing to judge.
Here's the fix.
A story is not a summary of a period. It's an account of something that changed. Without a turning point, there's no tension, and the listener has nothing to hold onto. Compare these two answers to "Tell me about a time you handled a difficult project":
Before (a fog):
So we had this project, it was quite complex, lots of stakeholders, and the timelines were tight. I was kind of coordinating between teams and trying to keep things moving, and overall it went pretty well, I think.
There's no moment in that. Nothing happened. The interviewer can't tell what you actually did or how you think.
After (a story):
Two weeks before launch we found the database migration would lock the table for six hours. I had to choose: delay the launch, or ship with the old column still in place and clean it up later. I chose to ship with the old column. It cost us a messy quarter of tech debt - but it held the launch date the sales team had already promised customers.
Same project. But now there's a decision, a real trade-off, and a result you can judge. That's a story.
Before you answer, locate the single moment the situation changed. Then tell four beats, in order:
The honesty in step 3 is what makes step 4 believable. An answer that's all upside reads as luck or spin; naming the cost makes you sound like someone who understands trade-offs - which is exactly what behavioural questions are testing.
You've probably heard of STAR - Situation, Task, Action, Result. It's a fine scaffold, but most people use it to justify dumping more context: they spend ages on Situation and Task and never get to a real decision.
"Find the turn" is STAR with the emphasis fixed. The Situation and Task collapse into one line of "before." The Action becomes a choice between two options - which is far more revealing than a list of things you did. And the Result splits into cost and gain, so it sounds like judgement rather than a highlight reel. If STAR is the skeleton, the turn is the heartbeat.
"Tell me about a time you failed." Keep the exact same shape - before, choice, cost, gain - and let the gain be the lesson. A failure told with a clear turn reads as self-awareness; a failure told as fog reads as evasion.
I spent nine days convinced a performance bug was in the database. It wasn't - I'd been reading the wrong metric the whole time. On day ten a colleague asked why I hadn't checked the queue. That was it. The cost was nine wasted days; what it bought me was a habit of stating my assumption out loud before I go deep, which has caught me twice since.
"Tell me about a time you disagreed with someone." The turn is the moment you decided how to raise it. Lead with the choice, not the conflict.
"Tell me about a time you led without authority." The turn is usually the moment you got someone to move without being able to tell them to. Name that moment.
Here's the practical trick: you can't memorise an answer for every possible question, but you can prepare a handful of turns from your own experience. Write four or five real moments where you made a hard call, each as four lines: before, choice, cost, gain. In the interview, you match the question to the nearest turn. Five turns cover most behavioural questions you'll be asked.
STAR stands for Situation, Task, Action, Result - a structure for answering behavioural questions. It works, but people often over-invest in Situation and Task and never reach a real decision. Framing the Action as a choice between two options, and splitting the Result into cost and gain, makes the same structure far more compelling.
Aim for 60-90 seconds. That's enough for the four beats - before, choice, cost, gain - without drifting into a full project recap. If you're over two minutes, you're almost certainly re-telling the situation instead of the turn.
Use the same four-beat shape and let the "gain" be what you learned. Pick a real failure with a clear decision in it, own the cost plainly, and show the specific habit or judgement it changed. Avoid fake failures ("I work too hard") - they read as evasive.
You don't need one. Interviewers are assessing how you think, not the scale of the project. A small, real moment with a genuine decision beats a large vague one every time. A two-person task with a clear trade-off is a great answer.
Prepare five "turns" - five real moments where you made a hard call - rather than memorising answers to specific questions. Five cover most behavioural prompts (conflict, failure, leadership, ambiguity, deadline pressure), and you match the question to the nearest one on the spot.
Real situations, before/after examples, and a quiz. Chapter 1 is free.
Open the course