Key Takeaways
- Engineers are the majority at most IIMs, so being a high-percentile engineer with good grades is the baseline, not the differentiator. The panel has met that person fifty times today.
- Panels quietly filter for the engineer who has a point of view beyond code — curiosity, a domain interest, a reason for the MBA that isn't just "tech salaries plateaued."
- The two questions that expose generic engineers: "why MBA after engineering?" and "what do you bring that isn't technical?"
- Your edge is rarely more technical depth. It's connecting your technical work to business, people, or a domain you genuinely care about.
- This is an articulation problem. The differentiation exists in your head; the interview tests whether you can say it out loud, fast, under a tired panel's scrutiny.
By the time your turn comes, the IIM panel has already interviewed a dozen engineers today, and a few hundred this season. Same degree, similar percentile, similar "I want to move into management" answer. If your plan is to be a good engineer candidate, you're planning to blend into the exact group the panel is struggling to tell apart.
The uncomfortable truth: your engineering degree and your CAT score are table stakes. They get you the interview. They do not get you the seat. What gets you the seat is being the engineer the panel remembers — and that has almost nothing to do with how good an engineer you are.
Why "good engineer" isn't enough
IIM cohorts skew heavily towards engineers. That's not a knock on engineers; it's a math problem for you in the interview room. When most of the candidates share your background, your background stops being information. The panel can't differentiate on "engineer with a 99 percentile" because that describes half the people they'll see.
So they look for something else: a candidate who's curious about more than the next framework release, who has a view on an industry or a problem, who can connect what they built to why it mattered to a business or a user. The generic engineer talks about technologies. The memorable one talks about impact, trade-offs, and an interest that suggests they'll thrive outside a purely technical role.
The two questions that expose you
"Why MBA after engineering?" The weak answer — implied or stated — is "tech growth plateaus and management pays more." Panels have heard it a thousand times and it signals you're running from a ceiling, not toward a goal. A strong answer names a specific direction (a function, an industry, a kind of problem) that genuinely needs the breadth an MBA gives, and connects it to something you've already shown interest in.
"What do you bring that isn't technical?" This is the differentiation question in disguise, and generic engineers freeze on it because they've only ever been evaluated on technical output. If the honest answer is "nothing yet," the panel learns exactly what it wanted to know. Have a real answer: a time you led or persuaded, a domain you follow closely, a side interest that shows range, a business angle you brought to a technical project.
⭐ Pro Tip
Before the interview, finish this sentence with something specific and true: "Most engineers in this room can code. The thing that's actually different about me is ___." If you can't fill that blank convincingly, that's your prep, not your delivery. Find the real answer first.
Four ways to actually differentiate
- Connect tech to business. Don't just say what you built — say who it was for, what it changed, and the trade-off you made. That instantly reads as MBA-ready thinking.
- Have a domain point of view. Follow one industry closely enough to have an opinion ("here's where I think Indian fintech is heading and why"). Curiosity beyond your job is rare and memorable.
- Own a non-technical story. A time you led, resolved a conflict, or convinced someone — proof you operate beyond the IDE.
- Make "why MBA" specific and forward-looking. Vague ambition is the engineer's default. Specific direction is the differentiator.
How to prepare
The differentiation almost always already exists — you've done interesting things, you do have interests — but it's buried, and the interview gives you ninety seconds to surface it under pressure. That's an out-loud problem, not a thinking problem.
Rehearse the two exposing questions until your answers are specific and quick. Record yourself answering "why MBA after engineering?" and "what do you bring that isn't technical?", play it back, and listen for the generic-engineer defaults creeping in. Fix one, run again. The general method panels respond to is the same one covered in the mistakes IIM panels hate, and the mirror-image challenge for non-engineers is in our non-engineer survival guide.
Rehearsal · practice that compounds
The panel has met fifty engineers today. Be the one they remember.
"Why MBA after engineering?" and "what do you bring that isn't technical?" are where generic candidates blur together. Rehearsal's AI interviewer drills exactly those questions until your answer is specific, fast, and unmistakably yours.
The one-line version
Being a good engineer is the baseline, not the edge. Find the specific thing that isn't technical about you, point your "why MBA" forward, and rehearse the two exposing questions out loud until you stop sounding like every other engineer in the queue.