10-Minute Quick Commerce India Entry round·Consulting·Medium·20 min

McKinsey Associate Interview — 10-Minute Quick Commerce India 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: Associate
Duration: 20 min
Difficulty: Medium
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. An interviewer-led McKinsey market-entry case on whether Sahaj Retail, a profitable mid-sized Indian supermarket chain, should launch its own 10-minute quick-commerce service against Blinkit, Zepto and Swiggy Instamart.
Conversation dynamic. A Partner sets the prompt, releases data only when you ask a precise question, and pushes on every assumption and number you cannot ground.
What gets tested. A tailored structure, sanity-checked market sizing, dark-store unit-economics reasoning, a credible right-to-win, and an answer-first recommendation under pressure.
Round format. A single continuous case at the post-MBA Associate bar, roughly nineteen minutes, opening clarification through final recommendation and reflection.

What strong answers look like

Clarify before structuring. You confirm the objective and decision-maker and ask whether the goal is profit, share, or strategic defence before laying out any structure.
Tailored structure with a hypothesis. Every branch is connected to Sahaj and Indian quick commerce, for example you say the decision hinges on whether existing stores can act as micro-fulfilment nodes cheaply enough to beat incumbent dark-store cost.
Numbers out loud, then checked. You compute orders per store times average order value times contribution margin minus rider and fixed cost, then sanity-check the total against the market figures you were given.
Answer-first close. You end with a clear go or no-go, two or three reasons, the biggest risk, and a concrete next step rather than a summary.

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

Generic framework recital. Listing 3C or Porter with no tailoring reads as a red flag; tie each branch to Sahaj and the Indian market instead.
Silent math. Stating a final number with no visible steps loses credibility; narrate every calculation as you do it.
Unchecked figures. A market size with no reasonableness test invites a hard pushback; always sanity-check against a second anchor.
Summary instead of a call. Recapping findings without committing to go or no-go signals weak synthesis; state the recommendation first, then support it.

Pre-interview checklist (2 minutes before you start)

Recall the four-bucket logic. Have market attractiveness, competition, right-to-win, and economics ready to tailor, not recite.
Have a unit-economics skeleton. Be ready to build per-dark-store profit as orders times average order value times margin minus rider and fixed cost.
Identify the real incumbents. Know Blinkit, Zepto and Swiggy Instamart run dense networks with funded parents.
Think of one right-to-win angle. Decide what Sahaj asset could matter, for example existing stores as fulfilment nodes.
Pull up your sanity-check habit. Plan to test every number against a second anchor before you commit to it.
Re-read the prompt intent. Be ready to ask whether the goal is profit, share, or defence within the first minute.

How the AI behaves

Probes every number. Asks how you derived a figure and whether it passes a smell test, not just the headline result.
No mid-case praise. Will not say great answer or validate; it acknowledges the specific content then pushes harder.
Interrupts on recital. Pushes back when a framework is recited without being connected to Sahaj or Indian quick commerce.
Adds constraints when you are doing well. Raises difficulty by introducing a cash-burn ceiling or a cannibalisation concern rather than easing off.

Common traps in this type of round

No objective clarification. Structuring before establishing what a yes versus a no means for Sahaj.
Untailored buckets. A structure that could describe any market-entry case with no Sahaj or India specificity.
Hidden arithmetic. Reaching a number without narrating the steps so the interviewer cannot follow it.
Flat brainstorm. Listing risks with no grouping or prioritisation of which matters most.
Rigid under pushback. Defending an unchecked number instead of recalculating when given new data.
Summary close. Ending by recapping analysis rather than committing to a recommendation with a risk and next step.

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.

Case Structure Tailoring

Whether your structure is built around Sahaj and Indian quick commerce specifically, not a textbook framework recited with no connection to the client.

22%

Market Sizing Arithmetic Discipline

Whether you narrate every calculation step and sanity-check the result against a second anchor instead of asserting a single unchecked number.

20%

Dark Store Unit Economics Reasoning

Whether you build per-store profit from orders, basket size, margin, rider and fixed cost and state the volume where a store turns positive.

22%

Right To Win Judgment

Whether you identify a concrete Sahaj advantage versus the incumbents and honestly test if it is durable rather than listing competitors.

14%

Recommendation Ownership

Whether you lead with a clear go or no-go, defend it with reasons and a named risk, and avoid hedging or a summary close.

12%

Assumption Stress Response

Whether you recalculate and update when the interviewer adds a new data point instead of rigidly defending an unchecked figure.

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 market-entry case round actually test?

