How IB Interviews Are Actually Graded

Most candidates prepare for IB interviews as if they were exams: learn the material, answer the questions, get the score. But interviews are graded by tired bankers between live-deal calls, compared across a slate of similar candidates, and typically settled in short debrief conversations. Understanding how the grading actually works changes what you optimize for, and it explains why candidates with perfect technicals still lose to candidates with slightly worse technicals and much better delivery.

None of what follows is a universal rulebook; processes differ across banks, groups, and years. But the craft knowledge below describes how evaluation commonly works, and preparing for the common case is the highest-return move you can make. Treat this as the grading rubric you were never shown.

The First 90 Seconds

Interviewers commonly form a working impression very early, often during your walk-me-through-your-resume answer, and then spend the rest of the interview testing that impression rather than building one from scratch. That is not laziness; it is how time-pressed evaluators with dozens of data points operate. The practical implication is that your opening answer carries disproportionate weight.

What registers in that window is not content, it is delivery: communication (clear sentences, a narrative with a direction, no filler spiral), energy (someone who seems glad to be in the room and awake enough to survive the job), and structure (an answer with a visible beginning, middle, and end, delivered inside two minutes). A candidate who opens with a crisp, structured resume walk-through has bought goodwill that cushions a later technical stumble; a candidate who rambles for four minutes has created a hole that even flawless technicals may not climb out of. This is why rehearsing your opener aloud, timed, is the single best minute-for-minute investment in interview prep.

The Evaluation Dimensions

Whether or not a group uses a formal scoresheet, feedback commonly clusters around the same few dimensions, and it is worth self-assessing against each one before you walk in.

• Technicals: not just whether you got the answer, but how you got there. A structured walk toward a mostly-right answer often reads better than a memorized-sounding recitation of the exactly-right one, and how you handle a question you do not know is itself scored.
• Fit and story coherence: does your resume walk-through, your why-banking answer, and your deal pick all tell the same story? Incoherence, such as claiming a passion for healthcare and then discussing a tech deal, reads as manufactured interest.
• Polish and maturity: composure under pushback, concise answers, professional handling of failure and conflict questions, and the general sense that the bank could put you in front of a client in a year.
• Genuine interest: evidence you follow markets and deals without being assigned to, that you have talked to people at the firm, and that your questions for the interviewer are real questions rather than performances.
• The threshold nature of technicals is worth understanding: strong technicals rarely win an offer alone, but weak core technicals commonly end the conversation, because they suggest either low effort or low interest, and both are disqualifying.

Three Strong Answers Beat Ten Mediocre Ones

Here is the asymmetry most candidates miss: interviewers tend not to average your performance; they remember it, and memory keeps peaks and lows, not means. In a debrief hours later, an interviewer will recall the moment you nailed the accretion math under pressure, or the moment you called your view on a deal and defended it, far more vividly than eight adequate-but-forgettable answers. Ten answers at a seven out of ten leave nothing to say about you; three answers at a nine give your interviewer a story to tell in the room.

The preparation implication is to build spikes deliberately. Make your resume walk-through, your deal discussion, and one technical area genuinely excellent rather than making everything uniformly acceptable. This is not permission to neglect fundamentals, because a low moment is equally memorable in the wrong direction: the goal is no disasters plus two or three moments an advocate can quote. When your interviewer has to argue for you later, you want to have handed them the argument.

How Superday Debriefs Commonly Work

Superday decisions are commonly made fast. After the final interview, the interviewers compare notes, in a room, on a call, or over a shared feedback thread, and at many banks the discussion per candidate is a matter of minutes, not hours. Each interviewer typically arrives with a rough verdict already formed, and the debrief is less a deliberation than a consensus check: strong yes, yes, neutral, no.

Two dynamics commonly shape the outcome. The first is the champion effect: a candidate with one senior interviewer actively arguing for them frequently beats a candidate everyone merely liked, because hiring decisions need someone willing to spend capital. The second is the veto effect: a single strong no, especially from a senior person and especially on grounds of attitude or integrity, commonly sinks a candidacy regardless of other scores. The practical consequence of both is the same: your goal in each individual interview is to win that person specifically, either as your champion or at minimum as a non-veto. Playing it safe with everyone produces a slate of lukewarm yeses, which is often not enough in a competitive pool.

This also explains a superday truth that surprises candidates: the interview you think went worst may matter less than you fear if another interviewer is championing you, and a superday where every session felt fine can still end in a rejection if nobody in the room felt strongly. You cannot control the debrief, but you can play for advocates rather than for the absence of mistakes.

Instant Red Flags

Some behaviors function as near-automatic disqualifiers because of what they predict about you as a colleague. Interviewers commonly forgive a blanked technical; they rarely forgive these.

• Blaming others: any story where a teammate, professor, or previous employer is the villain. Even when true, it predicts how you will talk about this team someday.
• Rehearsed-but-hollow answers: a why-this-bank that could be search-and-replaced for any firm, or a script recited so smoothly it collapses at the first follow-up. Fluency is the goal; recitation is a flag.
• Wrong core technicals delivered confidently: missing an obscure question is fine, but confidently botching a fundamental, such as basic enterprise-value or accretion logic, signals either low preparation or low self-awareness, and confident wrongness is the more dangerous trait in an analyst.
• No questions for the interviewer, or questions answerable by the firm's homepage. It reads as no genuine interest, which contaminates everything else you said.
• Arrogance or entitlement: correcting the interviewer ungraciously, negotiating before an offer exists, or visibly ranking this bank below another.
• Dishonesty of any size: an inflated resume line or a claimed deal you cannot discuss. Integrity vetoes are commonly the hardest no in the debrief room.

Self-Grade Your Practice Answers

You can approximate the interviewer's-eye view in your own prep by grading recorded practice answers against a simple rubric. Score each answer from 1 to 3 on four dimensions, for a total out of 12, and be harsh: the point is to see yourself the way a tired banker at 6pm will.

Structure (1 to 3): did the answer have a visible shape, a first-second-third or a past-present-future, and did it end on purpose rather than trail off? Correctness or substance (1 to 3): was the content right, and for behavioral answers, was there a concrete story with a result rather than adjectives? Concision (1 to 3): under two minutes for a first telling, with detail held in reserve for follow-ups? Engagement (1 to 3): would a stranger watching this recording think you want the job, based on energy and delivery alone?

Interpreting the score: an answer at 10 or above is superday-ready; 7 to 9 means rework the weakest dimension and re-record; below 7 means rebuild the answer from an outline. Grade a full mock this way and patterns emerge fast, and the failure is usually concision or structure, not knowledge, which is exactly what the first-90-seconds effect punishes.

How to Prepare

Once you know the grading, preparation stops being about coverage and starts being about the impression your answers leave: openers that land, spikes an advocate can quote, no vetoes. That is a delivery problem as much as a knowledge problem, and it responds to recorded, timed practice.

Keep the knowledge layer sharp in parallel: the bank-tagged technical and behavioral decks in WACC Buddy are the retrieval reps that make sure a core-technical miss never becomes your memorable moment.

1. 01Rehearse your resume walk-through until it reliably lands inside two minutes with a clear arc; it is the answer the first-90-seconds impression is built on.
2. 02Choose your two or three deliberate spikes, typically your deal discussion, one technical area, and one signature story, and over-prepare those.
3. 03Record a full mock interview and grade every answer with the 12-point rubric; rework anything under 10.
4. 04Audit yourself against the red-flag list, especially conflict and failure stories, and rewrite any answer that blames someone else.
5. 05Prepare two or three genuine questions per interviewer that show real research, and drill core technicals daily so confident wrongness is never the risk.

FAQ