How to Handle an IB Interview Question You Didn't Prep For

Every IB candidate, no matter how prepared, will get a question they didn't prep for.

A technical curveball. A sector question they hadn't researched. A market event they missed. A behavioral question they didn't anticipate. The question that breaks most candidates isn't the hard one they prepped for. It's the one they didn't see coming.

The skill being tested in that moment isn't your knowledge floor. It's what you do when you hit your ceiling. The candidates who get offers aren't the ones who never miss. They're the ones who handle the miss without collapsing. This piece walks the mechanics of that moment: what interviewers are actually testing, the three failure modes most candidates fall into, the framework that works, and how to adapt it across different question types.

What This Question Is Actually Testing

The meta-frame. The interviewer is testing four things when they ask you something you don't know.

Honesty. Will you bluff. The interview is a high-stakes conversation, and the interviewer wants to see how you behave when the easy out is a lie. Most candidates take the easy out without realizing it's being scored against them.

Composure. Can you handle uncertainty without panic. The interview is a simulation of the work, and the work is full of moments where you don't know the answer and have to perform anyway. The candidate who panics on a question is the candidate who will panic on a deal.

Reasoning. Can you derive an answer from what you do know. Memorization gets you through the floor. Reasoning gets you past it. Bankers care about reasoning more than they care about recall because the work rewards reasoning every day and rewards recall only occasionally.

Self-awareness. Can you accurately gauge what you know versus what you don't. This is the trait that decides whether you survive year one as an analyst, when you're going to be wrong about a hundred things and need to know which ones you can fake your way through and which ones you need to escalate.

The fifth thing, less obvious but more important: client simulation. Junior bankers get asked questions they don't know constantly, by clients, by MDs, by senior partners. The right response in those moments is the survival skill that decides who stays and who washes out. The interview is testing for that skill, using a question you can't answer as the trigger.

The Three Failure Modes

The wrong ways candidates handle this, paired with why each fails.

The Bluff. Pretending you know. Making up an answer that sounds plausible. Hoping the interviewer can't tell. The interviewer almost always can tell, because they know more than you do. They've been asked the same question by other candidates. They've worked through the topic on live deals. The bluff gets caught, and the catch is much worse than the original "I don't know," because now the candidate has signaled dishonesty in a high-stakes conversation. Bluffing also creates a follow-up trap. The interviewer pushes, the bluff unravels, and the candidate has to either double down (worse) or confess midway (much worse). Either way, the conversation is over even if it continues politely for another twenty minutes.

The Freeze. Long pause. Visible panic. No answer at all. The candidate stares into the camera or down at the table, mind blanked, nothing coming out. The freeze reads as two things at once: inability to think under pressure, and inability to manage the candidate's own nervous system. Both are negative signals for client work, where the same kind of pressure shows up live every week. The freeze is also visible to the interviewer in a way the candidate underestimates. They can see the panic, hear the silence, and they're scoring it.

The Surrender. "I don't know," then silence. Honest, but lazy. The interviewer wants to see what happens after you realize you don't know. The surrender deprives them of the thing they're actually testing for. It's better than the bluff because it doesn't compound the problem with dishonesty, but it leaves all the credit on the table. The candidate who surrenders is signaling "I gave up rather than thought about it," which is its own negative signal even if it's an honest one.

The right move is none of these. The right move has structure.

The Framework That Works

A three-step structure.

First, acknowledge directly and briefly. One sentence, calibrated tone, no apology. "I haven't worked through that specifically." "I don't have the answer to that off the top of my head." "I missed that one." The acknowledgment buys you the credibility to reason in the next step. Skipping it and going straight to reasoning makes you sound like you're bluffing, which is worse than the original gap.

Second, reason out loud from what you do know. "Let me work through it. My read would be..." Walk the interviewer through your thinking. Not silently. Out loud. Narrate the reasoning even if you can't land on a definitive answer. This is the part that earns credit, because this is the part the interviewer is actually testing.

Third, land somewhere. Either an answer with appropriate uncertainty ("my best guess is X, but I'd want to verify the specifics before I'd commit to it"), or a clear honest acknowledgment that you can't get there from what you know ("I don't have enough to derive it confidently, and I wouldn't want to guess at this level"). Both landings are acceptable. The unacceptable landing is rambling without a conclusion.

Total time: twenty to forty seconds. Long enough to show the reasoning. Short enough to not waste interview time. Most candidates either underuse the time (surrender in fifteen seconds) or overuse it (ramble for two minutes). The thirty-second target is the calibration that signals you've thought without spinning.

Different Question Types, Different Approaches

The framework adapts by category.

Technical questions you don't know. Reason from first principles. If asked about a specific accounting treatment you haven't memorized, work through what the principle would imply. "I haven't worked through ASC 606 in detail, but the principle on revenue recognition is around when control transfers to the customer, so my read for a software subscription would be..." The interviewer cares more that you can reason from principles than that you've memorized the specific rule. Reasoning from principles is the analyst's actual skill; memorization is what falls apart at hour fourteen of a deal.

