Coachable gaps and the ones that are not

The idea

Every candidate arrives with something missing. The useful question is not is there a gap but does this gap move, how fast, and who pays for the moving.

Missing knowledge and missing reps usually move, as long as there is evidence the person has learned something hard before and can tell you how they knew they had learned it. Patterns of attribution, defensiveness and low self-awareness rarely move, because the person does not agree there is anything to fix.

And coachable is not free. A gap that closes in eighteen months is a decline for a role that needs it in three. Naming the weeks, the coach, and what the team gives up is the difference between a hiring decision and a wish.

Place the gap, then price it

How it works

1. Name the kind of gap. Knowledge — they were never told. Reps — they were told, they have not done it enough. Pattern — attribution, defensiveness, low self-awareness. Conditions — the format failed, not the person. Only the first two reliably move on hiring timelines.
2. Ask for the learning record, not the self-assessment. "What is the most recent hard thing you learned, and how did you know you had learned it?" The second half is the real question — it tests whether they have a way of checking themselves.
3. Probe stated growth areas with a scenario. Anyone can say "I need to work on communication." Put them in a situation that requires it and watch what actually happens.
4. Change one condition before you call it a working style. Same task, clock off, or sent asynchronously. A candidate who froze on a timed problem but reasoned cleanly untimed has told you something different from one who never got there.
5. Read the partial signal. Strong debugging instincts under a failed solution, or strong technical judgment with no reports — in both cases the missing thing is reps, not aptitude. Say which part worked.
6. Price it, then compare it to the runway. Weeks to competence, who does the coaching, what the team gives up meanwhile.

gap             never managed people
kind            missing reps (not aptitude)
evidence        held a quality line under pressure; gave hard
                feedback to a peer and named what changed after

coaching plan   weekly 1:1 with their manager        3 h/wk
                peer-manager buddy                   1 h/wk
                first hard conversation is coached, not delegated
time to a first competent performance cycle   ~30 weeks

--- role runway = 9 months -------------------------------
39 weeks available - 30 weeks needed = +9 weeks margin
margin is 23% of the runway  ->  closes, but tight
verdict: hire only if that manager has signed up by name

--- role runway = 3 months -------------------------------
13 weeks available - 30 weeks needed = -17 weeks
verdict: decline for THIS role. not a verdict on the person

The arithmetic is deliberately crude. Its job is to stop "coachable" from being a mood, and to force the two facts a debrief usually skips: by when, and at whose expense.

When to use it

This is a hiring tool, not a diagnosis. You are reading three hours of interview, not a person — so state your evidence and its limits in the same breath.

Watch out for

• "Coachable" used as a verdict instead of a plan. If nobody in the debrief can name the coach, the weeks, and what the team gives up, the word is doing no work. Ask "coachable by whom, by when?" and watch the room go quiet.
• Mistaking a rehearsed growth-area answer for self-awareness. "I can be too much of a perfectionist" is a script. The evidence is a scenario where the growth area is required and the behaviour changes in front of you.
• Calling interview-pressure performance a working style. Unless the job contains that exact clock, a timed collapse measures the format. Change one condition and re-measure before you write "struggles under pressure."
• Over-reading one defensive moment as a pattern. Look across three stories, and check whether your own questioning built the wall. A pattern is a person who cannot locate their own part in any account — not a person who bristled once at a badly framed question.
• Putting the coaching cost on a manager who is already full. The candidate does not pay this bill; the team does. Two coachable hires into the same manager is one uncoached hire and one exhausted manager.
• Confusing "I would enjoy learning that" with evidence. Enthusiasm is cheap and sincere. The learning record — most recent hard thing, and how they knew they had learned it — is the part that predicts.

Worked example

A staff engineer candidate for a platform team froze on the timed exercise: twelve minutes of silence, then a half-solution. The interviewer changed one condition and sent the same problem asynchronously. It came back with orderly reasoning, two tests, and a note naming her own earlier mistake. That gap moved from skill to conditions — and since the role has no live-coding clock in it, the gap is roughly two weeks of ordinary onboarding.

The second gap did not go the same way. She had named stakeholder communication as her growth area, so the next interviewer stopped accepting the self-report and ran a scenario: your project is six weeks late, explain it to the VP who promised the date. She recited the dependency failure, used three internal system names, and finished with "they didn't really have the context." No adjustment when the audience changed, and no story of having ever changed it before.

The debrief line was therefore not "great engineer, communication concerns." It was: the coding signal was a format artifact and we have the untimed evidence; the real gap is communication, we have no evidence it has ever moved, and this role presents to the exec staff in month two. Decline for this role — with a named reason, and an open door if she comes back with a different learning record.

Check yourself