IIM Bangalore EPGP Interview: Format, Panel, and Sample Questions

Career Simplified
3 days ago
10 min read

Sit in on enough IIM Bangalore EPGP interviews and a pattern shows up that candidates rarely expect: the panel doesn't try to rattle you. There's no manufactured disagreement, no theatrical pushback designed to test composure under fire. Instead, they ask one simple, factual question about the field you've claimed expertise in, and watch closely whether you have mechanism or only vocabulary.

That distinction is the entire EPGP interview in one sentence. A candidate who says "I work in hospital operations" gets asked how a specific reimbursement mechanism actually works, not whether they can defend their career choices under stress. If you can explain the arithmetic, the panel moves on satisfied. If you can only repeat the term you used in your resume, the room goes quiet in a way that a generic "tell me about a challenge you overcame" story never prepares you for.

This is why generic MBA interview prep, the kind built around behavioral stories and leadership anecdotes, under-serves EPGP applicants specifically. The bank you actually need is weighted toward domain mechanism, not personality.

Program	Panel	Duration	Pre-Interview Test	What It's Really Testing
ISB PGP	2-3 alumni/admissions interviewers, blind to your essays	30-40 min	Two-prompt WAT, same day	Whether your story holds up without the panel having read your packaged narrative
IIM Bangalore EPGP	2-5 faculty and alumni	15-35 min	One-prompt WAT, paper-based, same day	Whether you have mechanism or only vocabulary in your own domain
IIM Calcutta MBAEx	2-3 faculty and alumni	15-30 min (sometimes 45-50)	None	Whether your reasoning holds up under pushback and comparison to your own alternatives
IIM Ahmedabad PGPX	2-3 professors	15-25 min, right after a 2-min extempore	2-minute extempore on a controversial prompt	Composure under active disagreement, not just content

How the Four One-Year MBA Interviews Actually Differ

The table above this section is your at-a-glance reference across ISB, EPGP, MBAEx and PGPX. Keep it in mind through the rest of this piece: EPGP is the "cordial tone, forensic content" interview of the four, and that combination is exactly what trips up candidates who prepare for stress instead of scrutiny.

How IIM Bangalore Actually Runs the EPGP Interview

The format has two parts on the same day: a written ability test, thirty minutes to write roughly 250 words on an assigned topic, paper-based and handwritten for the current admissions cycle, followed by a personal interview with a panel of two to five people, usually a mix of faculty from different departments and occasionally alumni. The personal interview itself runs fifteen to thirty-five minutes depending on the panel and how deep the conversation goes.

The tone is genuinely different from what most candidates brace for. Reports from recent admits describe the interviews as cordial and casual, closer to a structured conversation than an interrogation. Panelists generally put candidates at ease early, ask about daily responsibilities and career transitions in a fairly relaxed register, and there's rarely any attempt to manufacture pressure through disagreement or rapid-fire questioning the way IIM Ahmedabad's PGPX panels sometimes do.

That relaxed tone is precisely what makes the domain-mechanism question land so hard when it arrives. A candidate lulled into thinking the interview is a friendly chat about their career gets a specific, factual question about their claimed field of expertise, dropped into the conversation without warning, and how they handle it tells the panel more than an hour of behavioral questions would.

What the Panel Is Actually Testing

Where ISB panels are testing whether your story holds up without the essays they haven't read, and IIM Ahmedabad PGPX panels are testing composure under active disagreement, EPGP panels are testing something narrower and more specific: whether the expertise on your resume is real, load-bearing knowledge or borrowed vocabulary.

The mechanism is simple. You've described yourself as working in a particular function or industry. The panel picks one factual, checkable question inside that domain, not a case study, not a hypothetical, a real mechanism you should already understand if your claimed experience is genuine, and asks you to explain it. There's no ambiguity in a mechanism question the way there is in a behavioral one; either you can explain how the thing actually works, or you can't, and a panel of subject-adjacent faculty can tell the difference immediately.

Take healthcare and hospital operations as a worked example, since it's one of the more common domains EPGP sees among applicants. A candidate who describes their work as "healthcare finance" should be able to explain, without notes, how NHS funding actually flows from commissioner to provider, or walk through the basic payer-provider-commissioner split in a health system they've worked in. They should know what a QI (quality improvement) denominator actually measures and why it matters for a specific initiative they claim to have run, be able to do rough PM-JAY (Ayushman Bharat) claim arithmetic if they've touched India's public health insurance scheme, and explain what ARPOB (average revenue per occupied bed) tells you about a hospital's operating economics and how a hospital's profit pool actually forms across departments. None of that is exotic knowledge. It's the baseline mechanism anyone genuinely working in the space would carry without thinking, which is exactly why its absence is so noticeable.

