This is the full Vibe Card.
An example of the complete Autopsy — score, deeper analysis, your Biggest 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.
aurate vibe card
“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.”
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.
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.
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.
5-Band Coaching Vocabulary
- [75–100]Exceptional.Clear mastery with specific examples that exceed expectations for the stated level.
- [60–74]Competent.Solid, structured responses with relevant content — meets the bar for the level.
- [45–59]Developing.Engaged meaningfully but answers lacked depth, specificity, or structure.
- [30–44]Building.Significant gaps yet — vague, unfocused, or struggled to provide relevant examples. The shape of a next step is clear.
- [0–29]Early Foundations.Did not yet demonstrate this dimension — the next interview is the moment to practise.
Sub-Score Axes
- logic — 81Analytical reasoning, framework articulation, structural thinking. Higher when answers connect cleanly to the role context.
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.
- resilience — 70Performance under stress, recovery from pressure, hostile-persona handling. Weighted on the grill segment when present.
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.
- synthesis — 74Connecting evidence, fit-gap articulation, cross-theme integration. Higher when answers reference prior moments.
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.
- specificity — 68How concretely you backed claims — specific examples, names, numbers, and real situations vs generalities.
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.
Theme Coverage
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 anglePush 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.
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 angleForce the metric: ask "by how much, and how did you know?" on every claim until quantifying becomes the reflex.
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 angleImpose a 60-second cap to force the decision to the front, then ask for the prioritisation logic explicitly.
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 angleTest a case where the evidence is contested, not just unheard — does the influence approach hold when the room pushes back?
Strongest Signal
Asked about a decision you pushed for that wasn’t yours to make, you didn’t reach for process language — RAID logs, governance, who signed off. You went straight to the delivery: what was actually at risk, who it affected, and the smallest change that protected the outcome. That is the programme-lead move — owning the result rather than the plan — and it is exactly the muscle four years of programme delivery built. You have spent those years closest to where delivery actually breaks; under questioning that proximity reads as genuine programme judgement, not borrowed governance vocabulary. And you held it under pressure: when challenged on overriding the original plan, you didn’t retreat to "it wasn’t my call" — you restated the risk and let the decision stand.
Biggest Gap
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.
Fit Assessment
supports target role
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.
Grill Segment
partially held
Strength under stress: 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.
Vulnerability 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.
Improvement Areas (3)
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.
Concrete suggestion: Take 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.
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.
Concrete suggestion: Open 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.
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.
Concrete suggestion: Replace "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.
Notable Evidence To Reuse
- ◆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
+3pts vs prior best (4 runs)
Session 4
Next Run Brief
- →Force the metric: ask "by how much, and how did you know?" on every claim until quantifying becomes the reflex.
- →Take 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