Market or current events questions. Acknowledge if you missed the specific news. Pivot to the principle underlying the question. "I missed that specific announcement. The broader question is about regional banking consolidation, which I have been thinking about, so let me work through the dynamics." Bluffing about a deal announcement is the most catchable lie in IB interviews because the interviewer is in the market every day. They saw the announcement, they have a view on it, and they will catch your fake view in one follow-up.

Sector-specific questions outside your prep. Acknowledge the gap directly, then reason from the general framework. "I haven't focused on the energy sector specifically. The general framework on commodity exposure is..." Don't pretend to know a sector you haven't touched. The pretense collapses in two follow-ups, because the interviewer works in that sector and you don't.

Behavioral or fit questions you weren't expecting. Buy yourself five seconds with a calibrated pause: "Let me think about that for a moment." Then answer with whatever honest material you have. "I haven't been asked that before, but the honest answer is..." The pause is acceptable here in a way it isn't on technical questions, because behavioral answers earn their depth through reflection.

Brainteasers and estimation problems. Different rules entirely. Covered in their own section below.

The Reasoning-Out-Loud Move

The single most important skill in handling questions you don't know. Most candidates try to reason silently in their head, then deliver a finished answer. This is the wrong move for three reasons.

First, it creates a long awkward pause while you think, and the interviewer can't tell whether the pause is productive thinking or panicked blanking. From the interviewer's seat, both look the same for the first fifteen seconds.

Second, it deprives the interviewer of the thing they actually want to see, which is how you think. The interview is partly a simulation of working with you, and silent thinking isn't useful information about your reasoning process. The interviewer is hiring a brain. They want to watch the brain work, not just see its output.

Third, if you can't land the answer, the interviewer has nothing to work with. A silent two minutes followed by "I don't know" is much worse than a narrated two minutes that lands on the same conclusion. In the second version, the interviewer at least knows how you reason and can score the reasoning even if the answer didn't land.

The right move is to think out loud. Narrate your reasoning. "My first thought is X. But if that's true, then Y. So the answer probably depends on Z. Let me work through it from that angle." The interviewer is now watching you reason, not just waiting for an output. Even if you don't land the answer, they have seen the reasoning, and the reasoning is the credential.

This is unnatural at first. Most education and most prep work reward silent thinking and clean answers. Interview reasoning rewards visible thinking and calibrated answers. The shift is a skill, built through reps. Most candidates need a few mock interviews to get comfortable narrating before they can do it in the real thing.

Buying Time Without Bluffing

Sometimes you genuinely need a few seconds to gather your thinking before you start reasoning out loud. There are acceptable moves and unacceptable ones.

Acceptable moves:

"That's a good question, let me think about it for a moment." Buys up to about eight seconds of thinking time without sounding evasive. Don't overuse, because saying it on every question reads as a stall tactic.

"Let me make sure I'm understanding the question correctly. You're asking about X?" Confirms the question and buys time. Works especially well for behavioral or open-ended questions where the prompt might be ambiguous.

"Let me back up to the fundamentals before I try to answer that." Signals you're going to reason from first principles. Works for technical questions where you want to establish your framework before diving in.

Unacceptable moves:

Filler words to mask the pause ("um, well, you know, I mean, sort of, kind of..."). Reads as nervous and unprepared. The filler isn't actually a pause; it's a stalling sound that broadcasts you're not thinking, you're scrambling.

Asking the interviewer to repeat the question to buy time when you heard it perfectly the first time. Transparent and annoying.

Pivoting to something you do know without acknowledging the original question. The interviewer will redirect you back, and now the pivot looks like an evasion rather than a clean reframe.

The Hardest Variant: The Market Question

"What do you think about [recent specific market event]." This is the question that breaks more candidates at the IB superday than any other.

If you didn't see the event, acknowledge directly. "I missed that one." Then either ask the interviewer to give you a quick overview so you can react, or pivot to a related topic you have a view on. Both are acceptable. "I missed that one. Can you give me the headline? I'd love to react to it" is a fine answer. "I missed that one. I have been thinking about the related question of [adjacent topic], if that's useful" is also fine.

Bluffing about market events is the single worst move in IB interviews because the interviewer is in the market every day and will catch you instantly. The catch is brutal because it confirms you will bluff to clients too, which is disqualifying. A candidate who would lie to a client to cover a gap is a liability the bank cannot afford.

If you saw the event but haven't formed a view, be honest. "I saw the announcement but I haven't formed a view yet. Let me work through what I'd be looking at." Then reason out loud.

If you saw it and have a view, this is the layup. Take a beat, frame it cleanly, deliver. The candidates who rush market answers without structure under-perform candidates who structure even moderately interesting takes.

