McKinsey Business Analyst Interview — India EV Market Entry

It tests whether you can take an open business question, should an automotive OEM enter the India electric vehicle market and how would it reach profitability, and turn it into a structured, prioritised analysis under an interviewer who steers. You are graded on four things candidate reports and McKinsey case guides consistently name: a clean non-overlapping structure, fast accurate mental math, business judgement that ends in a recommendation, and crisp top-down communication. The interviewer releases data only when you ask, so diagnosing what you need to know is itself part of the test.

Take ten seconds of silence, then lay out a small number of buckets that do not overlap and together cover the decision, state which one you would test first and why, and tie it back to a hypothesis about whether entry pays. For this case the natural areas are the market opportunity and its segments, the competitive field and likely response, the OEM's own cost position and capabilities, and the entry economics including breakeven. Localise every bucket to battery and bill-of-materials economics rather than reciting a generic tree.

The repeat failures from candidate reports are jumping into numbers before any structure, building buckets that overlap or leave gaps, never stating a hypothesis or which branch to test first, reciting a generic market-entry framework without localising it to India EV economics, slipping on mental math or losing units, and finishing with no clear so-what or recommendation. A subtler one is over-selling the size of the opportunity while ignoring the cost side, which is where this case is actually won or lost.

It mirrors the interviewer-led McKinsey style closely: it steers the case, releases a data point only when you ask for that specific input, and probes assumptions by making you recompute rather than handing you the answer. The differences are that it never gives outcome feedback during the session, it holds strictly to one question at a time, and it produces a transcript-backed scorecard afterward. It will not coach you mid-case or tell you the framework.

Your transcript is scored against role-specific dimensions drawn from how McKinsey actually evaluates the case: structure quality, hypothesis discipline, quantitative accuracy under pressure, exhibit and data interpretation, the two-minute recommendation, and clarity of communication. Each dimension has observable anchors, so two evaluators would land close. You also see a live tracker of the case beats ticking off as you hit them, and the scorecard quotes the specific moments your structure or math broke.

Repeat the objective back in one sentence so it is clear you understood it, ask one or two sharp clarifying questions, for example what counts as the OEM's product and time horizon, then take a short silence and lay out your structure with a stated first branch and a hypothesis. Do not start computing before you have a structure, and do not ask for every number at once. The interviewer warms to a candidate who scopes before solving.

Do not defend the number, redo it. Walk the arithmetic out loud, state each assumption, sanity-check the order of magnitude in rupees, lakh or crore, and say explicitly what would change your answer. If you realise an assumption was off, recalculate cleanly rather than rationalising. The interviewer is testing whether you recompute under challenge, not whether your first guess was perfect.

A strong answer scopes the question, lays out a small non-overlapping structure, names the branch to test first and why, and explicitly localises the analysis to India, two-wheeler versus passenger segments, battery pack cost as the dominant lever, and localisation for cost parity. It does the breakeven math out loud with clean units, treats data as something to request, and closes with a two-minute recommendation to the CEO that states the call, the key number behind it, and the main risk.

Because in India the economics differ sharply by segment. Electric two-wheeler and three-wheeler total cost of ownership is far more attractive than passenger or commercial, their new-vehicle share could reach 50 and 70 percent by 2030, and new entrants captured over 75 percent of two-wheeler sales by competing on cost. A candidate who treats India EV as one undifferentiated market usually reaches the wrong entry recommendation, so segmenting early is a high-signal move.

Mental math matters a lot and there is no calculator. Candidate reports specifically flag that cases are harder than published practice cases and that speed and accuracy on arithmetic under time pressure are evaluated. Expect to size a market and compute a breakeven volume out loud. Round sensibly, keep units consistent across rupees, lakh and crore, and state your sanity check so an arithmetic slip does not read as a structural failure.

This practice round focuses on the market-entry and profitability case, which is the part you asked to rehearse. In a real McKinsey India first round you would also face two Personal Experience Interview questions on a single deep story about personal impact, leadership and conflict. The interviewer here may ask one short reflection question at the end about your own judgement during the case, but the bulk of the round is the case itself.