Sample

This is the marked card.

An example of the full breakdown: score, deeper analysis, the gap, the evidence behind it, and how you’d track progress Run over run. Every paid session ends with one, built from your own interview. Tap the card to flip it.

Senior Programme Manager

neutral

aurate

Competent

74/100

The tick is 60 — where Competent begins

Fit

At the bar

Dimensions

logic81
resilience70
synthesis74
specificity68

Marked: weakest

Run over run4 sessions

Marked independently. Same dimensions, same scale, every time.

In short

Priya, your instinct for holding a complex delivery together — and keeping the people behind it onside when priorities collided — was the strongest thing in the room. Where it thinned was proof: the projects landed, but you told the story of the outcome without the number that would have made it land.

The gap

You told the story of the delivery but never the size of it. "It went well and the sponsor was happy" lands far harder as "we shipped three weeks early, 12% under budget, and adoption hit 80% in the first month" — and in the room you reached for the adjective, not the number.

What’s working

You run a delivery the way a strong programme lead does — from the outcome and the stakeholders backwards, holding the line when scope, time and budget pulled against each other, even on calls that sat above your remit. That judgement is the hardest part to teach, and you already have it.

Next step

Before your next session, Priya, pin your three best deliveries to one number each — days early or late, over or under budget, scope held, value realised. Lead with the outcome, name the number, then the how.

How we scored this

5-Band Coaching Vocabulary

Exceptional · 75–100: Clear mastery with specific examples that exceed expectations for the stated level.
Competent · 60–74: Solid, structured responses with relevant content — meets the bar for the level.
Developing · 45–59: Engaged meaningfully but answers lacked depth, specificity, or structure.
Building · 30–44: Significant gaps yet — vague, unfocused, or struggled to provide relevant examples. The shape of a next step is clear.
Early Foundations · 0–29: Did not yet demonstrate this dimension — the next interview is the moment to practise.

Sub-Score Axes

logic · 81: Reasoning was structured and outcome-first — you traced each delivery decision back to the risk it managed, and the logic held when the panel pushed on whose call it was.
Analytical reasoning, framework articulation, structural thinking. Higher when answers connect cleanly to the role context.
resilience · 70: You held composure under direct challenge and conceded valid points gracefully rather than defending a weak position; only the opening beat of the pressure moments wobbled, spent re-explaining the governance.
Performance under stress, recovery from pressure, hostile-persona handling. Weighted on the grill segment when present.
synthesis · 74: You connected delivery risk, stakeholder impact, and the programme outcome into one coherent story; the room to grow is the reverse-inquisition close, where the influence narrative could land sharper.
Connecting evidence, fit-gap articulation, cross-theme integration. Higher when answers reference prior moments.
specificity · 68: The single trailing axis: real deliveries described qualitatively. You hold the numbers — you quoted a budget variance unprompted — but defaulted to the adjective under pressure. One quantified outcome per delivery closes most of the gap.
How concretely you backed claims — specific examples, names, numbers, and real situations vs generalities.

Senior Programme Manager

Session 4 · neutral

aurate

What’s working

It wasn’t my programme to re-plan, but I was the one seeing the dependency slip on every stand-up — so I pushed to re-sequence the two workstreams before the integration date became impossible.Segment 1

Owned the delivery risk and acted on it before it became a crisis, without waiting for permission — a programme-lead instinct.

I didn’t have the authority to move the date, so I brought the three teams who’d be blocked into one room and let them hear the dependency for themselves. The evidence made the case I couldn’t make on title alone.Segment 4

Influence without authority done the right way — moved a delivery decision with evidence rather than escalation.

The gap in full

The delivery was there; the proof wasn’t. On three separate answers you described a real outcome — "it went smoothly", "the sponsor was delighted", "we got it over the line" — and stopped exactly where a hiring panel leans in. You clearly TRACK the numbers (you quoted a budget variance unprompted early on), so this is a packaging habit, not a gap in the work: under question pressure you defaulted to the narrative and left the metric on the table. For someone stepping up to programme level — trusted with bigger budgets and harder benefits cases — that is the most expensive habit, because the quantified version is what tells a sceptical panel the delivery instinct is real and repeatable, not just a good story.

The migration went really smoothly in the end — honestly the team pulled together and the sponsor was delighted with how it landed.Segment 2

A real, defensible delivery described with adjectives ("smoothly", "delighted") where one number would have closed it.

We prioritised the integration work because it was clearly the highest-risk thing in the programme, and it paid off.Segment 3

"Highest-risk" and "paid off" are claims, not evidence — the metric that proved the call never surfaced.

Quantify the delivery

The migration went really smoothly in the end — honestly the team pulled together and the sponsor was delighted with how it landed.

Every strong delivery story landed one number short. Panels read a quantified outcome as proof and a qualitative one as a pitch — and at programme level the quantified version is what makes the delivery instinct believable rather than aspirational.

Say insteadTake your three best deliveries and write the single number each one moved — days early/late, % over/under budget, scope retained, benefit realised. Rehearse each as "We delivered X, here’s how" until the number arrives before the narrative.

