Interview questions, by leadership principle

A behavioural prompt has a surface request and an underlying one. The surface request is for a story. The underlying one is for evidence about a specific principle that the interviewer has been assigned and will be writing up afterwards. Answering only the surface request produces a pleasant, well-told anecdote that scores nothing.

So the first move on hearing any question is to identify what it is fishing for. “Tell me about a time you disagreed with your manager” is not interested in the disagreement. It wants to know whether you can hold a position under authority and then commit properly after losing — and most of the scoring happens in the second half, which most candidates never reach because they spend their time proving they were right.

The same story can serve several principles depending on which part you foreground. That is the skill this page is built around: not having more stories, but knowing which face of a story to turn toward the question.

Structure exists so that an interviewer taking notes can follow you. Use it as scaffolding rather than as a recital — announcing “now the situation” reads as rehearsed and wastes the seconds you need elsewhere.

• Situation, compressed. Twenty to thirty seconds. Include the scope — team size, revenue, users, how many organisations — because scope is what makes everything after it legible at the right level.
• Action, expanded, in the first person. This is where the score is decided. Say what the team did, then say plainly what you personally decided. Describing your own work as “we” is generous and, in a written write-up, indistinguishable from not having done it.
• Result, against a baseline. A number with no starting point cannot be assessed. Give the movement, the timeframe, and how many people it touched.
• Reflection. What you would do differently. At senior level this is close to mandatory and is often the closing question anyway.

Two minutes is a good target for the initial answer. Under a minute reads as thin; past four you have stopped leaving room for the follow-ups, which is where the interviewer actually forms a view.

The opening answer is a prepared artifact and every interviewer knows it. What they are testing is what happens when they push past it. Probes escalate in a fairly predictable ladder, and knowing the shape lets you prepare depth rather than polish.

Prepare by having someone ask “why that rather than the obvious alternative” three times consecutively on your strongest story. The point where you start improvising is the point where your preparation actually ends, regardless of how good the first ninety seconds sounded.

Questions are not cleanly partitioned by principle. An interviewer assigned Deliver Results and Dive Deep will happily use a single question for both, starting with the outcome and then asking how a number was computed. Loops are designed with deliberate overlap so that the same claim gets tested from more than one angle.

Three practical consequences:

• Consistency is checked. The same story told to three interviewers is compared across three write-ups. Details that drift get noticed.
• Vary your material. Reusing one story across an entire loop reads as a thin career even when the story is strong. Plan which stories go to which rounds if you know the assignment; otherwise, keep a mental tally as you go.
• Answer the question asked. If you have decided in advance that a story is your Ownership story, you will bend an Earn Trust question toward it. Interviewers hear this immediately.

Four question types account for most of the difference between candidates who get an offer and candidates who interview well. They share a property: each requires you to be the person who was wrong, and each is easy to answer in a way that technically responds while giving the interviewer nothing.

• Tell me about a failureNeeds a named misjudgement, a real cost, and a change in your practice that stuck. Failures caused by circumstances, or that turned out fine anyway, are transparent and score worse than admitting you have not thought about it.
• Tell me about a conflictThe trap is proving you were right. What is being assessed is how you handled the other person, what you conceded, and whether the relationship survived.
• Tell me about feedback you receivedChoose feedback that was actually hard to hear. “I was told I care too much” is a non-answer and everyone recognises it.
• What would you do differently?Almost always asked, frequently last. Have a real answer per story. “Nothing, it worked out” closes on your weakest note.

A useful rule: for each of your core stories, write the version where you come out worst. If that version is unusable, the story is thinner than you think.

Product interviews are not only behavioural, but the non-behavioural rounds are still written up against principles. How you approach a product question is read as evidence just as directly as a story is.

The practical implication: think out loud, state your assumptions, and ask clarifying questions before designing. An interviewer cannot score reasoning they cannot hear, and a confident answer to the wrong question reads as a failure of Customer Obsession before it reads as anything else.

The questions you ask are scored too, and generic ones are a wasted slot. The useful ones reveal something you actually need in order to decide, and incidentally demonstrate that you understand the level you are interviewing for.

• What does this role own that nobody currently owns?
• What decision is the team getting wrong today that a strong hire would change?
• Where does this team's roadmap come from, and who can overrule it?
• What has been written down about this area recently that I should read?
• What would make you regret this hire in a year?
• Which of the principles does this team find hardest in practice?

Avoid asking anything answerable from the job posting, and avoid compensation and levelling in a loop round — those belong with your recruiter, who is the person actually able to move them.

1. Inventory before you look at the list. Write out everything significant you have done in the last five or six years. Starting from the principles produces manufactured stories.
2. Map stories to principles and find the empty rows. Expect gaps at the two newest principles and at Frugality.
3. Write each story in full prose. Not bullets. Writing exposes the details you do not actually remember — which is precisely what the fourth follow-up will find.
4. Reconstruct the numbers. Baseline, delta, timeframe, definition of the metric.
5. Rehearse probes, not answers. Have someone drill one story four levels deep. Where you run out is where the real preparation starts.
6. Record yourself once. Painful and unusually efficient. Count how often you say “we”.
7. Do a full mock in one sitting. Loops are long, and fatigue changes answers more than most candidates expect.

Preparation past a certain point stops helping. The candidates who do best are not the ones with the most polished stories — they are the ones who can stay specific and honest under a fourth follow-up, which is a property of having done the work rather than of having rehearsed the telling.