Most engineering manager candidates I talk to prepare the same way: they write out full answers to 30 interview questions, memorise them, and then freeze when the interviewer asks the question slightly differently.

It is not a knowledge problem. It is a preparation problem. You cannot memorise 30 scripts and deliver them naturally under pressure. You can, however, prepare 12 stories and use them to answer almost any leadership question.

That is the whole method. The rest of this post is how to do it.

Why scripts fail

A script is brittle. If the interviewer asks "tell me about managing an underperformer" and your script is about an underperformer, you are fine. If they ask "tell me about a time you had to give difficult feedback to someone who was struggling," and your script was filed under a different question, you hesitate — and hesitation reads as uncertainty.

A story is flexible. One real experience — an engineer who was missing commitments, the plan you put in place, the weekly check-ins, the outcome — can answer the underperformer question, the feedback question, the follow-through question, and the "how do you support struggling people" question. Same facts, different emphasis.

Interviewers are not scoring your memory. They are scoring evidence: did you act early, did you do something specific, did you follow through, and did anything change after?

The 12 stories

Start by listing 12 experiences from your own work. Not 12 perfect successes — 12 real situations with a decision in them. A useful starter set:

  1. An underperformer who turned it around — or didn't
  2. Giving hard feedback
  3. Letting someone go, handled well
  4. A conflict with a peer
  5. Retaining someone who was about to leave
  6. A project rescue
  7. A bad hire, and what it taught you
  8. Disagreeing with your manager — and committing
  9. Leading an incident
  10. Growing a senior engineer toward staff
  11. Delivering across teams
  12. A difficult stakeholder

You do not need a dramatic story for each one. You need a specific situation, what you actually did, and an outcome you can defend. Approximate numbers you can explain beat precise numbers you invented — "about a third of reviews were late" is fine; a metric you cannot explain under follow-up is not.

Write each story in STAR form, but keep it short: situation in two lines, what you did, the outcome, and what changed after. If it takes more than 90 seconds to say out loud, it is too long.

Mapping stories to questions

Now take 30 leadership questions — the usual spread across people and performance, delivery, technical leadership, team and culture, stakeholders and strategy, and your management story — and map each question to one or two of your stories.

This is where the method pays off. "How do you retain your best people?" is not a philosophy question. It is story 5: who was at risk, how you knew, what you changed, how long they stayed or grew. "How do you handle conflict between two reports?" is story 4, or a version of it: hear each side separately, a joint conversation, an agreement, a check-in afterwards.

When you map it out, you will find gaps. Maybe you have no story for hiring, or no story for letting someone go. That is useful information — it tells you what to prepare, rather than discovering the gap in the interview.

Practise the mapping out loud, timed. Ninety seconds per answer is the target. Two minutes is the ceiling. If your answer is over two minutes, you have lost the interviewer, however good the content is.

What a strong answer actually sounds like

Take the underperformer question. A weak answer sounds like this:

"I waited and hoped, then put them on a PIP and it worked out."

It has no timeline, no action, and no evidence. Compare it with a strong version of the same story:

"Missed 2 commitments. 6-week plan, pairing twice a week, Friday check-ins. By week 6, 5 of 6 PRs passed clean."

Same story. One has evidence. The difference is not talent — it is preparation. The strong version names the gap, the plan, the cadence, and the outcome. An interviewer can score that. They cannot score "I waited and hoped."

The same pattern holds for feedback. A weak answer is vague, only happens in reviews, and assumes the person "just knew." A strong answer names the specific behaviour, its impact, what you asked for, how they responded, and the follow-up date.

System design, through a manager's lens

EM system design is not IC system design, and preparing for it the same way wastes time. Interviewers are not mainly testing whether you can draw a diagram. They want judgement: trade-offs, who owns what, what breaks first, and how you would staff it.

Practise with prompts like these: who gets notified, when, and what happens if they miss it? Push or pull, retry or drop, noisy failure or silent failure — and why? Who is on call for it, and what breaks first?

A worked walkthrough helps here — for example, walking through a notification system end to end, naming the trade-offs at each step, rather than memorising a system-design textbook. Six focused prompts, practised out loud, will do more than a week of reading.

A 14-day plan that fits in real life

If you have two weeks, here is a shape that works:

  • Days 1–3: Write your 12 stories. No polishing, just get them down.
  • Days 4–8: Map them to the 30 questions. Practise out loud, timed, 90 seconds each. Start with three: the underperformer, difficult feedback, and conflict between two reports.
  • Days 9–12: System design prompts, plus mock interviews. Score yourself on evidence, structure, timing, and follow-through — not on whether it "sounded nice."
  • Days 13–14: Scorecard, weak spots, rest. Do not cram new material the day before.

Track your progress simply: mark each question not started, in progress, or ready, so you practise the ones you dread instead of the ones you already know.

What this method is not

It is not a shortcut, and it will not guarantee an offer — no preparation method can. It is not a video course, and it does not cover LeetCode or salary negotiation. It is a way to turn experience you already have into answers you can actually deliver, in 90 seconds, under pressure.

If you try it, start with three stories and three questions. Practise them out loud today. If you can answer those three cleanly in 90 seconds each, the method works for you — and the other 27 questions are just mapping.

If you want the full version — 30 questions, 12 stories mapped to all of them, 8 worked STAR answers with weak vs strong versions, 6 manager-lens system-design prompts, and a tracker — I put it together as a $15 starter kit. A free 4-page sample (Q1–Q5, one worked answer, tracker preview) is here: https://rainbowroadprep.gumroad.com/l/qiptza — full kit: https://rainbowroadprep.gumroad.com/l/zwsrde