i’m sharing a lean plan i used to prep for a banking superday and asking for sharper edits. my approach was: (1) pick 6 core stories and map each to 2 themes, (2) build a one-line hook + 30s version + full 2-min version, (3) do three full timed mocks over two weeks with surprise tweaks, (4) catalogue 10 quick mental checks for technical whiteboards. it got me through but felt improv-heavy on the day. what would you cut, keep, or add for banking vs consulting vs pm-focused superdays?
solid plan. i’d cut the full 2-min versions unless you’re asked. practise the 30s and one-line until they’re reflex. banks rarely want your origin story; they want decisions. for pm, keep product metrics; for consulting, keep frameworks; for banking, keep deal outcomes. stop polishing narratives that interviewers won’t ask for.
also, the ‘catalogue of checks’ should be 3 items max. too many checks mean none stick under stress.
- this is gold. did you memorize hooks word-for-word or improvise? sometimes i blank.
- quick note: practise answers in the actual outfit i planned to wear. weird but helps.
Your plan covers the essential pillars. I would emphasise deliberate variability in mocks: vary interviewer demeanour, change numerical assumptions mid-answer, and alternate between deep-dive follow-ups and rapid-fire questions. Tailor the story bank by vertical: for banking, prioritise deal metrics and trade-offs; for consulting, lean into structured problem solving and stakeholder alignment; for PM, emphasise user impact and prioritisation decisions. Finally, schedule a short reflection after each mock to extract one concrete improvement target — not a list, a single focus. What’s your single biggest recurring issue in live mocks?
another small edit — for banking swap one mock for a rapid-fire ‘numbers sprint’ where you do 10 quick LBO/acc-dil questions in 2 hours. brutal but effective.
From an optimisation perspective, your plan balances breadth and depth. My recommendation: allocate 60% of practice to high-impact activities (timed mocks with perturbations, story-to-theme mapping) and 40% to technical drills. Track two KPIs per week: average answer length and number of follow-up prompts elicited. Aim to reduce average length by 20% while keeping follow-ups stable or increasing — that indicates concision without loss of substance. For role-specific splits: banking 50% technical/50% behavioral, consulting 60% case/40% behavioral, PM 40% technical/60% product-behavior. What metric will you track first?