Consulting Fit Interview: The Stories You Need Ready
Updated: Oct 27
A consulting fit interview can begin with a deceptively simple question: Tell me about a time you led a team.
You have a few minutes to answer. You know what happened, you remember the result, and you have rehearsed the story. But then the interviewer asks why you made a particular decision, what your teammate said in response, and what you would do differently today. Suddenly, the story you thought you knew has become a much deeper examination of how you think, act, and work with others.
At McKinsey, a single personal experience can take up to 20 minutes of an interview. At other firms, behavioral questions may be shorter, but the challenge remains the same: showing what you personally did, why you did it, and what you learned.
The solution is not to memorize dozens of answers. It is to prepare eight genuine stories covering leadership, persuasion, failure, team conflict, initiative, and analytical work — and to understand each one well enough to discuss it from several angles.
I’m Gregoria Fiorentino, lead mentor at Wall Street Guide (WSG) and an alumna of UPenn and a former McKinsey consultant. I went through McKinsey’s on-cycle recruiting myself, and I’ve since guided dozens of students through it. Here’s how to prepare for the fit interview, from understanding what each firm looks for to building stories that hold up under questioning.
McKinsey digs deeper into a single story than most firms, so see how to prepare for its Personal Experience Interview here. Your strongest stories should already show up on paper, and the consulting resume checklist here helps make sure they do.
How the Fit Interview Runs at Each Firm
The questions are broadly similar across consulting firms. Interviewers want to understand how you lead, handle disagreements, respond to setbacks, and make decisions. What changes is how much time they devote to these questions and how deeply they examine each answer.
McKinsey gives candidates the most time to develop a single story. BCG, Bain, and Tier 2 firms typically cover several behavioral questions in a shorter period.
Firm | Where it sits | How long | What to expect |
McKinsey | The Personal Experience Interview (PEI), in every interview alongside the case | About 10 to 20 minutes of a 45- to 60-minute interview | One story, probed with 10 to 25 follow-up questions |
BCG | Inside each 45-minute interview, before or after the case | 10 to 15 minutes (some guides report 5 to 10) | Why BCG, why consulting, then times you led, disagreed, persuaded, or failed |
Bain | Depends on the office: a standalone behavioral interview, or 10 to 15 minutes inside each case interview | 10 to 15 minutes in a case interview; about 45 minutes when it stands alone | The same questions for every candidate in a role |
Oliver Wyman | First-round interviews, as a separate conversation alongside the case | About 15 minutes | Your interest in business, accomplishments, outside interests, and career goals |
L.E.K. | Start or end of each first-round case interview | 5 to 10 minutes per interview | Why L.E.K., what draws you to diligence work, and a time you got something wrong |
Kearney | Usually one of the two first-round interviews; some offices put fit at the start of each | Not published (Kearney gives no firm-wide figure) | Your background and motivation, then teamwork, conflict resolution, and leadership |
Sources: McKinsey, BCG, Bain, and Oliver Wyman careers pages (accessed October 2026); Hacking the Case Interview’s guides to the McKinsey PEI, BCG, Bain, Kearney, and Oliver Wyman interviews, plus its Bain values page; StrategyCase’s McKinsey PEI and L.E.K. guides; CaseCoach’s PEI guide. Interview lengths at BCG, Kearney, Oliver Wyman, and L.E.K. come from coaching guides and office-specific careers pages rather than firm-wide policy.
McKinsey devotes up to 20 minutes of an interview to a single story, more than any firm with a published length here. Kearney publishes no behavioral length, so it is not charted. Among the firms charted here, L.E.K.’s is the shortest.
These are general patterns, not universal rules. Offices can run interviews differently, so confirm the format with your recruiter before preparing for a specific interview.
McKinsey’s interviewing page suggests “coming prepared with two personal examples that demonstrate how you’ve made an impact in each of the four areas below.” Coaching guides such as Hacking the Case Interview and StrategyCase name those areas Leadership, Connection, Drive, and Growth — the labels from McKinsey’s mid-2025 PEI refresh. Our guide to the McKinsey PEI covers each one. The rename was a relabelling rather than a change in substance: Personal Impact became Connection, Entrepreneurial Drive became Drive, Inclusive Leadership became Leadership, and Courageous Change became Growth, so older prep material will use the previous names.
Understanding these areas is useful, but knowing their names is only the beginning. The real work is finding experiences that demonstrate them and being ready to explain the decisions behind those experiences.
What Interviewers Score in Your Answer
A strong behavioral answer is not simply a story with a happy ending. It is an explanation of what you personally did, why you chose that approach, and how you responded when things did not go as planned.
McKinsey’s interviewing guidance asks candidates to explain their specific role, lead with their reasoning, and approach the interview as a conversation rather than a rehearsed presentation. That distinction matters. Interviewers are not merely checking whether your team succeeded; they are trying to understand the thinking that produced the result.
At McKinsey, this can mean answering as many as 25 follow-up questions about a single experience. Hacking the Case Interview’s PEI guide groups these questions into four types:
Factual checks: Does the story hold together? For example, how long did the project take from start to finish?
Decision probes: What was your reasoning? Why did you choose that particular approach?
Interpersonal probes: How did you understand and respond to other people? How did the person or team react to your actions?
Reflection probes: What did you learn about yourself? What would you do differently if you could start again?
Each type examines a different part of the same experience. You might remember the final result perfectly but struggle to explain why you rejected an alternative, how someone responded to your decision, or what you would change today. That is why memorizing a polished answer is not enough. You need to understand the story beneath the answer.
McKinsey interviewers may begin with one or two factual questions before moving to more open-ended probes, which carry much of the scoring weight. At BCG, Bain, and Tier 2 firms, individual behavioral questions typically last about three to five minutes, so interviewers have less time to explore each story. The same preparation principles still apply.
The objective is to know your experience well enough that you can explain it naturally, rather than trying to predict the exact question you will be asked.
Each type asks for something different about the same story, so prepare an answer for all four.
How Many Stories You Need
Eight stories cover the common behavioral questions at every firm in this guide. Six recurring themes come first; the seventh and eighth give Leadership and Growth a second story each, so every one of McKinsey’s four areas ends up with two. The key is choosing the right experiences, not collecting as many as possible.
Leadership: A time you led a group or made a difficult decision.
Persuasion: A time you changed someone’s mind.
Failure: A time you made a mistake and had to recover.
Team conflict: A time you worked through a disagreement.
Initiative: A time you identified a problem and acted without being asked.
Analytical: A time you broke a difficult question into parts and acted on what you found.
Start with one story for each theme. Then identify which other questions each experience could answer. A leadership story, for example, might also demonstrate Drive if you pushed through resistance to achieve the result.
This overlap matters, but it has limits. McKinsey’s first round usually includes two back-to-back interviews, followed by two or three more in the final round. Each interview has its own PEI, and interviewers may focus on one dimension and examine it in depth. StrategyCase notes that most offices will not let you reuse a story at all, and you may be asked about the same trait by two interviewers.
That means you need enough variety to avoid relying on the same experience every time.
Looking at the six example stories below, Connection is covered by the persuasion and team-conflict stories, while Drive can be demonstrated through initiative and the analytical story. Leadership and Growth have fewer dedicated examples.
For that reason, prepare a seventh story that demonstrates leadership and an eighth that focuses on Growth — ideally, an experience in which you encountered a setback, adapted, and emerged with a different approach. This gives you more flexibility, particularly because first-round McKinsey interviewers typically focus on Leadership and Connection.
The goal is not to force every experience into a different category. It is to build a collection of genuine stories that demonstrate different strengths and give you room to adapt to the interviewer.
How to Structure Each Story
A good story has a clear beginning, a meaningful decision, and an outcome you can explain. Without that structure, even an impressive achievement can become a confusing list of events.
Use five parts to organize each experience:
Setup: Explain the situation and the problem in two sentences.
Your role: Clarify what you were responsible for deciding or doing.
Actions: Explain what you did, step by step, and why. Include at least one thing you actually said, where you can recall it.
Result: Describe what happened, using a number where possible.
What you’d change: Identify one thing you would do differently today.
The failure story below (story 3) shows how short every part but the actions can be.
This structure builds on the familiar STAR framework — Situation, Task, Action, and Result — with an additional reflection on what you would change.
The most important part is the actions section. Interviewers want to understand your contribution and reasoning, so spend most of your answer explaining what you did and why you chose that approach.
For McKinsey, where one story may fill the PEI, Hacking the Case Interview suggests an initial answer of about three to four minutes, with two to three minutes devoted to your actions. Keep the other sections short. For BCG, Bain, and Tier 2 firms, where each story is one of several questions, aim for about two minutes and let the interviewer draw out the details through follow-ups.
Every part other than the actions takes less than a minute. The timings follow Hacking the Case Interview’s four-part summary, problem, action, result breakdown; the reflection on what you would change sits inside the result.
A few practical rules will make your answers stronger:
Distinguish your contribution from the team’s. Use “I” when describing your own actions. Use “we” when explaining what the group accomplished collectively.
Explain your reasoning. Don’t just say what you did; explain why you chose that approach over the alternatives.
Use specific details. Numbers, conversations, and concrete decisions make a story easier to assess.
Keep follow-up answers concise. One or two sentences are often enough. Answer the question, then stop.
Be honest about what you remember. If you cannot recall an exact figure, give an approximation and say so. Avoid presenting an uncertain number as precise.
The following six examples show how to build stories around different behavioral themes. They are illustrative outlines, not scripts to memorize. Use the underlying structure to develop stories from your own experience.
1. A Leadership Story Built Around a Decision
A strong leadership story shows a decision that was yours to make, someone on the team who disagreed with it, and what you did to bring that person along. The group can be small, and you don’t need a title, since leading without one can make a stronger example.
Example outline
Setup: A 12-person volunteer tutoring program lost half its tutors by the eighth week of each semester.
Your role: You were the coordinator, and deciding how to address the problem was your responsibility.
Actions: You asked the six tutors who had left the previous semester why they quit. Four said they had been assigned subjects they did not know well. You decided to let tutors choose their subjects. Two of the most experienced tutors objected, arguing that nobody would cover the difficult subjects. You took those subjects yourself for a month and asked the two tutors to train two newer volunteers.
Result: Ten of the 12 tutors completed the semester, up from six of 12.
What you’d change: You would check in with each tutor midway through the semester to identify problems before people decided to leave.
The leadership is not simply in your title as coordinator. It is in the decision you made, the resistance you encountered, and the cost you were willing to take on yourself.
Follow-ups to prepare for:
What exactly did the two tutors say, and how did you respond?
Why did you take the difficult subjects yourself instead of assigning them to someone else?
How did you know by the middle of the semester that your approach was working?
2. A Persuasion Story Where Someone Else Makes the Call
Persuasion is different from leadership. In this story, the decision belongs to someone else. Your task is to understand that person’s concerns and offer something that changes their mind.
This distinction is particularly important for McKinsey’s Connection dimension, which examines how you influence and persuade others. Proving that your idea was right is not necessarily the same as persuading someone to support it.
Example outline
Setup: Your club’s faculty advisor controlled its $9,000 budget. She wanted to spend most of it sending eight members to a national conference, while you wanted to organize an on-campus stock-pitch competition open to the whole club.
Your role: As treasurer, you could propose a budget but could not approve it yourself.
Actions: Your advisor explained that alumni donors expected the club to attend the conference. Rather than arguing immediately, you returned a week later with a one-page plan that addressed her concern: alumni could judge the competition, keeping them involved. You also brought 45 sign-ups collected over the preceding week.
Result: She approved a split budget, with the larger share going to the competition. Fifty-two members competed.
What you’d change: You would ask about her concerns before presenting your own plan.
The plan worked because it addressed the concern behind the disagreement. Your advisor was not simply rejecting your idea; she was trying to protect an existing relationship with donors. Understanding that priority allowed you to propose a solution that worked for both sides.
Follow-ups to prepare for:
What was her objection, in her own words?
How did you know she had genuinely changed her mind rather than simply given in?
Why did her objection make sense from her perspective?
3. A Failure Story With a Real Cost
Failure questions can take different forms. An interviewer might ask you to describe a time you failed or an experience you wish you could do over.
The strongest answer identifies a decision you made that went wrong, explains the consequences, and shows what you changed afterward. A minor inconvenience is not necessarily a meaningful failure, and disguising a strength as a weakness does not demonstrate self-awareness.
Example outline
Setup: You ran your club’s fall recruiting campaign and decided to skip the activities fair, expecting social media to attract enough new members.
Your role: You owned the plan and were responsible for its results.
Actions: On the application deadline, the club had received 40 applications, compared with 85 the previous year. You told the club president that day and asked for an extra week to recruit. You then staffed a table outside the business school for three hours a day with two other members.
Result: The final count reached about 70 applications.
What you’d change: The following year, you would run the activities fair and social media campaign together. You would also write a one-page handoff so the next recruiting lead would not repeat the same mistake.
The numbers make the cost of the decision clear. The handoff shows that you did more than recover from the setback: you changed the process so the lesson could outlast your involvement.
Follow-ups to prepare for:
Why did skipping the activities fair seem reasonable at the time?
How did the conversation with the club president go?
What would someone on your team say you got wrong?
4. A Team Conflict Story Told Through the Conversation
A strong conflict story centers on a disagreement with a peer about the work itself. Neither person can simply settle the issue by authority, so the story depends on how you approached the disagreement and what you said.
Bain, BCG, and Kearney all ask candidates about conflict. Your answer should show that you can challenge an idea without turning the discussion into a personal confrontation.
Example outline
Setup: During a four-person corporate finance project, the teammate responsible for the valuation model refused to change the discount rate after the professor said it was too low.
Your role: You were a teammate without authority over his work, but the model affected the entire group’s grade.
Actions: You spoke to him after class and said, “The professor flagged the rate, and I’d rather fix it with you now than lose points on the whole model. Can you walk me through where it came from?” He explained that he had taken the rate from a textbook example for a different industry. You offered to rebuild the input with him and present the change to the group as a joint decision.
Result: The professor accepted the revised rate, and your teammate asked to work with you on the next assignment.
What you’d change: You would raise the professor’s comment on the day it arrived rather than waiting.
The conversation is the heart of this story. You identified the problem without accusing your teammate of being careless, asked him to explain his reasoning, and offered to work through the solution together.
Interviewers may examine that conversation closely, so prepare to describe what you actually said and how the other person responded. If you cannot explain the interaction, the story risks becoming a general statement about teamwork rather than evidence of how you handle disagreement.
Follow-ups to prepare for:
Why did you speak to him individually rather than raising the issue with the group?
How did he react in the first few seconds?
Would he tell the story the same way you do?
5. An Initiative Story About Something You Started
An initiative story begins with a gap you noticed before anyone asked you to address it. The challenge is to show what you did when obstacles appeared, rather than simply describing the idea you had.
This is central to McKinsey’s Drive dimension. Hacking the Case Interview describes strong examples as involving a challenge in which you took ownership, created a plan, and executed it persistently.
Example outline
Setup: The career center offered resume reviews but no technical interview preparation. Several friends had been eliminated in first-round interviews after struggling with accounting questions.
Your role: You decided to organize a weekly, one-hour peer workshop throughout fall recruiting.
Actions: You had no room, no budget, and a finance club board that worried the workshop would compete with its events. You persuaded a professor to provide a classroom, built the first four sessions using free materials, and offered the finance club co-branding and priority seats for its members.
Result: About 15 people attended the first session, growing to about 40 by week six. The finance club then asked you to run the workshop under its name the following year.
What you’d change: You would document the sessions so someone else could run them after you stepped back.
Each obstacle is paired with an action you took. That connection matters: it shows how you turned an idea into a functioning program, rather than relying on enthusiasm alone.
Follow-ups to prepare for:
Why did you care enough to start the workshop?
Who told you no, and what did you do next?
What did the initiative cost you in time or other commitments?
6. An Analytical Story About a Hard Problem You Solved
An analytical story shows how you broke an open question into smaller parts, gathered evidence, made a judgment call, and used your findings to influence a decision.
Bain asks about the accomplishment you are most proud of, making this a useful story to prepare. At McKinsey, Hacking the Case Interview’s PEI guide states that problem-solving is assessed exclusively through the case interview. You can still use an analytical experience as a Drive story if the emphasis is on how you handled setbacks and kept working toward a solution.
Example outline
Setup: Attendance at your club’s events had dropped by about a third over two semesters.
Your role: You volunteered to find out why.
Actions: You separated the question into two parts: who had stopped attending and why. Sign-in sheets from 20 events showed that most of the decline came from sophomores. Your first survey received only nine responses, so you asked the group-chat administrators for each class to repost it. You received about 30 responses, most pointing to a clash with a required sophomore course whose time slot had changed. You treated the responses as a useful lead because the scheduling conflict could be checked against the course timetable.
Result: The club moved half its events to another evening, and within a semester sophomore attendance had recovered to within about 10% of its previous level.
What you’d change: You would check the course schedule before launching the survey.
The most revealing decision is not the final recommendation. It is why you trusted the evidence you had. You started with limited survey responses, found a way to collect more, and checked whether the explanation matched an independently verifiable scheduling change.
That is the judgment you should be ready to explain.
Follow-ups to prepare for:
How did you decide what to investigate first?
What did the data show that you had not expected?
Where could your conclusion have been wrong?
Which Story Answers Which Firm’s Questions
Story | McKinsey area | Bain angle | Tier 2 question or quality |
1. Leadership | Leadership; Drive if you pushed through resistance | A time you showed leadership | Kearney: leadership and teamwork |
2. Persuasion | Connection; Leadership | Changing the direction of a team | Kearney: teamwork |
3. Failure | Growth; Drive for the recovery | A time you failed, and what you learned | Kearney: a failure, with most of the answer on what changed; L.E.K.: a time you were wrong about something important |
4. Team conflict | Connection; Leadership | A team conflict you managed | Kearney: conflict resolution |
5. Initiative | Drive; Growth if you changed course | Showing initiative and leadership | Oliver Wyman: your accomplishments and experiences |
6. Analytical | Drive if it involved setbacks | The experience you’re most proud of | Oliver Wyman looks for data and analytical skills |
Sources: the McKinsey column follows the area descriptions in Hacking the Case Interview’s PEI guide; the Bain and Tier 2 columns map each story onto the questions and qualities described by Bain’s careers page and Hacking the Case Interview’s guides to the Bain, BCG, Kearney, and Oliver Wyman interviews. The phrasings are paraphrased, not quoted.
Counting secondary areas as well, Leadership gets stories 1, 2, and 4; Connection gets 2 and 4; Growth gets 3 and 5; and Drive gets 5, plus 1, 3, or 6 depending on how you frame each one. That gives every area at least two candidates, but most offices let you tell each story only once. Stories 2 and 4 are Connection’s two main stories, which leaves Leadership with a single story that leads with it, and story 5 is one of Drive’s strongest, which leaves Growth in the same position. The seventh and eighth stories give Leadership and Growth a second story that leads with that area. In short, each area ends up with one story that leads with it and at least one backup.
BCG: Its common questions (a time you led, disagreed, persuaded, or failed) map straight onto stories 1 to 4. BCG’s interview process page lists five qualities its interviewers look for, and we map them as follows: the initiative story for Drive, the analytical story for Intellectual Curiosity and Creative Thinking, persuasion and conflict for Collaborative Mindset, and a failure told plainly for Integrity.
Bain: Bain’s interviewing page tells candidates to “come ready to talk about our operating principles.” Hacking the Case Interview’s Bain values page lists five, and each pairs naturally with one of your stories:
Guided by True North (doing the right thing by clients, people, and communities): a failure you owned plainly.
Passion for Results (delivering outcomes that matter): your analytical story.
Practical and at Cause (bold thinking with a hands-on, ownership-driven approach): your initiative story.
Diverse Teams, One Bain (diverse, inclusive teams drive results): your conflict or persuasion story.
A Bainie Never Lets Another Bainie Fail (stepping in to help a colleague who’s struggling): a story where you stepped in to help a teammate by coaching someone, covering for them, or rebuilding their work with them. Keep it separate from your conflict story, which is already carrying Diverse Teams, One Bain.
How to Answer the Motivation and Background Questions
When a firm asks both “why consulting” and “why this firm,” answer the first with two or three reasons tied to things you’ve done, and the second with firm-specific reasons, at least one of which is true only of that firm. BCG, Bain, L.E.K., and Kearney all ask about motivation, while McKinsey’s PEI usually skips “Why McKinsey?”, according to CaseCoach.
Our guide to answering why consulting keeps the whole answer under 90 seconds. Give the firm answer about the same length, built on three reasons that are specific: a consultant you spoke with, a practice whose work you know, or the way the firm develops new hires. When an interviewer asks only “why consulting,” close it with one line about the firm that names a practice, a person, or a project, as our guide suggests.
For “Tell me about yourself” or “Walk me through your resume,” most fit-interview guides suggest a two- to three-minute answer: a short opening summary, then your most relevant experiences, then a line connecting them to why you want the role. For questions about what you do outside school, which Oliver Wyman asks, name your three strongest interests and give a quick example of each; genuine beats polished.
Say This, Not That
The difference between a strong answer and a weak one often comes down to specificity. General statements can sound polished, but they give an interviewer very little to examine.
Consider these examples.
When describing an action
Say this: “I called each of the three sponsors two days before the deadline and asked what it would take for them to sign.”
Not this: “I reached out to stakeholders to build alignment.”
The first describes what you actually did. The second uses professional language without explaining the action itself.
When reflecting on a mistake
Say this: “Next time, I’d decide before launch what sign-up number would tell me the plan was working.”
Not this: “I learned that communication is key.”
The first identifies a specific change you would make. The second states a broad lesson without showing how it would affect your future decisions.
When explaining why you want to join a firm
Say this: “Talking with two consultants in your Chicago office about their hospital cost work is what made me want to be here.”
Not this: “I love the culture and the people.”
The second statement could apply to almost any firm. The first connects your interest to a concrete experience that the interviewer can ask you about.
Across all three examples, the principle is the same: replace general claims with specific actions, decisions, and reasons. The more concrete your answer, the easier it is for the interviewer to understand your contribution — and the more room the interviewer has to probe it.
How to Practice Your Stories Before the Interview
You have chosen your stories and organized them into five parts. Now, test whether you can explain each experience when someone challenges your reasoning.
Start by creating a one-page grid with your eight stories down the left and the five parts — setup, role, actions, result, and what you’d change — across the top. Use short notes, not full scripts. Pay particular attention to the actions column: each story should include at least three specific things you did and, where you can recall it, at least one thing you said.
Next, practice aloud with a partner. Give them the follow-up questions above and ask them to keep pressing on two things: What did you say? Why did you do that? Their job is to expose gaps in your reasoning, not to help you deliver a smoother answer. If you run out of concrete details after two or three follow-ups, strengthen or replace the story. An impressive two-minute answer may not hold up in a 20-minute interview.
Finally, practice your stories alongside your cases. Both require preparation, so don’t leave either to the last few weeks before your first round.
Our consulting recruiting timeline has this cycle’s dates, and our guide to preparing for a consulting interview covers the case side.
Comments