Behavioral interview scoring often turns on what your story leaves out. When a story has a gap, the interviewer fills it. They rarely fill it in your favor. The gap that costs the most is usually another person or team you never explain. Say “they kept changing the API without telling us” and stop there. You sound like the only reasonable person in the room. So prepare for the follow-up, not just the story. For every person who caused friction, have a plain answer to one question. What was going on for them? Then say what you changed so it wouldn’t happen again. That answer shows judgment about people you don’t control. That’s what collaboration rubrics are built to find. Below is one cross-team Android story told two ways. The first leaves the gap open. The second closes it. Then we walk through why that version scores better.
Why gaps get filled against you
Austen McDonald is a former Meta hiring committee chair. He now sells coaching and a book on behavioral rounds. In an April 2026 post, he warns that interviewers fill narrative gaps with the unfavorable assumption. His post is about AI stories. But the mechanic isn’t specific to AI. An interviewer has about 45 minutes and has to write a score. Anything you leave unexplained, they have to guess.
McDonald also reports that Meta’s rubric now has a “Partnering” area, covering how you handle disagreement with colleagues. That’s one company, reported secondhand. But most engineering loops probe collaboration in some form.
The example: a backend change that broke the release
Say the question is “tell me about a time you worked with a difficult team.” Here’s the version most candidates give.
We were two days from an Android release when checkout started crashing. The payments team had renamed a field in their API response without telling us. We lost two weeks fixing and retesting. They kept doing things like that, so I pushed hard for them to communicate better.
Nothing in that story is false. But the payments team is only an obstacle in it. An interviewer will ask the obvious follow-up. What caused that on their end?
If you haven’t thought about it, you’ll reach for “they just didn’t care about mobile.” That’s the gap closing against you.
The same story with the gap closed
Here’s the same event, told by someone who prepared for the follow-up.
We were two days from an Android release when checkout started crashing. The payments team had renamed a field in their API response. The web client shipped from the same repo, so they updated it in the same change. Nothing in their process knew the Android app existed as a consumer.
So it wasn’t carelessness. They had a web deadline and no signal that mobile would break. Old app versions also stay installed for months. Web never has to think about that.
I fixed the crash first, then met with their lead. We added a contract test in their pipeline that runs against our parsing models. I also joined their API review list. After that, breaking changes went to a new versioned field instead.
The release still slipped two weeks. What I’d do earlier next time is ask every backend team who owns the mobile contract.
The details are illustrative, so use your own. The shape is what matters.
What behavioral interview scoring rewards in the second version
The second paragraph answers the follow-up before it’s asked. The payments team gets a plausible reason that isn’t hostile. The candidate still says the change broke them. They just don’t treat the other team’s motive as obvious.
The third paragraph moves from frustration to a fix. The contract test and the review list are concrete. An interviewer can probe either one and get a real answer.
The last paragraph keeps the cost honest. The release still slipped. The candidate names what they’d change about their own behavior, not the other team’s.
Notice what the second version doesn’t do. It doesn’t defend the payments team or pretend there was no problem. Over-explaining reads as rehearsed. It just closes the one gap an interviewer would otherwise fill.
Other gaps to close in the same story
The other team isn’t the only gap. Look at the first version again. “We lost two weeks” invites a question about why it took that long. “I pushed hard” invites a question about what pushing looked like. Each vague phrase is a spot where the interviewer has to guess.
You don’t need to explain every detail up front. You need a ready answer for each one.
What to prepare
Take each story you plan to tell and mark three things.
- Every person or team who caused friction. Write one line on what was going on for them.
- Every vague phrase like “two weeks” or “pushed hard.” Write what actually happened.
- The change you made afterward. It should be about your behavior, not theirs.
Sometimes the honest answer is that the other team just dropped the ball. That’s fine to say, briefly. Then spend your time on what you did about it. For more on the probes that follow, see our post on behavioral interview follow-up questions.