Senior behavioral rounds, bar raiser rounds especially, share one technique: recursive probing. You tell your strongest story. The interviewer picks a decision inside it and asks why. You answer. They ask why again. Three or four layers down, one of two things is exposed: bedrock (you actually understood what you were doing) or air (the story was a rehearsed surface over borrowed reasoning). The method exists because first-layer answers can be prepared, but third-layer answers can only be known.
What the layers look like
Take a story about migrating a service to event-driven architecture.
Layer 1: "Why did you migrate?" "The synchronous chain was fragile; one slow dependency took down checkout." Any prepared candidate clears this.
Layer 2: "Why events rather than just adding timeouts and fallbacks?" Now you need the actual analysis: what fallbacks would and wouldn't have bought you, why decoupling was worth the operational cost. Candidates who inherited the decision start hedging here.
Layer 3: "You said ordering mattered for inventory events — why was partial ordering acceptable for payments then?" This is only answerable if you personally wrestled the details. Bedrock, or air.
The interviewer isn't being hostile. They're amplifying signal. A story that survives layer three is worth ten stories that were never tested.
How to prepare for recursion
Interrogate your own stories first. For each core story, play the skeptic. Why that option? What were the alternatives, really? What would have happened with the naive approach? Which constraint actually drove the call? If you find a decision you can't defend, one that was made above you or that you've never questioned, know that before the loop.
"I don't know" and "that wasn't my call" are power moves at depth. When probing reaches a genuine boundary, a decision your architect made or a number you never measured, say so plainly: "Honestly, that predated me; my piece started at the rollout design." Bar raisers report this as positive signal, because it proves the rest of your claims are load-bearing. What fails is improvising authority you didn't have. Layer four is coming.
Distinguish reasons from rationalizations. Under recursive pressure, candidates drift into justifying decisions with arguments they've clearly constructed after the fact. The tell is fluency without specifics. The antidote is anchoring each "why" in what you knew at the time: "at that point we'd had two incidents traced to the sync chain, so the fragility argument had data behind it."
The honest failure question is the same test
"Tell me about a failure" plus three whys is the bar raiser's favorite recursion, because failure stories are where candidates most reliably hold something back. The layers go: what failed, why did it fail, why didn't you catch it earlier, and what does that say about how you work? Prepare your failure story to that fourth layer, the one where the answer is a real change in your own behavior, and you'll be ahead of nearly everyone in the pipeline.
Stories don't need to be impressive to survive recursion. They need to be yours, all the way down.