The same pattern repeats across every domain the panel encounters, banking, technology services, manufacturing, consulting. The specific mechanism changes; the test doesn't. This is why our WAT prep guide for EPGP matters as a companion to interview prep, not a separate task: both the WAT and the interview reward the same underlying skill, structured, mechanism-level thinking rather than surface familiarity, delivered under time pressure on the same day.

The EPGP Question Bank: 38 Questions Across 7 Categories, Weighted Toward Domain Mechanism

1. Resume and Career Trajectory (brief, usually opens the interview)

Walk me through your resume.
Why this specific transition at this point in your career?
What does your current role actually involve, day to day?

How to approach this category: Keep this section tight and factual. It's the warm-up, not the test; the panel is orienting itself before the mechanism question arrives, so don't overinvest prep time here relative to the domain sections below.

2. MBA Motivation and Program Fit (brief)

Why an EPGP now rather than three years ago or three years from now?
What specifically about IIM Bangalore's EPGP structure fits your goals?
Where do you see this program changing your trajectory?

How to approach this category: A clear, specific trigger for timing matters more than a polished delivery. Panels have heard every version of "it felt like the right time"; a concrete reason lands better.

3. Domain Mechanism: Healthcare and Hospital Operations

Walk me through how NHS (or your equivalent public health system) funding actually flows from commissioner to provider.
Explain the payer-provider-commissioner split in the health system you've worked in.
What does a QI denominator actually measure, and why does it matter for the initiative you led?
Do the rough arithmetic on how a PM-JAY claim gets reimbursed under Ayushman Bharat.
What does ARPOB tell you about a hospital's operating economics, and how does a hospital's profit pool actually form across departments?

How to approach this category: This is a mechanism check, not a knowledge dump. Explain the actual flow of money or process, in your own words, the way you'd explain it to a colleague who genuinely didn't know it, not the way you'd summarize it in a resume bullet.

4. Domain Mechanism: Banking and Financial Services

Walk me through how net interest margin actually gets calculated and what moves it quarter to quarter.
What is a CASA ratio, and why does a bank's management team care about it?
Explain how NPA provisioning actually works and what triggers a change in provisioning requirements.
How does RBI's repo rate change actually transmit into what a borrower or depositor experiences?
What does the credit-deposit ratio at your bank or NBFC actually tell you about its lending posture?

How to approach this category: Panels in this domain are listening for whether you understand the mechanism behind the metric, not just the definition. Knowing that "NIM is interest income minus interest expense over earning assets" is vocabulary; being able to explain why yours moved last quarter is mechanism.

5. Domain Mechanism: Technology and IT Services

Walk me through the difference between time-and-materials and fixed-price billing, and how each shapes project economics.
What is a bench cost, and how does it actually affect a services firm's margins?
Explain how utilization rate is calculated and why it's watched so closely.
How does an offshore-onshore delivery mix actually change a project's cost structure?
What's the real difference between revenue recognition on a project versus a subscription-based product?

How to approach this category: Candidates from technology backgrounds often default to product or feature vocabulary. The panel wants the underlying business mechanism, the actual economics behind the delivery model you've worked in, not a description of what the software does.

6. Domain Mechanism: Manufacturing and Supply Chain

What does OEE (overall equipment effectiveness) actually measure, and how would you improve it on a specific line?
Walk me through how a working capital cycle actually behaves in your industry.
What's the difference between inventory turns and days of inventory, and why would a plant manager watch both?
Explain landed cost and what actually drives it up or down for a specific product category.
How does capacity utilization actually affect unit economics at your facility?

How to approach this category: This is the category where "I managed a plant" and "I understand plant economics" diverge fastest. Be ready with one specific number you actually moved and the mechanism behind how you moved it.

7. Leadership and Behavioral (brief, usually closes the interview)

Tell me about a time you led a team through a difficult transition.
Describe a conflict with a peer or manager and how you resolved it.
What's a decision you'd make differently in hindsight?

