Consulting Interview Practice

The grade is the anchor chosen and defended (stores x throughput x ticket, or demand-side households x frequency), the narrated assumption chain, and the sanity close. Interviewers track structure, not arithmetic.

Why it matters: First-round standard; it tests whether you can build a number from nothing without losing the listener.

Common mistake: Reaching for the most precise-seeming chain. 500 residents/store is a better assumption than a 3-decimal market share because it is checkable.

Trade-off: State the assumption your answer hangs on and how you would test it cheaply (visit three stores). Confidence calibrated to evidence is the senior signal.

Ideal structure: Narrate the structure before numbers: stores x daily transactions x ticket size x days, top-down and bottom-up cross-check, explicit assumptions, and a confidence range with what you would validate first.

Tip: The interviewer is grading the structure, not the arithmetic.

Follow-up to expect: “A competitor just signed 20 locations. Restate the range.” Adjusting explicitly instead of silently is what they are checking.

The market-vs-self split is the whole answer: is the market growing faster, is the growth from price not volume, are they losing a segment they deliberately abandoned. Each question either saves or redirects the engagement.

Why it matters: The classic client trap. The junior fixates on the falling share line; the grade is noticing growth and share answer different questions.

Common mistake: Rushing to competitive analysis before checking whether the “loss” is a deliberate mix shift (premium exit = margin gain).

Trade-off: Name what you would ask the client to pull before your next meeting; scope discipline beats a beautiful unfalsifiable tree.

Ideal structure: Separate market decline from share loss, then segment (geography, product line, channel, cohort), form two hypotheses, and name the data that would falsify each. Clarifying questions are the answer.

Tip: Spend the first five minutes asking; panels watch how you frame.

Follow-up to expect: “Growth is price, volume fell, share loss is all one segment: what is the actual problem?” Reframing to the abandoned segment’s economics is the expected pivot.

Graded on mechanism specificity: which number or demonstration moved them, whether you engaged before the meeting where they could entrench, and what you conceded. Persuasion with a visible engine scores; “built consensus” scores nothing.

Why it matters: The change story; consultants live where analysis meets politics.

Common mistake: Winning-measure stories. Panels respect the partial win honestly told (“he blocked half; here is what I traded for the rest”) far more than clean victories.

Trade-off: Name the relationship cost and how you managed it. Stakeholder wins that burned a bridge get flagged in reference checks; interviewers know this.

Ideal structure: The specific objection, the analysis or proof you built (not opinions), what changed in one round of meetings, the outcome number, and what you would do differently.

Tip: Consulting panels score how you handled "no".

Follow-up to expect: “What if they said no a second time?” Escalation discipline (when, to whom, with what options) is the scheduled follow-up.

Profit bridge thinking: decompose revenue (volume x price x mix) before costs, find the flat’s composition (which product/geography held it down), then match the cost rise to it. The sequence is the grade; starting with headcount cuts reads reactive.

Why it matters: The profitability case’s core move. Separating revenue diagnosis from cost diagnosis is what training the first week.

Common mistake: Cost-first instinct. If revenue mix is shifting to low-margin, cutting costs preserves the wrong business.

Trade-off: State the cost categories you would NOT touch (the moat: brand, platform, key talent). Optimization without a protected core is a red flag interviewers note.

Ideal structure: Revenue mix decomposition → margin-per-segment view → cost structure mapped to that mix, then the hypothesis (e.g., growth moved to the low-margin segment while fixed costs scaled for the old mix) and the test that would prove it.

Tip: Say “before proposing cuts, I would know which revenue we want to grow.” That sentence alone re-frames the case.

Follow-up to expect: “The CFO wants a number by Friday.” 80/20 scoping with stated assumptions is the expected pressure answer.

A market-entry rubric with judgment: demand and its size, competitive dynamics, capability fit (what would we have to build vs buy), economics (what must be true to pay back), and the recommendation as a staged bet. Enter/exit answers score below test-then-decide answers.

Why it matters: Strategy practice compressed into ten minutes; it is also how consultants are evaluated on real work.

Common mistake: Balanced no-recommendation summaries. Clients hire for a view; “it depends” is the fail state.

Trade-off: Commit to the condition that flips you: state the kill criterion (CAC over X by month six walks away). Falsifiable commitments are the senior tell.

Ideal structure: Rubric → what must be true → the cheapest test of each → staged recommendation with a kill date → the two risks that would make you wrong.

Tip: End on the pilot design, not the deck. Landing answers are what consultants are paid for.

Follow-up to expect: “The CEO already decided to enter: still recommend the same?” Client-reality handling: sharpen the test, own the framing. The answer they probe for is whether judgment survives hierarchy.