The interview playbook: run the room, get the offer

Most people prepare for interviews by rereading the job posting and hoping. Then they walk into a room where the other side has a structured scorecard, a list of concerns, and forty-five minutes to decide whether you’re a yes — and they improvise. The result is predictable: rambling answers, forgotten wins, and the drive home spent composing the brilliant things you should have said.

Here’s the reframe that changes everything: an interview is a performance, and performances are rehearsed. Not memorized — rehearsed. Roughly 80% of what you’ll be asked is knowable in advance, which means the winning move is to build your material before you’re in the chair. This playbook is that build: five parts, a worked example, and the failure modes that sink good candidates.

Part 1 — The dossier: 45 minutes, five questions

Before any interview, you should be able to answer five questions in one sentence each. What does this company sell, and to whom? How does it actually make money (not the mission — the mechanism)? What happened to it in the last six months — funding, launch, layoff, leadership change? Who am I meeting, and what does each of them own? And the big one: what problem is this role being hired to solve? Nobody opens a headcount for fun. Someone upstairs is feeling pain — missed revenue, a churning team, a product that ships late. Your entire candidacy is an argument that you end that pain.

That last question powers the answer everyone fumbles: “Why do you want to work here?” The weak answer recites the company’s About page back at them. The strong answer connects their problem to your evidence:

• Script: “From the posting and your last two quarters, it looks like you’re trying to [the problem]. That’s the exact shape of what I did at [company], where [one-line result with a number]. That overlap is why I’m here.”

Part 2 — The story matrix: six stories, indexed

Behavioral questions feel infinite but they aren’t. Nearly every one is fishing for one of six things. Build one 90-second story for each, and you’ve pre-answered most of the interview:

1. The win — you drove a result that mattered. Your flagship story.
2. The failure — something you owned that went wrong, and what changed after.
3. The conflict — you disagreed with a colleague or boss and resolved it like an adult.
4. The leadership — you moved people without (or beyond) formal authority.
5. The speed — you delivered under a brutal deadline or with nothing.
6. The judgment — you made a hard call with incomplete information.

Write each to a strict template: Stakes (one line — what was on the table), Moves (two or three lines — what you did, first person singular), Score (the result, with a number), Scar (one line — what you’d do differently or what you now do every time). Numbers are non-negotiable. “Improved onboarding” is noise; “cut onboarding from 12 days to 5” is evidence. If your work is hard to quantify, count something: people, dollars, days, tickets, retention points.

Part 3 — Answer architecture: headline first, then stop

Structure beats brilliance in a live room. For every question, answer in this order: headline (your answer in one sentence), evidence (the relevant story, compressed), stop (a full stop, not a trailing “so, yeah…”). The discipline of stopping is what reads as confidence. Nervous candidates keep talking to fill silence and dilute a strong answer into a weak monologue; the interviewer’s follow-up will tell you exactly which detail they want more of — let them ask.

Worked example. Question: “Tell me about a time something you owned failed.”

• Weak: “Hmm, a failure… I guess our product launch was pretty chaotic, there were a lot of factors, marketing was late, and honestly the timeline was unrealistic from the start…” (No ownership, no number, blames the room.)
• Strong: “I shipped a feature to 100% of users instead of staging the rollout — my call — and a payment bug hit about 3,000 customers in the first hour. We rolled back in forty minutes, I wrote the postmortem naming my own decision as the cause, and every launch I’ve run since goes out behind a percentage rollout. Support tickets on my launches dropped roughly 60% after that.” (Ownership in the first sentence, a number, a scar, a system.)

Notice the strong answer is also shorter. That’s not an accident.

Part 4 — The reverse interview: five questions that flip the room

“Do you have any questions for us?” is not a courtesy — it’s scored. Asking about vacation policy in round one signals you’re shopping; asking operator questions signals you’re already doing the job. Five that consistently land:

1. “What would the person in this role have to do in the first six months for you to call the hire a home run?”
2. “What’s the hardest part of this job that isn’t in the posting?”
3. “Why is this role open — growth, backfill, or reorg?” (Each answer tells you something different about what you’re walking into.)
4. “How does this team make decisions when two senior people disagree?”
5. “What almost made you leave, and what kept you?” — for the interviewer personally. It’s disarming, and the honest ones tell you the truth about the culture.

Part 5 — The close and the follow-up

End every round with the two-line close almost nobody uses: “Based on what you’ve seen today, is there anything about my background that gives you pause? I’d rather address it now than have it decide things in the debrief.” Two things happen: you get a live shot at killing an objection while you’re still in the room, and you signal a comfort with direct feedback that most candidates never show. Then: “What’s the next step, and when should I expect to hear?” — so you’re never the person refreshing their inbox on a guess.

Within 24 hours, send a follow-up that isn’t a thank-you card. Three sentences: reference one specific moment from the conversation, add one new thing (a link, a thought that extends something you discussed, a sharper answer to a question you half-hit), restate your interest in one line. The note’s job is to be forwardable — something your champion can paste into the debrief thread.

The six failure modes

• The ramble. Ninety-second answers stretched to five minutes. Fix: headline first, then stop.
• The résumé recital. Walking through your history chronologically instead of answering the question asked. Your résumé got you the room; stories keep you in it.
• Humility theater. “My weakness is I care too much.” Everyone’s heard it; it scores as evasion. Name a real, non-fatal weakness and the system you use to manage it.
• Badmouthing the last job. Even when justified, it transfers the stink to you. One neutral sentence on why you left, then pivot forward.
• Winging the logistics. Late join, dead laptop, echoing mic, wrong building. Logistics are the one part of the interview fully under your control — treat them like part of the score, because they are.
• No questions. “I think you’ve covered everything!” reads as “I stopped caring.” Bring the five from Part 4; ask at least two.

Your prep week, hour by hour

Total investment: about five hours, reusable for every interview after the first. Day 1 (45 min): the dossier. Day 2 (90 min): draft all six stories in the Stakes/Moves/Score/Scar template. Day 3 (45 min): say them out loud, timed, twice. Day 4 (30 min): pick your five reverse-interview questions; rehearse the close until it sounds like you. Day 5 (30 min): logistics dry run — route or link, outfit, printed copies, questions on one card. Then walk in knowing 80% of the script was written before anyone asked a question.