i made the mistake of prepping one-size-fits-all mocks — then failed to account for role-specific signals. veterans helped by tailoring feedback: for IB they grilled my number structuring and deal rationale; for consulting they challenged my logic trees and synthesis; for PM they asked about trade-offs, metrics, and stakeholder buy-in. that no-fluff feedback helped me reweight practice drills. what’s your approach to modifying the same case to hit different role expectations?
stop treating cases like a buffet where you pick whatever looks nice. IB cares about clean, auditable math and deal logic. consulting cares about crisp structure and recommendation synthesis. PM cares about user impact and trade-offs. tailor your language and metrics. if you show a consultant-style synthesis in an IB interview they’ll blink and ask for numbers. know who you’re talking to and act accordingly.
the lazy candidate tries to please everyone. the good one knows the job and speaks its language. no sympathy for mixing signals mid-case.
i started a role-matrix: for each role, list 3 must-show skills. helped focus practice. anyone got a template?
Role-specific customization is often overlooked. I recommend constructing role templates before you practice: for IB, prioritize transaction rationale and sensitivity to valuation; for consulting, practice hypothesis-driven structures and a concise 2–3 point executive recommendation; for PM, emphasize metrics, user personas, and stakeholder constraints. During mocks, explicitly state which role lens you’re using at the start — that primes the interviewer and frames your answers appropriately. This also helps the debrief; veterans can then give role-aligned critique rather than generic advice.
great shift — once you frame the role at the start, your answers feel much more on-point. keep tailoring, it pays off!
i once used the same case for IB and PM mocks. for IB i leaned into deal structure and NPV; for PM i repurposed the same numbers to show user monetization scenarios. veterans called out different blindspots and i suddenly had two skill sets to practice from one case. repurposing is efficient if you change the lens deliberately.
in another mock i prefaced: ‘answering as a product manager.’ immediate shift in follow-ups. small label, big difference.
From reviewing mock outcomes, the top differentiator between role-aligned and generic candidates is metric selection. IB candidates who emphasized transaction-specific KPIs (IRR, EBITDA adjustments) scored higher; PM candidates who framed user metrics (activation, retention) did better. Create a short list of 3–4 role-specific KPIs and force yourself to reference one during every recommendation. It’s a low-effort way to signal domain fit and focus your analysis.