What makes an example too trivial or too overused to tell a behavioral interviewer?

## Two different defects, often confused 'Too trivial' and 'too overused' feel like the same complaint but fail for different reasons, and the fixes differ. **Trivial** means the story contains no decision worth scoring. Something happened, you did the expected thing, it resolved. The listener has nothing to write down because nothing turned on you. **Overused** means the story contains a decision, but it is the same decision the listener has heard in the preceding several conversations. The evidence is real and its differentiating value is near zero. ## The counterfactual test for triviality Ask: if a reasonably competent peer had been in that seat, what would have gone differently? If the honest answer is 'nothing much', the story is trivial no matter how urgent it felt at the time. A page fires, the runbook says to shift traffic away from the affected tier, you shift traffic away, the graphs recover. That is a good on-call shift and a dead behavioral answer, because the whole content is compliance with an instruction someone else wrote. The same experience becomes tellable at the exact point where the script ran out — when the runbook's step did not apply, when two of its instructions conflicted, when you decided to deviate and could name why. That is where the counterfactual opens up, and it is usually a small moment inside a big incident rather than the incident itself. A useful sharpening question: what was the *other* option, and who would have chosen it? A story with no plausible alternative path is a report, not an answer. ## The substitution test for overuse Ask: could most candidates interviewing for this role tell this story with their own nouns swapped in? A handful of experiences are near-universal in infrastructure work — the flaky check that was quarantined, the alert threshold that was too noisy, the colleague who was unresponsive on chat until you walked over, the ticket that turned out to be someone else's config. These are true, they are relevant, and they are so widely shared that they cannot separate you from the field. A behavioral interviewer running many conversations has heard each of them several times, and their scorecard has no room for 'told the usual one, told it well'. Overused material is not worthless, though. It works as supporting detail — a clause inside a larger story that establishes context — and it works as a fallback when a prompt catches you with nothing better. What it cannot do is carry the answer. ## Distinguishing small from trivial Size and triviality are independent, and confusing them causes real damage in both directions. A small, quiet decision can be excellent: choosing to hold a cutover for one more day against pressure, and being able to say what you saw that others had not, is a strong ambiguity answer even though nothing burned. Conversely, an enormous incident can be entirely trivial as evidence if your role in it was to execute someone else's plan competently. So the filter is not 'was this big?' but 'was there a contested call, and was it mine?' The clean test is whether the story contains a sentence of the form 'I chose X over Y because Z' where Y was genuinely available. ## Where the drama reflex fits The two defects interact badly with the instinct to reach for the most dramatic thing you own. Dramatic incidents are frequently trivial as evidence, precisely because a real crisis is the situation where procedure takes over and individual judgment is deliberately constrained. Meanwhile the quiet, unglamorous decision — the one you would never volunteer at a dinner party — is often where the contested call actually lives. Candidates who filter by excitement systematically discard their best material. ## Running the filter before the loop Go through your prepared experiences once, against the handful of themes that recur — ambiguity, conflict, failure, leadership, deadline pressure — and mark each one twice: does it survive the counterfactual test, and does it survive the substitution test? Anything failing the first gets rewritten to start at the moment the script ran out. Anything failing only the second gets demoted to supporting detail. What is left is thinner than what you started with, and every remaining item earns its airtime. One caution when applying this: a story is not overused merely because *you* are bored of it. You have told it many more times than any single listener has heard it, and familiarity fatigue makes candidates abandon strong material for weaker novelty. Judge overuse by how common the situation is in the field, not by how tired you are of your own sentences.