A behavioural interview in consulting asks you to describe things you have actually done — led a team through a disagreement, changed someone’s mind, recovered a project that was failing — on the premise that past behaviour predicts future behaviour more reliably than stated intent. It runs alongside the case interview at every major firm, is assessed independently, and ends candidacies on its own.
Candidates prepare for it far less than for the case, which is a mistake of allocation rather than understanding. The case is harder to prepare for and easier to improve; the fit round is easier to prepare for and, unprepared, easier to fail.
What the round is actually testing
Three things, and they are not the ones the questions appear to be about.
Whether you would be credible in front of a client. A consultant is placed with clients within weeks. The interviewer is forming a judgement about whether they would be comfortable putting you in a room with a client’s operations director. Everything about how you answer — the structure, the concision, whether you can be interrupted without losing your place — feeds this.
Whether you did the thing you are describing. Not whether you were present when it happened. Interviewers push on the specifics because the specifics are where the difference between participation and contribution becomes visible.
Whether you have judgement about your own behaviour. Candidates who can say what they would do differently, and mean it, read as people who improve. Candidates who defend every past decision as optimal read as people who will make the same mistake twice.
Build a story bank, not a question bank
Preparing one story per anticipated question produces a bank that shatters as soon as a question is phrased unexpectedly. Preparing six to eight deep stories and mapping them to qualities produces one that adapts.
Choose experiences that were genuinely difficult and where your role is separable from the group’s. Then map them:
| Quality commonly assessed | Story A: failing client project | Story B: team disagreement | Story C: process I started |
|---|---|---|---|
| Leadership | ✓ | ✓ | |
| Persuasion and influence | ✓ | ✓ | ✓ |
| Handling conflict | ✓ | ||
| Initiative | ✓ | ||
| Resilience or failure | ✓ | ✓ | |
| Working with difference | ✓ |
The pattern to look for is coverage. If four of your eight stories only serve “leadership” and nothing covers failure, the bank has a hole and you will discover it in the interview.
Two rules while building it:
Include a real failure. Not a disguised strength. “I worked too hard and burned out” is a well-known evasion and interviewers have heard it many times. A story where you were wrong, it cost something, and you can say what you learned is far stronger and much rarer.
Prefer recent and specific over impressive and distant. A detailed account of a six-week project last year beats a vague account of a large achievement four years ago, because the details are what the follow-up questions need.
Use STAR as a check, not a script
STAR — situation, task, action, result — is a completeness test. It should never be audible.
The weighting is what matters, and most candidates get it wrong:
| Element | Time to spend | Common error |
|---|---|---|
| Situation | 15% | Three minutes of context before anything happens |
| Task | 10% | Describing the team’s task rather than yours |
| Action | 55% | Summarised in one sentence |
| Result | 20% | Unquantified, or no counterfactual |
The Action section is the interview. It is where your reasoning, your choices and your role live. A candidate who spends two minutes on the situation and fifteen seconds on what they did has answered the wrong question thoroughly.
Within Action, include the alternatives you rejected. “I considered escalating to the partner, but I thought that would harden the client’s position, so I asked for a meeting with the operations lead first” tells the interviewer that a decision was made rather than that events unfolded.
Quantify the result, and state the counterfactual
A result without a number is an assertion. A number without a comparison is context-free.
| Weak | Strong |
|---|---|
| “The project was a success” | “We delivered two weeks late instead of the six weeks the original plan implied” |
| “Sales improved a lot” | “Conversion rose from 2.1 to 2.8 per cent over the quarter” |
| “The team worked better together” | “Handover defects fell from about six a week to one or two, measured over the following month” |
Where you genuinely have no number, say what would have happened otherwise: “The client had been ready to end the engagement; they extended it by three months instead.” That is a counterfactual, and it does the same work.
Where the result was poor, say so plainly and follow with what you took from it. Interviewers are more suspicious of uniformly successful candidates than of one that went badly.
The follow-ups are the interview
Every prepared story gets probed. Preparing the story and not the probing is the most common preparation failure, and it is visible immediately: the first two minutes are fluent, the next five are not.
Expect these, and rehearse them:
- What was the hardest part of that?
- What would you do differently?
- How did the other person see it?
- What did you say, exactly?
- What if that had not worked?
- Why did you choose that over the alternative?
- What did you learn that you have used since?
Two answers are worth having ready in a usable form. “What would you do differently” — have something real. Saying you would change nothing is either untrue or shows you have not reflected. “How did the other person see it” — a candidate who can state the opposing view fairly demonstrates exactly the quality consulting work requires when a client disagrees with the recommendation.
Delivery counts as content
The round assesses client-readiness, and client-readiness includes how you speak.
Answer in two to three minutes unless invited to go longer. Lead with the point rather than building to it. Stop when you have answered rather than trailing into qualification. Let yourself be interrupted without losing the thread. Match the interviewer’s register — this is a professional conversation, not a presentation and not a chat.
The most useful rehearsal method is recording yourself and watching it back, which is uncomfortable and effective. Check three things: did you get to what you did within forty-five seconds, did you state a result with a number, and did you stop cleanly.
Firm-specific formats
The behavioural round varies more between firms than the case round does. McKinsey runs the structured Personal Experience Interview, which examines one story in depth for twenty minutes and demands a different preparation depth from a round that samples several stories briefly. Other firms run a more conversational round, often blended with “why consulting” and “why this firm” questions.
The firm profiles cover how each of McKinsey, BCG and Bain structures the round, and the fit interview question bank works through the specific questions that recur. For where the round sits in a full preparation plan, see the fit interview hub.