It tests whether you can decide, with structure and numbers, if an Indian retailer should launch a 10-minute quick-commerce service. The interviewer drives an interviewer-led case and scores four things: a tailored structure rather than a recited framework, fast and sanity-checked arithmetic on market size and dark-store unit economics, business judgment about the Indian quick-commerce model, and an answer-first recommendation with risks and a next step. It is set against the post-MBA Associate bar, so the depth and pace are higher than a screening chat.

How should I structure my answer in a market-entry case?

Clarify the objective and the decision-maker first, then state a hypothesis. Build your own tailored structure covering how attractive the Indian quick-commerce market is, how intense the competition from incumbents is, whether Sahaj has a credible right to win, and whether the economics work. Prioritise which branch to analyse first and say why. Do not recite a generic framework: the interviewer treats untailored Porter or 3C as a red flag and will push you to connect every branch to Sahaj specifically.

What are the most common mistakes candidates make in this round?

Diving into a structure without clarifying what a yes versus a no means, reciting a generic framework with no tailoring, doing mental math silently so the interviewer cannot follow it, stating a market-size or unit-economics number with no sanity check, listing brainstorm ideas as a flat list with no prioritisation, skipping synthesis between segments, and ending with a summary instead of a confident recommendation. Inflexibility under pushback, refusing to update a number when given new data, also reads as a red flag.

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

It behaves like a real interviewer-led case partner: it sets the prompt, releases data only when you ask a precise question, and probes every number for how you got there. It never praises mid-case, never coaches you toward the framework, and never tells you how you did during the round. The difference is that it produces a transcript-backed scorecard afterwards that quotes the exact moments your structure or arithmetic broke, which a real partner rarely gives you in detail.

How is scoring done in this practice round?

Your transcript is scored against role-specific dimensions: structure quality, market-sizing arithmetic discipline, dark-store unit-economics reasoning, right-to-win judgment, recommendation ownership, and how you respond when an assumption is stress-tested. Each dimension has observable anchors, so two evaluators would land within a narrow band. You are not graded on accent, fluency, or whether you reached one exact number, but on whether your logic survived the interviewer following it in real time.

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

Confirm the objective and the decision-maker, restate the prompt in one line, and ask one or two sharp clarifying questions, for example whether the goal is profit, share, or strategic defence, and whether there is a cash-burn ceiling. Then take a short structured pause and lay out a tailored structure with a hypothesis. Do not start pitching a launch decision before you have analysed anything. The first two minutes set whether the interviewer trusts your judgment for the rest of the case.

How do I handle the dark-store unit-economics part of the case?

Build the economics per dark store: orders per day times average order value times contribution margin, minus rider cost per delivery, minus fixed dark-store cost. Anchor on real ranges, a 2 to 3 kilometre catchment, metro density driving profitability, smaller towns taking six to twelve months to stabilise. State every number out loud, sanity-check the result against the market figures the interviewer gave you, and say what would have to be true for it to be profitable rather than asserting it is.

What does a strong answer sound like at the McKinsey Associate bar?

It opens with a clarifying question, states a hypothesis, and walks a tailored structure where each branch is connected to Sahaj and Indian quick commerce. It does arithmetic out loud with sanity checks, recalculates rather than rationalises when the interviewer pushes, and closes answer-first: a clear go or no-go, the two or three reasons, the biggest risk, and the next step. It treats the incumbents Blinkit, Zepto and Swiggy Instamart as a concrete right-to-win problem, not a generic competitor bullet.

Why does the interviewer keep pushing on my numbers?

Numerical ability is one of the four core skills McKinsey scores, and the partner specifically checks whether you can compute quickly, narrate the steps, and sanity-check the result. Pushing on a number is not a sign you are wrong: it tests whether your figure was reasoned or guessed and whether you will update it when given new data. Candidates who recalculate calmly gain credibility; candidates who defend an unchecked number rigidly lose it.

How does the right-to-win question apply against Blinkit, Zepto and Swiggy Instamart?

The three incumbents already run dense dark-store networks, around 2,100 for Blinkit and 1,100 to 1,200 each for Zepto and Swiggy Instamart, and have funded parents absorbing losses during the land grab. A strong answer does not just list them as competitors; it asks what asset Sahaj has that they do not, for example existing stores as micro-fulfilment nodes, a loyal base, or local supplier terms, and tests honestly whether that is a durable edge or a temporary one.

What happens if I freeze or go down the wrong branch?

The interviewer will redirect once with a narrower question rather than rescue you or hand you the structure. Recovering well, naming where you got stuck, recalculating, and re-prioritising, is itself a positive signal because real engagements rarely go cleanly. What hurts is staying silent, refusing to commit, or repeating the same unstructured answer after a redirect. Treat a redirect as new information and adjust, the same way you would update a hypothesis when the client gives you a new fact.

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.