The prep work that prevents most market question disasters: read the FT and the WSJ for two weeks before any superday. Know the three biggest deals announced that week. Know the three biggest market moves. Have a thirty-second view on each. Most candidates don't do this, which is why even shallow preparation here is differentiation.

The Brainteaser Category

Different rules apply. Brainteasers (estimation problems, logic puzzles, market sizing) test reasoning, not knowledge. The "correct" answer often doesn't exist. The interviewer cares about four things.

How you structure the problem. Do you break it into components.

Whether your reasoning is sound. Does each step follow from the previous one.

Whether you make reasonable assumptions. When you assume the average commuter takes 1.5 trips per day, can you defend it.

Whether you can revise your reasoning if challenged. If the interviewer pushes back on an assumption, do you adjust or do you defend it stubbornly.

The right move: structure the problem out loud, state your assumptions explicitly, work through the math, show calibrated uncertainty about each input, land on a range rather than a point estimate. The range matters because the interviewer knows you're working with rough inputs, and a candidate who lands on "between 8 and 12 million" sounds more sophisticated than one who confidently lands on "10 million" without acknowledging the imprecision.

Most candidates rush brainteasers because they're worried about getting the "right" answer. The interviewer is watching the process, not the output.

The Self-Awareness Test

Beyond the immediate question, the interviewer is testing whether you can accurately gauge what you know.

The candidates who get this right have a clear sense of where their knowledge has depth and where it has gaps. They can say "I'm strong on M&A mechanics but I haven't worked through restructuring specifically" without it sounding defensive or weak. The honesty itself is the credential. Senior bankers respect candidates who can name their gaps because senior bankers know that the candidates who can name them are the ones who will close them.

The candidates who get it wrong fall into two patterns. Some over-claim, projecting confidence on every topic, and the interviewer catches them within five minutes by pushing into a sub-topic they haven't touched. The candidate who claims to know everything always cracks somewhere. Others under-claim, hedging on everything, which signals a lack of confidence that's incompatible with client work where you need to commit to a view even when you're not certain.

The right level is calibrated confidence: confident about what you know with appropriate depth, honest about what you don't with appropriate brevity, willing to reason from the material you have when the gap appears. This sounds like a hard balance to strike, and it is. The reps build it.

When Honesty Becomes a Strength

The interviewer's perspective. Candidates who don't know something and handle it well demonstrate something that candidates who knew the answer can't demonstrate. They show honesty under pressure, reasoning ability without crutches, composure when they're uncomfortable.

The candidate who handles a gap well is sometimes better-positioned than the candidate who happened to know the answer to a question that hit their prep zone, because the candidate who handled the gap demonstrated a harder skill.

The bankers running interviews have all been in the seat where a client asked them a question they didn't know the answer to. The right response in that moment is the entire game, because clients pay for judgment, not encyclopedic recall. The interview is rehearsing for the real version of that moment, and the candidate who shows they have the response is sometimes the candidate who gets the offer over a candidate who answered every prep-zone question perfectly but never showed the harder skill.

The 60-Second Sample

A model dialogue showing the framework in action.

Interviewer: "How would you think about valuing a company where 60% of revenue comes from a single customer?"

Candidate: "I haven't worked through customer concentration adjustments specifically. My instinct would be to apply something like a 15 to 20% discount to the multiple to reflect the risk. The reasoning is that 60% concentration is significant but not existential, so you're pricing in a probability-weighted hit to the cash flow stream rather than wiping out the valuation entirely. But honestly, that's intuition more than a derived answer. I'd want to look at how M&A precedents have priced concentration risk in this sector before I committed to that specific number."

Interviewer: "What if the customer relationship is on a year-to-year contract?"

Candidate: "Then I'd widen the discount, probably closer to 25 to 30%, because renewal risk is real every year and any buyer is going to underwrite the possibility of losing that customer entirely. Same caveat though, that's the direction not a number I'd stand behind without seeing precedents where the same dynamic played out."

About 60 seconds of total dialogue. The candidate didn't have a memorized answer and didn't pretend to. They took a stab at a specific number, explained the reasoning, and explicitly flagged it as intuition rather than derived analysis. When the interviewer added new facts that should change the answer, the candidate updated their estimate without defending the first one.

The signal value of "that's intuition, I'd want to verify" is what makes the response work. It tells the interviewer the candidate can commit to a view under uncertainty, knows the difference between intuition and rigorous analysis, and has the self-awareness to flag which is which. That's the calibration bankers want in juniors. What the response doesn't do: hide behind "I'd present a range" as a non-answer, refuse to commit, or apologize. The candidate takes the swing, names the uncertainty, and moves on.

---

Where to Drill

This is the muscle the Analyst and Associate-level interviewers on HARDO test most directly. The Intern-level interviewer filters for floor competence on the questions candidates prepare for. The harder tiers push past where the candidate is comfortable, into the questions the candidate didn't prep, and the response to discomfort is itself the test. The candidates who handle the unknown well are the ones whose reps trained them to reason in the open, not to pretend they always have the answer.