India EV Market Entry round·Consulting·Easy·20 min

McKinsey Business Analyst Interview — India EV Market Entry

20 min · 1 credit · scorecard at the end

Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.

ZeroPitch Research Desk

Updated 2026-05-23 · Newly added · be among the first to take it

Field: Consulting
Company: McKinsey & Company
Role: Business Analyst
Duration: 20 min
Difficulty: Easy
Completions: New
Updated: 2026-05-23

How to prepare

What this round tests, what strong and weak answers sound like, and the traps to sidestep.

What this round is about

Topic focus. A market-entry plus profitability case on whether a global automotive OEM with no India presence should enter the India electric vehicle market and how it would reach profit.
Conversation dynamic. The interviewer is led: he steers the case, releases a data point only when you ask for that specific input, and pressure-tests your assumptions by making you recompute.
What gets tested. Structuring an open question, forming a hypothesis, market sizing and breakeven math out loud, interpreting the data you request, and a two-minute recommendation.
Round format. A single continuous case at the McKinsey India first-round Business Analyst bar, roughly twenty minutes, no calculator.

What strong answers look like

Scoped before solved. You restate the objective in one sentence and ask one or two sharp clarifying questions before structuring, for example product scope and time horizon.
Non-overlapping structure with a first branch. You lay out a small set of buckets that do not overlap and together cover the decision, then name which one you would test first and the hypothesis behind it.
Localised, not generic. You tie the analysis to India specifics: two-wheeler versus passenger segments, battery pack as the dominant cost lever, localisation for cost parity, rather than reciting a textbook tree.
Math out loud with a recommendation. You size the market and compute a breakeven volume with clean units, then close with a CEO-level recommendation stating the call, the key number, and the main risk.

What weak answers look like (and how to avoid them)

Numbers before structure. Diving into calculations with no laid-out approach: take ten seconds of silence and give the structure first.
Overlapping or gappy buckets. Buckets that double-count or leave holes: state your buckets and check aloud that they do not overlap and cover the whole decision.
Generic framework spray. Reciting a market-entry framework with no India or battery economics: anchor every branch to a concrete EV cost or segment fact.
No so-what. Ending the analysis without committing: always close with a recommendation, the number behind it, and the risk you are accepting.

Pre-interview checklist (2 minutes before you start)

Recall the profitability identity. Have profit equals revenue minus cost, revenue equals volume times price, cost splits fixed and variable ready to localise.
Have a market-sizing path ready. Be ready to size India EV demand from population, vehicle base, and a penetration rate without being told the method.
Identify the segment split. Be ready to separate electric two-wheeler and three-wheeler from passenger early, since the economics differ.
Pull up unit-economics instincts. Be ready to compute a breakeven volume from a bill of materials and a price point in your head.
Re-read the objective in your own words. Plan to restate entry-and-profitability as one sentence before structuring.
Think of one judgement call. Have one moment ready where you changed your own answer after new data, for the closing reflection.

How the AI behaves

Steers and rations data. It drives the case and gives you one requested number at a time, never a data dump and never the structure.
Probes every assumption. It asks you to walk the arithmetic and sanity-check units rather than accepting a stated number.
No mid-interview praise. It will not say great answer or validate, it acknowledges the specific content then pushes.
Interrupts on framework spray. It cuts in when you recite generic buckets with no prioritisation or no India localisation.

Common traps in this type of round

Opportunity over cost. Selling how big the India EV market is while never doing the cost side, which is where this case is decided.
Framework name as the answer. Dropping a framework label and treating the buckets as the analysis instead of testing one branch.
One undifferentiated market. Treating India EV as a single market rather than splitting two-wheeler and three-wheeler from passenger.
Unit drift. Losing track of rupees, lakh, crore, or units between revenue and cost so the breakeven is internally inconsistent.
Rationalising under challenge. Defending a shaky number instead of recomputing it cleanly when pushed.
No recommendation. Trailing off into more analysis instead of committing to a call with a number and a risk.

Reference

The full breakdown

How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.

Interview framework

You will be scored on these 6 dimensions. The full rubric with definitions is below.

Structure And Mece Discipline

How cleanly you break the decision into non-overlapping buckets that fully cover it, and whether you prioritise a branch instead of listing everything.

22%

Hypothesis Discipline

Whether you state an upfront hypothesis and a first branch to test, rather than analysing every area at equal depth.

16%

Quantitative Accuracy Under Pressure

How accurately and quickly you size markets and compute breakeven out loud, keeping units consistent and sanity-checking magnitude.

22%

India Ev Domain Localisation

Whether you anchor the analysis to India segment economics and battery cost rather than reciting a generic textbook tree.

16%

Recommendation And Synthesis

Whether you close top-down with a clear call, the number behind it, and the main risk, in CEO-ready form.

14%

Data Request Efficiency

Whether you ask for one specific input at a time and state what you will do with each number you request.

10%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

Common questions

What does the McKinsey Business Analyst market-entry case actually test?

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.

How should I structure my answer in this round?

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.

What are the most common mistakes candidates make here?

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.

How is this AI interviewer different from a real McKinsey interviewer?

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.

How is scoring done in this practice round?

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.

What should I do in the first two minutes of this case?

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.

How do I handle it when the interviewer pressure-tests my market size?

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.

What does a strong answer in this case sound like?

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.

Why is the two-wheeler versus passenger segment choice so important in this case?

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.

How much does mental math matter and can I use a calculator?

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.

Does this round include the Personal Experience Interview?

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.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.