Learn
Your story spent two minutes on the background and twenty seconds on you
"Tell me about a time you made a call without all the information." You know the story, so you start at the beginning: the company, the team, how the system came to be built that way. Somewhere in the second minute the interviewer says "and what did you do?" You have not reached your part yet.
The situation
Most preparation advice teaches four boxes: situation, task, action, result. The trouble is that the first box feels safe. You know the background, it cannot be wrong, and it postpones the part where you are judged. So it grows.
The interviewer, meanwhile, is listening for one thing: what you decided and what happened because of it. Background earns its place only where the decision makes no sense without it. Everything else spends the minutes they wanted for your reasoning.
A candidate wrote on DEV earlier this year that, after a lost onsite, the recruiter's debrief called their answers "rehearsed and shallow". Their own conclusion was to stop trying to complete every box and tell the story. A long situation box is one easy way to fill a box the story did not need.
What goes wrong
Here is an invented answer of the kind that runs out of time:
So I was at an online grocery company, about two hundred engineers. I was on the search team, six of us. Search had been built on a nightly reindex years before I joined, because originally prices only changed once a week. Then pricing moved to its own service, owned by another team in a different office, and they started changing prices several times a day. We had tickets about slow search, and a cluster migration was planned for next quarter. Anyway, one morning support told us some customers saw one price in search and paid another at checkout.
That is about forty seconds read calmly, and the problem has only just appeared. With nerves and asides it is easily a minute and a half. Now try each sentence against one question: does my decision make sense without it? Company size, team size, slow-search tickets, the migration: all fail. Only two facts survive: the index refreshed overnight, and prices now changed during the day.
Here is the same story with the setup cut to what the decision needs:
Last March, customers sometimes saw one price in product search and were charged another at checkout, because our search index refreshed overnight and prices now changed during the day. I owned the indexer. A faster reindex would take weeks, so I proposed a smaller change: search results stop trusting the index for price and ask the pricing service for the twenty items on screen. That made the results page slower, roughly eighty milliseconds on our dashboards, and I agreed the trade with the product owner before shipping. Support stopped receiving price-mismatch tickets, and the reindex work went ahead in the following quarter.
The decision now arrives in the third sentence, and the interviewer has the stake, your role, the option you turned down, the cost and the effect, with time left to ask about any of them.
What to say out loud
Open with the stake and your role in one breath: "Last March, customers were charged a different price from the one search showed them, and I owned the indexer." Now they know what was at risk and why the call was yours.
If the setup really is complicated, say that you are shortening it: "The short version of the setup is that the index refreshed overnight and prices did not wait." Then offer the rest: "I can say more about how it was built, if that helps." Most interviewers will say no, and the ones who say yes now asked for it.
A minute in and still describing the system? Switch: "Let me get to what I did."
If the interviewer cuts in with "so what did you do?", treat it as information, not rudeness, and give your decision in the next sentence.
The exercise
- Pick one story you would use for a question about a judgement call. Tell it aloud for two minutes and record it.
- Play it back and note the second at which you first say "I" followed by a decision in the past tense: chose, proposed, refused, rolled back. Write that time down.
- Write out every sentence before that point. Strike each one your decision still makes sense without. Keep the struck sentences on a separate list as material for follow-up questions.
- Rewrite the opening as at most two sentences: when it happened, what was at stake, and your role. Retell the story from there and note the time of the first decision again. Aim for inside thirty seconds.
- In three days, retell it without notes. If the background has crept back, read your struck list once and tell it again.
Where this fits in Gadfly
Gadfly has four rooms: algorithms, system design, behavioral and code review. The behavioral room keeps a bank of your stories, separates the competencies a story claims from the ones it actually earns, and asks you to retell a story later, as in the last step above. Its report is a set of observations made by rules over what you said, not a hiring prediction.
Published 20 November 2026 · Behavioral: your part of the story · all notes · feed
This note was drafted by Gadfly's scout — an automated writing agent run by Dmytro Hryshchenko — and checked by rules against the product's claims registry, not read by a person before it went live. The exercise is original. Spotted a mistake? [email protected].