Lead with the outcome

So there were a few moving parts in the programme that quarter, and to explain why we sequenced it the way we did, I should start with…

You opened most answers with context — the situation, the constraints, the governance — and reached the actual result last. Under panel pressure the buried outcome reads as hesitation even when the delivery was sharp.

Say insteadOpen with the result: "We delivered the integration three weeks early." Then the how. Practise stating the outcome in your first sentence and adding context only when asked — let the panel pull the detail.

Own the call you drove

I guess in the end the teams came round to it, so it sort of became the plan.

When a decision wasn’t formally yours, you hedged the ownership ("the team decided", "we ended up"). The judgement was yours; the language gave it away. At programme level, claiming the call you actually drove is the signal.

Say insteadReplace "we ended up" with "I argued for, and here’s what changed". Name your specific contribution to a shared decision — panels are scoring what YOU drove, not what the programme concluded.

Fit

On substance you are closer to the senior-programme bar than your current title suggests — the outcome-first delivery thinking, the comfort re-sequencing work under pressure, and the instinct to influence across teams without authority are all genuinely there, and they held under questioning. The gap is not delivery judgement, it is evidence: you deliver at the level the step-up demands but quantify a rung below it — in outcomes felt rather than outcomes measured. That is a coachable, weeks-not-years gap — and closing it is what turns a credible step-up story into an obvious one.

Theme coverage

Delivery judgement & decision-making

You anchored the call on the delivery risk and the teams it affected, reasoning from the outcome backwards rather than from the plan-on-paper. That outcome-first framing is the clearest programme-lead signal in the session and reads as real judgement, not borrowed governance vocabulary.

Next timePush you on a call with no obvious risk signal to lean on — a pure trade-off under ambiguity — to see whether the judgement holds without the delivery proximity.

Quantifying delivery impact

This is where the gap surfaced. You described real outcomes — a smooth migration, a delighted sponsor — but in qualitative terms, stopping exactly where a panel wants the number. You clearly hold the data (you quoted a budget variance unprompted), so it is a packaging habit, not a gap in the work.

Next timeForce the metric: ask "by how much, and how did you know?" on every claim until quantifying becomes the reflex.

Prioritisation under constraint

Your prioritisation instinct was sound — you sequenced the highest-risk work first for defensible reasons — but the answer opened with context and reached the decision last, and the "highest-risk" claim arrived without the metric that would have justified it.

Next timeImpose a 60-second cap to force the decision to the front, then ask for the prioritisation logic explicitly.

Influence without authority

You moved a decision you had no formal authority over by bringing the evidence directly to the teams it affected — the right mechanism, and exactly the question’s target. The only soft spot was ownership language: you let the outcome become "the teams’" when you had clearly driven it.

Next timeTest a case where the evidence is contested, not just unheard — does the influence approach hold when the room pushes back?

Under pressure

What held

When the panel pressed on whether a story was enough to justify the decision, you didn’t dig in — you agreed the evidence should have been quantified and said so plainly. Updating your position under pressure without losing the thread is poise, and it is one of the strongest things you did all session.

What surfaced

The first beat of each high-pressure answer went to re-explaining the governance before engaging the actual challenge — it reads as buying time. Replace that reflex with a single sharp clarifying question: it buys the same beat but reads as control rather than hesitation.

The moment

Fair challenge — honestly, if I’d had the benefit number in front of me at the time I’d have led with it, because the story alone shouldn’t have been enough to justify moving the date.Segment 5

Conceded a valid point without becoming defensive and named her own gap out loud — poise under direct challenge.

Evidence to reuse

For the real interview, not the next session.

The dependency re-sequencing push — a clean example of protecting a delivery you didn’t own, on evidence. Reuse it whenever you’re asked about influence without authority; just add the days-saved number.
Getting three blocked teams into one room to make the case governance couldn’t make for you — a strong, repeatable "influence with evidence" story.
The budget-variance figure you quoted unprompted early on — proof you DO carry the numbers. Pull that habit forward into every outcome you describe.
Framing the re-plan around the integration risk rather than the plan-on-paper — a textbook outcome-first opening; keep it.
Your stand-up instinct for where delivery was actually slipping — name it explicitly as the source of your programme judgement; it’s the backbone of your step-up story.

Run over run

Session 4

What next

Start your prep

Why it’s built this way

One gap, not a list.: A list of ten things to fix is a list nobody acts on. The card names the single change that would move your score most, and everything else waits until you’ve made it.
Something you already do well.: Not encouragement. The gap is what to change; this is what not to break while you change it.
The evidence is your own words.: Every judgement on the card points back at something you actually said in the session. Nothing is inferred from your CV or your profile.
The same four dimensions, every session.: So your second card is comparable to your first, and the movement between them means something. The standard is on the card, so you can check the mark rather than take it on trust.
Run over run.: One score tells you where you stand. Four tell you whether the preparation is working, which is the thing you actually want to know.

Want one of your own? Try live Five minutes, free, and you’ll get a smaller version of this.

Start your prep — the full interview, and a card like this at the end.