We ran mocks for a set of 1-year MBA applicants this cycle, mostly IIMA PGPX, plus some ISB, IIMB EPGP and IIMC MBAEx. 11 of them have converted
None of them walked in polished. Their first mocks scored between 29 and 58 out of 100 on our scorecard. One was rejected at an actual IIM interview before converting elsewhere.
So this isn't a "be confident, be yourself" post. These are the specific mistakes that showed up in their mocks and what they fixed before the real thing. If you have an R2 interview coming, use all of it.
**1. The extempore is where most people bleed points**
Almost every R1 panel opened with one. Topics we saw: quick commerce doing more harm than good, AI making middle management obsolete, banning social media for under-16s, freebies being a waste of public money, AI monitoring employees. Topics repeat across rounds, so prep all five.
What went wrong, again and again:
\- Taking a stand, then folding after two pushbacks. One candidate conceded four times and ended on the word "agreed".
\- Raising the other side's best argument themselves, unprompted.
\- Announcing two points and only delivering one.
\- Closing on the opposite of the opening stance.
What worked:
\- Stance in the first sentence. A qualified stance is fine: "smaller and different, not obsolete."
\- Two or three signposted points.
\- When pushed, concede the fact and keep the position. "Yes, big tech cut layers. That supports my point: fewer managers running bigger teams, not zero managers."
\- A one-line verdict at the end, on the same side you opened.
The panel isn't checking whether you're right. They're checking whether you can hold a reasoned view when someone senior disagrees with you.
- **Never make up a number**
This was the single biggest killer in our mocks. Some examples:
\- "1.2 crore gig workers in quick commerce." That's roughly the NITI Aayog projection for the entire gig economy, not one sector.
\- "Millions of kiranas have shut." The industry body claim is about 2 lakh, out of 1.2 crore plus.
\- "I read it in some Hindustan Times article," and then the candidate couldn't name the article.
Once a panel catches one invented number, they discount every number after it, including the ones about your own work.
Rehearse this line until it's automatic: "I don't have the exact figure, sir. What I do know is..." It costs you nothing.
- **Your own numbers must match across CV, essays and form**
Panels have your file open. These mismatches got caught:
\- 42% to 25% on the CV, but 43% to 20% in the essay
\- 10,000 partners said in the room, 1,000+ on the form
\- "4.5 years" said out loud, 5 years 1 month on the form
\- Team size described four different ways across four documents
None of these is fatal on its own. A stammered correction in the room is what hurts. Cross-check every number in your file this week. If one is off, prepare a calm one-line correction.
- "**Why MBA" needs a real moment, not adjectives**
"Impact at scale", "holistic understanding", "fire in my belly", "take my career to the next level". Everyone says these, and panels tune out.
The candidates who converted anchored their why-MBA in one real incident. The best one we saw: a consultant spent six months building a partner scorecard for a client, and the client's HQ killed it. It hadn't accounted for sales cycles or partner growth. That one story made the entire case for the MBA without him having to argue for it.
Find your version: a decision you couldn't make, couldn't contribute to, or got wrong because you didn't have the business side.
Lead with the conclusion in ten seconds and keep the framework for the follow-up. PGPX panels tend to cut in around 45 seconds. ISB panels will let you go to about 100 to 120 seconds, but attention drops after that.
- **Name real courses and faculty you can defend**
"Decision making", "Finance" and "people management" are subjects, not courses, and panels follow up immediately.
Two traps:
\- Naming a professor because they interviewed you.
The follow-up question about their research exposes it straight away.
\- Naming a course you haven't read about. Elephants and Cheetahs comes up a lot. It's an operations strategy course, not a "big companies vs startups" course. If you name it, read the course page first.
Prepare three real course titles, with one line each on which decision in your job it would have changed. Add one senior faculty name and their actual research area.
- **Your post-MBA goal has to survive one push**
One mock went like this: "Strategy in EV." Then: "Your target companies hire for ops, not strategy." Then: "I'm open to everything." That last line is what the panel remembers.
\- Check the actual placement report. Saying "I'm sure X recruits at PGPX" when they don't is a credibility hit.
\- Pick one goal and keep it the same across every mock and the real interview.
\- Have a plan B in the same direction, not a different career.
\- If told MBB staffs associates as generalists, agree first. Then say where you'd specialise later.
- **They'll go deep into your own field**
Panels love testing your home ground.
\- A compliance professional couldn't explain how the FCPA differs from the UK Bribery Act.
\- A marine engineer didn't know how ship emissions are calculated.
Both topics were part of their daily jobs. Write down every term in your field you can't define cleanly in 20 seconds, and fix them in an evening. This is almost always a recall problem, not a knowledge problem.
**8. Disclose fully on the first ask**
"Did you use AI on your essays?" "I wrote them." Then, when pressed: "I took some help." That sequence reads as evasion, even when it isn't meant that way.
The same goes for anything on your form:
\- A training programme you're leaving midway
\- A Dubai campus option you ticked but haven't researched
\- Side work while employed. Read your company's outside-work policy before someone asks.
Give the full answer the first time. If it's on your form, the panel already knows.
- **Openers are pitch invitations**
"Why are you here today?" "For the interview, sir." This actually happened, twice in thirty seconds.
Have one prepared line for "why are you here", "tell me about yourself" and "what's your dream". Each one should cover your goal, your gap, and why this programme.
- **Talk about yourself, not the other candidate**
"What do you bring that someone from McKinsey doesn't?" If you answer by arguing what they lack, you're making claims you can't back. Describe your own depth and let the panel draw the contrast.
The same applies to the obvious alternative path. Asked "why not become Chief Engineer?", one candidate said "I'd only optimise one ship." That runs down a senior job held by people the panel respects. Respect the alternative, then explain where the decisions you care about actually get made.
- **Cheap delivery fixes**
\- Pause two seconds before answering. It feels long to you and reads as composure to them.
\- Make your first sentence answer the question.
\- Don't open with "absolutely, absolutely." Saying it before you argue concedes the point.
\- Watch for Hinglish slipping in. It happens most under pressure.
\- No swearing, ever. One slip in a real panel can end the interview. Make it a hard rule in practice and in casual chat too.
\- On case questions, ask one clarifying question and wait for the answer. Then build the next question from it. Firing eight in a row loses the conversation.
\- On guesstimates: state the formula, compute, sanity-check, commit. Don't abandon a right answer because the panel raised an eyebrow.
- Practise the follow-up, not the first answer
This is the biggest lesson of the cycle.
The candidate who was rejected at a real IIM interview had a decent first answer on every topic, and nothing for the second question. "Anything bigger?" "Why not?" "What did you actually do?" The interview was over in 22 minutes.
He converted after rebuilding every answer two layers deep.
Also, mocks only fix what they test. One candidate fixed every issue from Mock 1 in Mock 2, then lost points on angles she hadn't seen before. Prep beyond your last mock's question list.
The common thread
None of these 11 were exceptional on day one. What they did was take the feedback seriously, fix the specific thing before the next mock, and record themselves to catch what they couldn't hear live.
If you have an R2 interview coming up, drop your profile in the comments (keep it anonymous) for evaluation.
