Gaps, your questions and after the round

It will happen. There are nine competencies and you will not have strong material for all of them, and the way you handle the gap is itself scored.

This lesson covers the three moments of a loop that candidates prepare least: the question you have no story for, the last ten minutes when you ask the questions, and the hours after the round — the note, the self-debrief and the wait. All three are still being scored or still shaping the next loop.

The three options, ranked

1. The honest adjacent answer. Best. You name the gap, then offer the closest real thing.

"I haven't managed anyone formally, so I don't have a performance-conversation story. The closest thing I have is a peer feedback conversation that was genuinely hard — I had to tell someone I worked with daily that their review comments were landing as dismissive. Is that useful, or would you rather I reason through how I'd approach the management version?"

That answer does three things: it is honest, it produces real evidence, and it offers the interviewer a choice. Interviewers routinely take the second option, and reasoning aloud about a situation you have not faced scores real credit when it is clearly labelled.

2. The reasoned hypothetical, labelled. Second best, and fine on its own when you have nothing adjacent.

"I've not faced that. Can I tell you how I'd think about it, and you can push on the reasoning? The first thing I'd want to know is —"

The labelling is the whole thing. An unlabelled hypothetical told as a real story is fabrication; a labelled one is a legitimate exercise in judgement.

3. The partial answer with the gap named. Sometimes you have half.

"I have the first half of that — I've had the disagreement, and I have not been in the situation where it escalated past my manager. Here's the half I have."

Why fabrication is the worst option

It is worse than the gap by a wide margin, and it fails for a mechanical reason: an invented story has no second layer. The first follow-up is "what did they say?" and the second is "why do you think they took that position?", and invented answers to those get vaguer while real ones get more specific. Anti-patterns and a worked example in Section 8 describes exactly what the interviewer sees.

The cost asymmetry is severe. A missing story is one unfilled rubric row, which for most competencies at most levels is neutral or mildly negative. A story that collapses under follow-ups is recorded as a credibility concern, and a credibility concern re-opens every other answer you gave.

Preparing the gaps in advance

You know your empty columns from the coverage matrix in Building the story bank. For each one, write two sentences now:

1. The honest framing of the gap: "I've not had a formal report, so —"
2. The adjacent evidence, or the reasoning you would offer instead.

Twenty minutes of work, and it converts the worst moment in a loop into a prepared one.

Your questions for the interviewer

The last ten minutes produce information you need, and they are still being scored — most interviewers write a line about what you asked.

What good questions do simultaneously

A strong question is useful to you and signals something about how you work. The two goals are not in tension; questions that are genuinely useful to a candidate tend to be the ones that signal seniority, because both come from thinking about the actual job.

Questions that work

About the work, specifically:

• "What's the thing the team is working on now that's hardest to get right?"
• "What's on the roadmap that you're least confident about?"
• "If I joined and did well for six months, what would be different?"

About how decisions get made:

• "Walk me through how a technical decision that affects two teams gets made here."
• "When was the last time a plan changed significantly? What drove it?"

About the honest state of things:

• "What's the most frustrating part of working here that you'd want a candidate to know?"
• "What's something the team has tried that didn't work?"

Role-specific, at senior and above:

• "What would you want the first thing I own to be, and why that?"
• "Where does this team's work stop and another team's start? Where is that boundary uncomfortable?"

Questions that read as filler

Two questions worth asking every interviewer

"What's your read on the biggest risk to this team hitting its goals this year?" Different interviewers give different answers, and comparing them across a loop tells you more about the organisation than anything on their website. Three people naming the same risk is a real signal; three naming different ones is also a signal.

"Is there anything about my background that gives you doubt?" This one is uncomfortable and it is the single highest-value question available. It gives you a chance to address a concern before the debrief, and the concern is otherwise unaddressable because you will never hear it.

The answer is often specific and useful — "you've not worked at this scale" — and thirty seconds of honest response can change a write-up.

After the round

Three things: the note, the self-debrief, and the wait. The middle one is the one that compounds.

The follow-up note

Send it within 24 hours, to the recruiter, asking them to pass it on. Short.

What it is for: a small positive signal, and one chance to add something you fumbled.

What it is not for: re-arguing a technical point at length, or a paragraph of enthusiasm.

A usable template:

Thanks for the time today. Two things I wanted to add.

On the question about the reconciliation cutover — I gave you the fifty-five-minute figure but not how it was measured. It was the job's own duration metric in Grafana, median across the two weeks after cutover, and the before figure was the median of the preceding month.

And the boundary question we ran out of time on: the piece I'd have added is that we moved retry handling to our side precisely because we were the team with the headcount to own it.

Enjoyed the conversation about the shim design in particular. Happy to go deeper on any of it.

Three short paragraphs, one of which adds real evidence. That is the maximum useful length.

The self-debrief

Do this within two hours, while you can still remember the wording. Twenty minutes, and it is the highest-return activity in the whole course if you have more than one loop.

Write down:

1. Every question you were asked, as close to verbatim as you can. This becomes your question bank, and it is far more accurate than any list you will find.
2. Which story you used for each, and whether it was the right one.
3. Every follow-up that caught you. These are your gaps, identified for free.
4. The two answers you would give differently, and what you would say instead.
5. What the interviewer seemed to write most. You noticed at the time; write it down before you forget.

After three loops this document is better preparation material than anything you can buy, because it is your questions, your gaps, and your phrasings.

Handling the wait

Two practical points.

Ask the recruiter for a timeline and then respect it. "What's the expected timeline for a decision?" at the end of the loop. If the date passes by more than a few days, one polite check-in is appropriate; a second one within the same week is not.

Keep the pipeline running. Do not stop interviewing elsewhere because one loop went well. Beyond the obvious risk management, having another process live changes how you negotiate, and it changes how the wait feels.

If you are rejected

Ask for feedback once, specifically, through the recruiter:

"I'd appreciate any specific feedback, particularly on the behavioral rounds — even one line about the competency where I was weakest would help me."

Many companies will not give it, for reasons that are about policy rather than about you. Some will, and one line is often enough to identify a pattern. Either way, your own self-debrief is the more reliable source.