How to approach this category: Keep these answers specific and concise. By this point the panel has already formed its main impression from the domain-mechanism exchange; this section confirms fit rather than making the decision.

Two Worked Examples

A weak answer to a mechanism question (Healthcare):

Panel: "Walk me through how ARPOB actually works at your hospital."

Weak response: "ARPOB is a key metric we track for revenue performance. It's important because it shows how well we're utilizing our beds and generating revenue." This restates the definition without demonstrating any understanding of the mechanism, how the number is actually built, what moves it, or what a change in it would mean operationally. A follow-up ("so if your ARPOB rose 8% last quarter, what actually drove that?") would likely expose that the candidate knows the term but not the mechanism behind it.

A strong answer to the same question:

"ARPOB is total inpatient and outpatient revenue divided by occupied bed-days over the period. At our facility it moved up about 8% last year, and it wasn't occupancy driving it, occupancy was flat, it was case mix. We shifted more elective surgical volume into two high-margin specialties, which raised average revenue per admission without changing how many beds were filled. The profit pool implication matters more than the headline number: a hospital can grow ARPOB in ways that look good on a slide but actually compress margin if the case mix shift comes with higher variable cost per case, so we tracked contribution margin by specialty alongside ARPOB, not instead of it." This works because it explains the mechanism, names the actual driver, and shows the second-order thinking a panel is listening for.

A Week-by-Week Prep Timeline

4-6 weeks out: Identify the two or three domain mechanisms most likely to come up given your specific claimed expertise, not generic industry knowledge, the actual numbers and flows you'd be expected to know cold if your resume claim is genuine. Write out the mechanism for each, in your own words, from memory, then check it against a real source.

3-4 weeks out: Practice explaining each mechanism out loud, unprompted, in under ninety seconds. If you find yourself reaching for jargon instead of a clear explanation, that's the gap to close before the interview, not during it.

2-3 weeks out: Prepare your resume walkthrough and two or three leadership stories, but deliberately spend less prep time here than on the domain sections; this is the smaller half of the interview's actual weighting.

1-2 weeks out: Do a mock interview specifically designed to include an unexpected domain-mechanism question, not just behavioral prompts. A mock that only rehearses your story doesn't test the part of the interview that actually decides the outcome.

Final week: Refresh the WAT format alongside interview prep, since both happen the same day and reward the same structured, mechanism-level thinking under time pressure.

FAQ: What EPGP Candidates Actually Ask

Is the EPGP interview really less stressful than PGPX's? In tone, generally yes, panels are more cordial and less likely to manufacture disagreement. In substance, the domain-mechanism question can be more exposing than PGPX's extempore-driven stress test, since there's no ambiguity in whether you actually know the mechanism.

What if my domain doesn't match the examples given here? The categories above (healthcare, banking, technology, manufacturing) cover the most common EPGP applicant backgrounds, but the underlying test applies to any domain: identify the two or three mechanisms, not just terms, that anyone genuinely working in your field would know cold, and be ready to explain them plainly.

What if I get a mechanism question outside my core expertise? Answer honestly about what you do know and reason through the rest out loud rather than bluffing. Panels can tell the difference between honest reasoning toward an answer and confident guessing dressed up as knowledge.

Does the WAT topic ever relate to the interview questions? Not directly by design, but the same evaluators sometimes sit on both, and a WAT response that shows genuine structured thinking in your domain can prime the panel's expectations for the interview that follows.

How technical should my answer be if the panel doesn't seem to know my specific industry? Explain the mechanism clearly enough that an intelligent generalist could follow it. The goal isn't to show off jargon; it's to demonstrate that you understand the thing well enough to teach it simply.

Is a strong WAT enough to offset a weak interview, or vice versa? Both feed into the same composite evaluation alongside your broader application, so neither fully offsets the other, but a genuinely strong mechanism-level interview performance tends to leave the more lasting impression since it's harder to fake than a well-structured WAT response.

Should I prepare different content for the WAT and the interview? Prepare the same underlying depth of thinking for both. If your WAT response and your interview answers both show the same level of real mechanism understanding in your domain, that consistency itself is a signal the panel notices.

If you want to pressure-test whether you actually have mechanism or just vocabulary in your own domain before the panel finds out for you, message us on WhatsApp for a mock built around domain-mechanism questions in your specific field, not a generic behavioral run-through.