Engineering Leadership · Chapter 8 of 9
The leadership interview, round by round
What each stage is actually testing, and the stories to prepare.
Leadership loops look conversational and are not. Each round is testing something specific, and knowing which lets you choose the right story rather than the most impressive one.
| Round | What it is really testing | The story to bring |
|---|---|---|
| Hiring manager | Scope — what you owned versus influenced | A number you were accountable for, and its trend |
| People management | Whether you can do the unpleasant half | Someone you grew, someone you managed out, and one you got wrong |
| Technical depth | Whether your engineers will respect you | Something you shipped recently, in real detail |
| Org / strategy | Whether you think in systems or in tasks | An org design you changed, and what it did to delivery |
| Cross-functional | Whether you can be disagreed with | A conflict with product or another org, resolved without escalation |
| Executive | Whether you can be trusted in front of the board | A bad-news conversation you handled early |
The five stories to have ready
- An outcome you owned — with a number, a baseline and a trend.
- A person decision you got wrong — a hire or a promotion — and what you changed about your own judgement.
- Something you stopped, and what it cost you.
- A disagreement you lost, handled well. Leaders who have never been overruled are not proposing anything contested.
- A decision made with insufficient information, and how you bounded the risk.
The thing that separates strong leadership candidates
Specificity about people. Weak answers describe process — ‘I gave regular feedback and set clear expectations’. Strong answers describe a person, a diagnosis, a decision, and an admission that the first read was wrong.
Interviewers at this level have all managed people badly at some point. They are listening for someone who has learned from it, not someone who has never done it.
What each round is really asking
| Round | The question behind it | What a strong answer contains |
|---|---|---|
| People / team building | Can you build and keep a team, and do people follow you back? | Specific people who grew, someone you managed out fairly, a hire you got wrong and what you changed |
| Technical depth | Can you still tell a good technical argument from a bad one? | Judgement, not currency. Nobody expects you to have written the code. They expect you to spot a design that will not operate |
| Org / strategy | Can you change the shape of the thing, not just run it? | A structural change you made, what you predicted, and what actually happened — including the part that did not |
| Cross-functional | Can you be trusted by people who do not report to you? | A conflict resolved with a peer where you gave something up. 'We aligned' is not an answer |
| Executive / business | Do you understand how the company makes money? | Cost, revenue and risk in the same paragraph as the technology — unprompted |
The three questions that decide most leadership loops
“Tell me about a time you were wrong about something important.” The weak answer is a technical misjudgement corrected quickly. The strong answer is a judgement about people or direction that took months to surface, plus what you changed in how you decide. Seniority is largely the accumulated cost of being wrong slowly.
“What is the hardest thing about your current organisation?” This tests whether you can be honest without being disloyal. Answering ‘nothing’ reads as either unaware or guarded; answering with a list of grievances tells the interviewer exactly what you will say about them next year. The shape that works is a real structural problem, your part in it, and what you are doing.
“How do you know your team is doing well?” Weak answers are velocity and delivery dates. Strong answers pair an outcome measure with a health measure and acknowledge the tension — because a team can hit every date for two quarters by accumulating debt and burning people, and both of those show up later, somewhere you were not looking.
And the question to ask them, which is the most useful in any loop: “What would make you regret hiring someone into this role?” It is very hard to answer from a script, and the hesitation is as informative as the answer.
A structural note about these loops: at leadership level the reference check is frequently the real decision, and it is often informal — someone who knows someone. That is worth knowing not so you can manage it, but because it means the way you left your last two roles is part of your candidacy whether or not it appears on the form.
Check yourself