The answer clock
Pick the format you're in. The bands rescale to the time you actually have — the shape stays the same, only the budget changes. Press Start and talk out loud; the playhead shows where you should be, not where you are.
Why this shape
Answer first, evidence second
Interviewers decide whether you're answering the question in the first ten seconds. Narrative order ("so back in 2019 we had this vendor…") spends that window on setup. Lead with the conclusion, then earn it.
Context is a tax, not a gift
Give only the context that makes the decision hard. Team size, regulator, deadline, the constraint you couldn't move. Everything else is detail you find interesting and they don't.
Stop early, on purpose
Ending 15 seconds under budget with a clean hand-back reads as executive control. Running 40 seconds over reads as someone who won't be manageable in a board meeting.
Read the room
The same question means different things depending on who's asking. Before the call, write down each interviewer's title and what that title is accountable for — that's the need your answer has to service. Their unspoken question is almost always about their own week getting better or worse.
Three questions to answer before you join the call
What is this hire supposed to fix?
Open roles exist because something broke, someone left, or an auditor/regulator/customer applied pressure. Find the trigger from the job description's oddly specific line — that line is the real requirement.
Who gets blamed if it stays broken?
That person is your sponsor, whether or not they're on the panel. Aim your proof at their exposure.
What's the cheapest reason to say no to me?
Too consultative, too technical, too senior, too regulated-industry, too long out of a big-company seat. Name it yourself in one clause, early, then move past it. Unnamed doubts grow.
Question decoder
Every common question has a surface form and a real need. Answer the surface form and you sound fine and forgettable; answer the real need and you sound like the person they've been describing to each other. Expand any question for the underlying worry, the usual failure, and a timed skeleton.
Live signals
You get feedback in real time; most candidates are too deep in their own answer to catch it. These are the tells and what each one is asking you to do differently — in the next sentence, not the next answer.
| What they do | What it means | Your move, immediately |
|---|
Two habits that buy you information
Scope the question before you spend 90 seconds on it
One short clarifier, not a stalling one: "Happy to go into either the program build or the incident side — which is more useful?" You get the real need handed to you, and it reads as consultative rather than uncertain. Use this at most twice per interview.
Hand back at the end
Close with "That's the short version — want the regulatory detail or the org detail?" It ends the answer cleanly, proves you have depth in reserve, and lets them steer instead of politely enduring.
Repair moves
Nothing here is a rescue for a bad interview. These are the small, unglamorous saves that stop one weak moment from setting the tone for the remaining forty minutes.
Prep locker
Everything you've written in the decoder, in one place. Saved in this browser only. Export before an interview and read the headlines — not the full answers — in the ten minutes beforehand.