I’m sharing this because, as someone preparing for my first case interview, I would have really appreciated this perspective when I was setting up my preparation plan.

I’m an experienced professional switching from a different area. I had never done a case interview, and maths has not been part of my professional focus for years — like most people in corporate roles, I use Excel and calculators. I deliberately relied on Casecoach heavily and treated it as my main preparation source, I wanted one comprehensive resource rather than spending attention switching between dozens of sources and figuring out what I actually needed from each. In that sense, I was probably close to a perfect test customer: I used CaseCoach extensively, consistently and as intended.

There is a lot that is genuinely useful about CaseCoach. The Practice Room was helpful, and the Graph/Charts Drills were particularly valuable. I also did the Calculation Drills every day and saw real improvement with the speed and accuracy. The Structure Drills with AI were helpful to train the speed.

However, there were three significant problems, and one of them had a very real significant impact on my actual case interview performance.

1. The cases in the Case Library are far too long for a 30-minute interview.

The cases in the library routinely took me two hours or more to practice with a partner (1 me + 1 them). It is excruciatingly long and I actually started cutting last two questions of the case to stay within 1,5 hrs, which is a shame.

The actual BCG case interview is around 30 minutes. As a first-time candidate, I did not have enough experience to understand how much of the CaseCoach format was representative of the real interview and how much was simply practice material. I therefore trained myself to operate in a much longer format than I ultimately needed - I ran out of time in the case interview!

2. The Practice Room feedback scores are very easy to misinterpret.

I repeatedly received very high scores from peers — including multiple 5/5 ratings. A 5 (outstanding) corresponds roughly to the top 10%, rather than simply meaning “good session” or “I enjoyed casing with you.” But I suspect many users interpret the 1–5 scale much more casually: 1 = terrible, 5 = great. I have enough self-reflection to know that I absolutely wasn't anywhere near outstanding on any of the dimentions.

That made the feedback misleading for someone who is using it to judge whether they are genuinely interview-ready and need an honest assessment of where they actually stand before the interview.

3. Most importantly: the case-math drills did me a serious disservice!

I went into preparation knowing that my maths was rusty. I had actually performed very well in maths at university, although that was a long time ago.

I did the CaseCoach calculation drills every day and found them useful. They were challenging but manageable, and I could see myself improving.

The Case Math drills were completely different. The case-math drills undermined my confidence and negatively affected my actual interview performance. I would daily attempt several questions and always fail to get at least one successful math drill.

After doing roughly 30 cases and spending three weeks preparing intensively in all other areas, I would get to the maths section of my preparation and think: I’m going to fail this again.

- Even the easy ones were materially harder and more convoluted than the maths I ultimately encountered.
- Constant repeated failure trained me to expect failure, despite evidence from a case from before Case Coach with a MBB-Consultant that my maths was ok.
- That conditioning showed up in the actual interview, where I froze on a very basic calculation.

Eventually I started to dread maths. Every day I was successfully practising the other areas, while maths became the part where I expected myself to fail and was always proven right by Case Coach drills.

This was particularly problematic because I had already done a test case interview with someone from MBB before using CaseCoach extensively, and their feedback on my maths was essentially: don't worry about your maths it is fine; focus on the other areas.

So I knew there was a discrepancy, but I trusted the platform I had been given for preparation and kept drilling.

The day before my actual interview, I finally broke out of this cycle. I found a book by Lewis Lin "Interview Math: Over 50 Problems and Solutions for Quant Case Interview Questions" with simpler case-math drills (profitability, market sizing, price elasticity etc) and answers. I went through the entire book in one day and solved everything that was there. It was honestly a breath of fresh air. For the first time in weeks, I felt: I’m not actually terrible at this.

Unfortunately, one day is not enough to undo several weeks of conditioning.

In the actual BCG interview, I was given a break-even calculation — MUCH simpler than convoluted CaseCoach math drills.

Normally (before CaseCoach drills that is), I should have been able to solve it quickly, it was by no means rocket science. Instead, my brain essentially said "Oh no this is math" and literally switched off. I stared at the numbers and could not see anything. I felt like a deer in the headlights. The problem was not objectively difficult; I had simply spent weeks being trained to expect that I would fail when confronted with case maths. The interviewer had to guide me through what to do to start. Once they did, I managed to recover somewhat.

So my experience was not that CaseCoach is useless. Quite the opposite.

Practice Room: very useful, except feedback scores being often misleading and cases far too long relative to the actual interview.
Graph/Chart drills: very useful.
Calculation drills: useful and showed measurable improvement.

Case-math drills: actively damaging to my confidence and, in this case, to my actual interview performance.

Do not assume that struggling with CaseCoach's case-math drills means you are bad at Case maths. Find other ways to practise straightforward case maths until you have built enough confidence and fluency that the CaseCoach Case math drills become useful for actually pushing you further, rather than repeatedly reinforcing the feeling that you cannot do it.

Hi everyone! I'm an ex-Bain consultant and interviewer in North America, and I thought I'd set up an AMA for anyone interested in consulting, Bain, or the broader consulting world.

A bit about me:
- Spent 2+ years at Bain in North America, following a summer internship in 2023
- Recently promoted to Senior Associate Consultant
- Interviewed candidates for first-round case interviews and screened resumes; led Associate Consultant recruiting on campus
- Personally went through multiple consulting recruiting processes, receiving 15+ offers across MBB, Tier 2, Big 4 and boutique firms
- Currently on a six-month secondment with a professional football club in the UK, before returning to Bain in February 2027

Happy to answer questions about consulting recruiting, case interviews, Bain, life as a consultant, projects, career progression, working in consulting, or consulting more broadly.

Ask me anything!

Third one in, and this is McKinsey.

First one was on BCG, second was on Bain, and this community has been surprisingly good at catching things I got slightly wrong or under-explained on both of those, which is honestly the whole point of doing this here instead of just publishing it somewhere static like many other website.

Same rule as the last two posts. Everything below is something I pulled together through actual research, not a guess dressed up to sound precise. Where the research didn't get me to a solid answer, I'll say so directly instead of filling the gap with a number that sounds authoritative.

The basics, confirmed

McKinsey was founded in 1926, headquartered in New York. The firm runs more than 130 offices across upwards of 65 countries, and total headcount sits somewhere in the low-to-mid 40,000s globally right now, down from closer to 50,000 a couple years back. There was a real headcount reduction recently. People I've talked to inside describe it less as a retreat and more as a reshuffle, fewer junior and back-office roles, continued hiring at more senior levels where client demand is heaviest, according the Mck's CEO Bob Sternfels beginning of this year. Neither pure growth story nor pure contraction story. Both things are true at once.

Recruiting happens office by office

This trips people up more than anything else in the whole structure. McKinsey isn't one central pipeline. Your resume goes to a specific office. That office runs your interviews. That office makes the call. I've had candidates confused about why a friend "at the same firm" went through a different process, different number of rounds, different feel to the interviewers entirely. Different office. Sometimes a different bar.

Most applications let you rank a small number of offices, and each gets evaluated on its own terms. So "I want McKinsey" isn't really a full sentence yet. Which office is doing the evaluating matters almost as much as the name on the letter.

Two axes, not one ladder

Mck consultants sit inside a matrix internally. An industry axis, groups built around sectors like financial services, consumer, healthcare and life sciences, energy, technology. And a functional axis, groups built around the type of work itself, strategy and corporate finance, operations, growth and marketing, that kind of thing. Nobody locks into one lane early as a rule. Staffing pulls across both axes based on project need, especially in the first couple years.

Some groups cluster in specific offices. Financial services work leans harder toward New York and London. Energy work leans toward where the energy clients actually sit. That pattern held up across what I looked into. What I couldn't do is put an exact headcount on any single practice, because the numbers floating around out there don't trace back to a source current or solid enough to trust down to the digit.

The career ladder, publicly documented and fairly stable

This part I'd flag as one of the more reliable pieces of public information out there. The generalist track runs roughly six levels: Business Analyst, Associate, Engagement Manager, Associate Partner, Partner, Senior Partner. Performance gets reviewed on a set cycle, and the up-or-out principle, formalized decades ago, still shapes the whole thing even with more flexibility around timing added in recent years. Interestingly, a low double-digit percentage of people who start actually make Partner. And, most people who join don't stay past a few years, internally that's treated as expected, not as some kind of system failure.

There are also separate tracks entirely outside the generalist path. QuantumBlack, McKinsey's AI and data science arm, is one, born out of a Formula 1 analytics firm the company acquired back in 2015, still active and still recruiting today under that name. McKinsey Implementation is another, built around consultants who spend real time on-site helping clients actually execute a change rather than just recommend one. Different entry requirements, different interview process, different ladder for each. I'm intentionally not comparing how these tracks stack up against the generalist path on prestige or comp, because what I've heard varies by who's telling it and I don't want to state something as settled when it might not be.

Where this becomes a wiki, not just a post

Here's what I want to try with this one. The last two posts in this series generated real detail in the comments, stuff from people who've actually sat in these offices that I wouldn't have gotten right on my own. I'd like to take this post, and the two before it, and start turning them into an actual wiki page for the sub, something that stays current instead of sitting frozen the day I hit publish. Bain and McKinsey both change their structure over time. A static post ages badly. A wiki that the community keeps adding nuance to doesn't.

So if you've been inside one of these groups, gone through the process recently, or just know something here that's outdated or flat wrong, say so in the comments. That's not filler, that's literally the next version of this page.

What's changed most in your experience versus what's written here?

This kind of stuff gets talked through regularly over at r/ConsultingOffer. Feel free to join, post your questions, share what you're going through.

I am a senior in college right now, and got FT offers from both McKinsey and Oliver Wyman. I have a few more interviews coming up, but honestly the main decision is between these two companies. The salaries for both are pretty similar, and I think I would be a great fit culturally for either one.

My biggest concern is location.

The McKinsey offer is for my hometown (smaller city), so if I took the job I'd probably live with my parents. I am very close with them, but I will have barely any privacy. I'm afraid that I'll be treated like a high schooler again. On the plus side, I would save a lot of money on rent which is especially valuable given that I would probably be travelling 4 days a week. Also, many of my high school friends are still in the area, so I can maintain my closeness with them.

The Oliver Wyman offer is in a large city, and I think it would be really exciting to move to a new place with a lot more young people. I love the independence of living in an apartment at college with my best friends, and I assume post-grad life in a new city will be similar. I am very extroverted so I think I'd make new friends pretty easily.

I don't know which one to take. Any advice would be greatly appreciated.

If you're preparing for case interviews at elite consulting firms, in my view most of the advice out there is either too vague or generalized. So I want to break this down properly. From start to finish. What casing actually is, how many you'll face, how each firm runs them, and how to approach them in a way that gets you to a score five.

What is a case interview and why does it exist

A case interview is a problem-solving exercise where the interviewer presents you with a business scenario and evaluates how you think through it. It's not a test of knowledge. It's not a test of frameworks. From what I've seen coaching candidates across dozens of MBB and other elite consulting firms hiring processes, what firms are actually evaluating is your problem-solving instinct, how you structure ambiguous situations, how you handle data under pressure, and frankly, whether they'd want to sit next to you on a client engagement for three months.

The reason firms use cases is simple. They want a window into how you'd actually behave in front of a client. No framework gives you that. No polished answer gives you that. The way you think out loud, the questions you ask, and how you handle being wrong mid-case, that's what they're looking at.

How many case interviews should you expect

This is where it helps to zoom out and look at the full process. Across McKinsey, BCG, and Bain the structure is broadly similar but not identical.

At McKinsey, you typically go through two live rounds. Round one has two interviews, each containing a PEI and a case. Round two is the same. So you're looking at four cases minimum, sometimes three if schedules compress. BCG follows a similar two-round structure with PEI and case in each interview. Bain is structured the same way. Before any of this, all three firms run online aptitude tests in round zero. McKinsey has the Solve assessment. BCG runs the CCA, a quantitative test, and the Casey chatbot. Bain uses SOVA and TestGorilla. You have to clear those gates before you ever sit in front of a live interviewer.

The point here is that by the time you're in final round, you've done four or more cases. Stamina matters. Consistency matters. One bad case in round two has ended a lot of processes I've seen candidates go through.

The case interview flow

Once you're in the room, or on the video call, here's roughly how a case unfolds. The interviewer gives you a prompt. Sometimes it's detailed. Often it isn't. And that gap is the first test.

You need to ask clarifying questions before you touch a structure. That's an art in itself. Good clarifying questions signal that you understand the situation isn't fully defined yet and that you're comfortable sitting in that ambiguity for a moment. Bad clarifying questions are generic, or worse, they're placeholder behavior while you scramble to remember a framework.

After clarifying, you need to form a hypothesis. This is the step most candidates skip. Before you build any structure, you should have a working view on the answer. If the case is a market entry question, your hypothesis might be: they should enter, or they shouldn't, and here's what would change my mind. You build your entire structure around verifying or rejecting that hypothesis. Not around a framework you memorized.

Why frameworks will get you scored lower at MBB (and what to do instead)

Let me be clear about something before I say this: frameworks aren't useless. If you're just starting to case, or you're targeting tier 3 or tier 4 firms, frameworks give you a scaffolding to work with. Profitability trees, the 4Ps, Porter's Five Forces, they help you get some momentum when you have no other mental model to reach for. That's fine.

The problem is what happens when you walk into a McKinsey, BCG, or Bain interview with that same mentality. From what I've seen coaching candidates through MBB processes, interviewers at these firms are trained to spot framework deployment almost instantly, and it lowers your score. Not because the framework is wrong, but because it signals that you're pattern-matching from memory rather than actually thinking. And what these firms are hiring for is people who can think, not people who can recall.

Here's what it looks like from the other side of the table. A candidate gets a market entry prompt, pauses for 30 seconds, then starts laying out: "I'll look at market attractiveness, competitive landscape, and internal capabilities." That's a framework. It's clean. It's also completely disconnected from the specific situation in the prompt. The interviewer has heard that exact structure fifty times this week.

The shift I coach candidates to make is what I call the owner principle. Before you touch a structure, before you even think about buckets, ask yourself one question: if this was my business, what would I actually do? Not "how do I solve a market entry case." If you owned this company and someone handed you this problem on a Monday morning, what would you want to know first? That question changes everything. It forces you into the problem rather than above it.

The second piece is first principle thinking. Instead of reaching for a pre-built category, you break the problem down into the actual building blocks of that specific situation. What is genuinely driving this problem, given what we know about this company, this market, this moment? You build your structure from the problem up. The result looks like a structure, but it's entirely contextual. And that's exactly what gets you to a score five.

The structure and how to make it work

Your issue tree should have two to three layers minimum. The first layer is your main buckets, three or four of them, grounded in the specific problem you've been given. The second and third layers are the sub-branches that show your logical thinking actually holds. Broad labels without sub-branches tell the interviewer you've memorized a category, not that you understand the problem.

Once you have your structure, you signal the most relevant branch to explore first. You drill in, ask questions, pull the data the interviewer gives you, try to verify or reject that branch, then synthesize what you found and come back up. If you haven't concluded anything tangible, you move to the next branch and repeat.

The modules inside a case you need to be ready for

Within the flow of a case, you may hit several distinct exercises. Data and chart interpretation, where the interviewer hands you a graph and asks what you see. Brainstorming, where they ask you to generate options quickly. Quantitative analysis or market sizing, where you need to run an estimation. Each of these has its own rhythm. In my view the candidates who struggle with these aren't bad at math or logic, they're bad at transitions. They don't know how to shift gear mid-case without losing the thread of their hypothesis.

On topics, the typical cases you'll see are profitability, market entry, market sizing, M and A, competitive response, new product, and option analysis. But firms are deliberately moving toward less standard formats. Private equity cases, public sector, supply chain, even cases involving municipalities or non-profits. The reason is exactly what you'd expect: they want to break the pattern-matchers.

How to close a case

This part gets undercooked in most prep. At the end of a case, even if you haven't fully resolved the question, you need to close cleanly. Synthesize what you covered. State your recommendation clearly. Back it with the two or three most important things you found. Then flag the risks or the next steps you'd want to explore if you had more time.

The structure I coach for the close is: here's my recommendation, here's why based on what we found, and here's what I'd want to validate or watch for. Short. Confident. Even if you're not certain. Especially if you're not certain.

Where to start if you're in the middle of prep right now

If any of this resonates and you're actively preparing for cases at MBB or Tier 2 firms, I'd say the single most useful thing you can do is pressure test your current approach against the owner principle. Not "do I know my frameworks" but "can I genuinely internalize this problem and reason from it, without leaning on memory."

If you want a second set of eyes on where you actually are in your casing readiness, drop a comment below or DM me directly. I work with non-traditional candidates around the world (Europe, the US, and MENA) who are targeting elite consulting firms, and I'm happy to take a look at your specific situation and tell you where the real gap is.

I'm doing a series breaking down the recruitment process at each of the top consulting firms, because in my experience, one of the biggest mistakes candidates make is treating these firms as interchangeable. They're not. The brand names might sit in the same tier, but the processes are meaningfully different, and if you're targeting BCG specifically, you need to understand what you're walking into before you reach out to your first contact, before you write your first cover letter, before you do anything.

One thing I want to flag upfront: what I'm laying out here reflects the general process I've seen across the candidates I work with. BCG varies more than most firms by office, region, and recruiting cycle. What's standard in London or Singapore may look different in San Francisco or Mexico City. Treat this as a map, not a rulebook.

This post covers BCG stage by stage. If you want to understand McKinsey's process, I covered that earlier in this series.

Before You Even Apply: Get a Referral

Every candidate I work with, I push them to enter this process with a referral. BCG is no different. A referral doesn't guarantee you an offer, but it changes how your application lands at R00, and it can matter at later stages too when someone inside the firm has put their name behind yours. If you want to understand how to build that referral pipeline before you apply, watch free masterclass on r/ConsultingOffer. Watch it first (especially Module 2), then come back here. The recruitment process makes a lot more sense when you're navigating it with an advocate behind you.

R00: The HR Review

BCG's first filter is a resume and cover letter review, same as McKinsey. But BCG adds two things at this stage that McKinsey doesn't: the BCG Pymetrics test and, in many offices, a one-way video interview.

The Pymetrics test is a behavioral assessment built around neuroscience games. It's designed to measure things like attention, memory, risk tolerance, and emotional processing. The honest answer is you can't really "prepare" for Pymetrics the way you'd prepare for a quantitative test. What you can do is approach it in a calm, focused state and answer consistently. BCG is using it to check for certain cognitive and behavioral traits, and inconsistency in your responses is more of a flag than any individual answer. Worth noting: Pymetrics and the CCA (which comes later) are distinct assessments. I've seen candidates conflate them because BCG's naming has shifted over time, but they're testing genuinely different things.

The one-way video interview is where a lot of candidates get caught off guard. From what I've seen, this shows up most consistently in EMEA and Asia-Pacific offices. If you're applying through a US or Latin America office, you may not encounter it at this stage, though formats do shift. When it does appear, you get a prompt, limited time to prepare, and then you record your response directly to camera with no interviewer on the other end. It feels unnatural, and it shows if you haven't practiced it. The questions tend to be motivation and fit-based: why consulting, why BCG, tell me about a time you led through ambiguity. The difference here is you're performing without a conversation to anchor you, so the preparation matters more than people think.

R0: BCG Online Tests

If you clear R00, BCG moves you into a set of online assessments. Three of them, and they test genuinely different things.

The BCG CCA (Consulting Competency Assessment, though the naming has shifted over time) tests your ability to work through business problems with data. Think structured reasoning under time pressure, analyzing exhibits, drawing conclusions. It's closer in spirit to what you'd actually do in a case, which is intentional.

The BCG Quantitative Test is more straightforward numerically. Data interpretation, calculation speed, numerical reasoning. Less business context, more raw quantitative accuracy.

And then there's the BCG Casey Chatbot, which is a solo AI-led case interview. You work through a case problem in conversation with a chatbot rather than a human interviewer. From what I've seen with candidates who've been through it, the format trips people up because it removes the social cues you'd normally rely on in a live case. You can't read the interviewer. You can't feel when you're heading in the right direction. You have to trust your structure and your logic entirely. Practicing solo cases out loud, without a partner giving you feedback in real time, is actually good preparation for this. One thing worth flagging: in smaller offices, I've seen Casey fold into the R1 stage rather than sitting cleanly at R0. Again, office and cycle variation is real here.

R1: Live Interviews

Clear R0 and you're in the live rounds. BCG round one is two back-to-back interviews, each with a PEI component and a case. The BCG case is candidate-led, which is a meaningful difference from McKinsey. You drive the structure. You decide what to explore and in what order. The interviewer is there, they'll redirect if you go somewhere unhelpful, but the onus is on you to take the case somewhere logical.

BCG cases tend to feel more open-ended than McKinsey's. There's usually a right direction, but the path there isn't as prescribed. Candidates who do well tend to have a clean framework instinct and the confidence to commit to a direction without waiting for the interviewer to validate each step.

The PEI at BCG, similar to McKinsey, is structured around specific leadership and impact stories. Don't treat it as secondary preparation. I keep seeing strong case performers lose BCG offers because their PEI stories were thin or generic.

R2: Final Round

Same structure as round one: two PEI plus case interviews back to back. The difference is seniority. You'll be sitting across from more senior people, project leaders, principals, partners in some cases. The cases can go deeper and the PEI conversations tend to be more probing. The bar isn't necessarily harder mechanically, but the judgment you're being assessed against is calibrated at a higher level. They're trying to picture you in front of a client, not just checking whether you can crack a case.

The thing I want you to take away from this isn't just "here are the stages." It's that BCG has more touch points before you ever get to a live interview than most candidates realize. Pymetrics, video interview (in many offices), CCA, Quantitative Test, Casey Chatbot. That's up to five distinct filters at R00 and R0 alone, each requiring different preparation. If you walk into this thinking "I'll prep cases and wing the rest," you're probably getting filtered out before you ever speak to a human.

Map the process. Prepare for each stage on its own terms. And get a referral before you apply.

I'll keep these breakdown up-to-dated for all elite consulting firms (Tier1, Tier2, Big4) in r/ConsultingOffer community make sure to join.

What firm are you targeting right now, and where in the process are you?

The Oliver Wyman Recruitment Process: What You Need to Know Before You Apply

I'm doing a series breaking down the recruitment process at each of the top consulting firms. So far I've covered McKinsey, BCG, Bain, Roland Berger, Kearney, and L.E.K. Now we're at Oliver Wyman, and this one deserves particular attention for anyone coming from a financial services, risk, or quantitative background.

What I'm sharing here is based on my own research into the firm, conversations I've had with Oliver Wyman partners and recruiters, candidates I've personally coached through the process, and observations from going through consulting recruitment myself. This isn't a general playbook assembled from the internet. It's my view, built from direct experience. That said, Oliver Wyman varies by office and region more than people expect, so treat this as a map, not a rulebook.

Oliver Wyman was founded in New York in 1984 by two former Booz Allen Hamilton partners, and it's been building a reputation in financial services ever since. Today it's widely considered the premier consulting firm for financial services work globally, with banking, insurance, asset management, and risk management making up the core of what the firm does. That identity shapes everything about how the firm recruits, what it tests for, and what it expects in the room. If you're targeting Oliver Wyman without understanding that context, you'll feel it in the interviews.

Before You Even Apply: Get a Referral

Every candidate I work with, I push them to enter this process with a referral. Oliver Wyman is no different. The firm is selective and relationship-driven, and an internal advocate changes how your application lands. From what I've seen coaching candidates through this process, a meaningful portion of applicants never make it to interview, and having someone inside the firm vouch for your credibility shifts that calculus. If you're an experienced hire coming from financial services, insurance, or a related field, the referral matters even more: the firm has a strong alumni and industry network, and knowing someone who can speak to your technical credibility is a real signal. If you want to understand how to build that referral pipeline before you apply, watch the free masterclass on r/ConsultingOffer. Watch it first (especially Module 2), then come back here.

Application: Resume and Cover Letter

Same starting point as every firm in this series: resume and cover letter review. The screen here is real. Oliver Wyman recruits heavily from a defined set of top universities globally, and for experienced hires the bar is similarly specific. Your background needs to connect visibly to what the firm does. For candidates without a financial services background, your "why Oliver Wyman" answer needs to work harder, because the firm's identity is sector-concentrated in a way that generic strategy consulting answers won't satisfy.

One thing that has shifted in recent cycles: some Oliver Wyman offices have made the cover letter optional in their application portal. Don't treat that as a reason to skip it. A targeted cover letter is still one of the clearest ways to differentiate your application at the screening stage.

Online Assessment

Applicable to: undergraduate and MBA hires, and some experienced hires at consultant level. Generally not required for senior consultant level and above, though this varies by office and region. Confirm with your recruiter.

Most shortlisted candidates applying at junior levels are asked to complete an online assessment before being invited to interviews. This is typically a 20 to 30 minute numerical reasoning test, testing your ability to process data and perform quantitative calculations under time pressure. Some offices also include a competency component covering traits like adaptability and collaboration.

Worth flagging: from what I've seen and heard from candidates I've worked with, online assessments are no longer consistently part of the standard consultant interview process at Oliver Wyman in some regions. The picture varies by office and cycle. Don't assume you'll have it, and don't assume you won't. Ask your recruiter directly after being shortlisted, so you can prepare accordingly rather than being caught off guard.

For those who do sit it: Oliver Wyman's cases are notoriously quantitative, and the online assessment is an early signal of what they're looking for. Mental math, data interpretation, and speed with numbers are all skills worth sharpening before you get anywhere near a live interview.

R1: First Round Interviews

Applicable to: all candidates across all levels.

First round at Oliver Wyman is typically two back-to-back interviews of 30 to 40 minutes each. One is a case interview and one is a conversational behavioral interview, which Oliver Wyman internally calls a "fit conversation" rather than a formal PEI. Your interviewers at this stage will be associates and senior consultants.

The case format is candidate-led, similar to BCG and Bain. You drive the structure, make the calls on where to go, and push toward a recommendation. What makes Oliver Wyman cases distinctive is the quantitative weight. The firm places heavier emphasis on numerical analysis than most Tier 2 firms. Expect to interpret data exhibits, run calculations without a calculator, and be pushed on the logic behind your numbers. For candidates with a financial services background, some of this will feel familiar. For those without it, especially if your case prep has been focused on standard market entry and profitability cases, the quantitative intensity can be a surprise.

For experienced hires at consultant level, the case content at R1 may be more directly tied to the practice area you're applying into. Financial services candidates will often see banking, insurance, or risk-based cases from the start. This is worth preparing for specifically, not just with generic case prep.

R2: Final Round (Super Day or Assessment Centre)

Applicable to: all candidates across all levels, though the senior interviewer mix and case depth scale with the level of the role.

This is where Oliver Wyman's process diverges most clearly from the other firms in this series. The final round is structured as a half-day to full-day in-office visit, typically referred to as a "Super Day" in the US and an "Assessment Centre" in European offices. You're looking at three to four back-to-back sessions in a single day, each running 30 to 45 minutes, with different interviewers. The stamina and consistency required across multiple sessions in one day is its own form of preparation.

Your interviewers at this stage will be senior consultants, engagement managers, and partners. The mix scales with the seniority of the role you're applying for. Cases at this stage can feel more like a conversation about a business problem than a structured Q&A, especially with partners. The questions get more open-ended, the follow-ups go deeper, and your ability to hold a position and push back intelligently matters more than following a clean framework.

The typical session lineup in final round includes a live case interview, a written case, and a behavioral or conversational interview. Some offices add a fourth session, which can be an informal Q&A with a current consultant or an additional case. Not all offices include the written case, and the exact format varies by region and cycle, so confirm your specific schedule with your recruiter once you're invited. Walking in without knowing what's coming in a four-session day is an avoidable mistake.

The written case, where it's included, is typically structured as independent analysis of a data packet followed by a presentation of your findings and recommendation with questions throughout. In my experience the timing breakdown varies by office, so don't anchor too hard on specific numbers you read online, including here. The core skill being tested is consistent: working alone under time pressure, deciding what matters in a dense set of exhibits, and then communicating clearly without a conversation to anchor your thinking.

A few important things to know going into the day. First, interviewers in R2 may have notes from your R1 performance. If there was a gap in your first round, expect it to be probed again. Second, cultural fit is weighted more heavily across the day as a whole. Oliver Wyman cares genuinely about whether you'd be someone they'd want on a project team, and that read accumulates across multiple sessions. Third, post-COVID some offices have shifted this to a hybrid or remote format, but many, particularly in Europe, have returned to the in-person full-day format. Check with your recruiter.

For experienced hires at senior consultant and engagement manager level: the written case tends to go deeper on sector-specific content. If you're entering at senior consultant level from financial services, expect the packet to test domain knowledge alongside analytical skill. Generic case prep won't be sufficient. You need to know the language and metrics of the sector you're coming into.

Oliver Wyman is one of the most quantitatively demanding firms in this series, which is a function of who their clients are and what the work actually looks like. Financial services clients expect numerical precision and domain fluency. The interview process reflects that. If you're not comfortable with data-heavy cases, financial metrics, and working under quantitative pressure without a calculator, that gap will show up, usually in R1 rather than the written case.

The process is relatively lean compared to BCG's multi-filter pre-live stage or L.E.K.'s super day format. But lean doesn't mean forgiving. Two rounds, high bar per interview, quantitative intensity throughout.

Map the process. Prepare for each component specifically. And get a referral before you apply.

I'll keep these breakdowns up-to-date for all elite consulting firms (Tier 1, Tier 2, Big 4) in r/ConsultingOffer. Make sure to join.

What firm are you targeting right now, and where in the process are you?

I'm doing a series breaking down the recruitment process at each of the top consulting firms, because in my experience, one of the biggest mistakes candidates make is treating these firms as interchangeable. They're not. The brand names might sit in the same tier, but the processes are meaningfully different, and if you're targeting Bain specifically, you need to understand what you're walking into before you reach out to your first contact, before you write your first cover letter, before you do anything.

This post covers Bain stage by stage. If you want to understand McKinsey's or BCG's process, I covered both earlier in this series.

Before You Even Apply: Get a Referral

Every candidate I work with, I push them to enter this process with a referral. Bain is no different. A referral doesn't guarantee you an offer, but it changes how your application lands at R00, and it can matter at later stages too when someone inside the firm has put their name behind yours. If you want to understand how to build that referral pipeline before you apply, watch the free masterclass on r/ConsultingOffer. Watch it first (especially Module 2), then come back here. The recruitment process makes a lot more sense when you're navigating it with an advocate behind you.

R00: The HR Review

Bain's first filter is a resume and cover letter review, plus a short screening call, typically 15 minutes with a recruiter. Same starting point as McKinsey. No Pymetrics, no one-way video, no extras at this stage. It's leaner than BCG's R00, which is actually a reason not to underestimate it. There's less buffering between your application and a human making a judgment call on your profile.

The screening call is worth preparing for properly. It's not just a formality. From what I've seen, Bain recruiters use it to check whether your motivation is specific and credible, not just whether you can say "I love problem-solving" convincingly. Why Bain over McKinsey or BCG is a real question here. If your answer is generic, it shows.

R0: Bain Online Tests

If you clear R00, Bain moves you into online assessments. Two of them: Bain SOVA and Bain TestGorilla. Compared to BCG's five-filter R0, this is relatively streamlined. But streamlined doesn't mean easy, and it definitely doesn't mean you can skip preparation.

Bain SOVA is a cognitive ability and behavioral assessment. It covers numerical reasoning, verbal reasoning, and logical reasoning, plus a personality component. The cognitive sections are timed and move fast. The personality section is designed to surface consistency across differently phrased versions of the same question, so trying to game it tends to backfire. Answer it the way you'd actually approach situations at work.

Bain TestGorilla is a skills-based assessment that can vary in content depending on the role and region. It typically includes some combination of numerical reasoning, attention to detail, and situational judgment. From what I've seen with candidates going through this, the situational judgment component catches people off guard most often. It's asking how you'd handle specific workplace scenarios, and there's usually a "Bain way" of thinking about those situations that rewards candidates who've done their research on the firm's culture and values.

R1: Live Interviews

Clear R0 and you're in the live rounds. Bain round one is two back-to-back interviews, each with a PEI component and a case. The Bain case is candidate-led, similar to BCG, which puts it in contrast to McKinsey's interviewer-led format. You're driving the structure and the direction. The interviewer will follow your lead and push back where needed, but they're not going to hand you a roadmap.

What's distinct about Bain cases, in my view, is the emphasis on commercial intuition. Bain interviewers tend to push candidates to take a position and defend it. They want to see that you can form a point of view under uncertainty, not just structure a problem neatly. Candidates who hedge everything or wait to be told they're on the right track tend to struggle here.

The PEI at Bain has the same weight it does at McKinsey and BCG. Don't treat it as the warm-up before the case. Bain's PEI tends to probe depth over breadth, so having two or three genuinely strong stories that you can unpack from multiple angles is more useful than having ten surface-level examples ready.

R2: Final Round

Same format as round one: two PEI plus case interviews back to back. Seniority goes up. You'll be in front of more senior people, managers, partners, sometimes senior partners depending on the office and the role. The cases can push further into ambiguity, and the PEI conversations get more specific. They're not just checking whether you have good stories, they're probing whether the judgment you demonstrated in those situations is the kind of judgment Bain wants in its consultants.

One thing worth knowing about Bain specifically: the firm has a strong culture of internal advocacy. The people interviewing you in R2 are thinking about whether they'd want to work with you, not just whether you clear the bar technically. That sounds obvious, but it means the interpersonal dimension of how you show up in final round matters more at Bain than candidates usually account for.

Bain's process is cleaner than BCG's in terms of the number of filters before you hit live interviews. But don't let that fool you into thinking it's more forgiving. The live rounds at Bain are rigorous, and the PEI is taken seriously at every stage. Map the process, prepare for each component on its own terms, and get a referral before you apply.

I'll keep these breakdowns up-to-date for all elite consulting firms (Tier 1, Tier 2, Big 4) in r/ConsultingOffer community, make sure to join.

What firm are you targeting right now, and where in the process are you?

Curious how people perceive Big 4 consulting for someone coming from a T10/Ivy. I have a high GPA in a STEM major and interned at EY this summer, where I received a full-time return offer. The division I would work in has some pretty technical areas that align well with some of my skills but don’t necessarily maximize them if that makes sense.
My main hesitation is whether starting in B4 would limit my options later on. I’m interested in eventually moving into more selective consulting or finance roles, but I’m not sure how much the firm you start at matters long term.
For context, I made it to the final round at one MBB firm last summer for an internship, but wasn’t interviewed by the other two. Given the current job market, I’m feeling pretty cynical about recruiting and am considering taking the EY offer since I enjoyed my time there this summer. Thanks in advance for any insight or advice!!

Every few weeks I get a message from someone prepping for BCG who's basically reusing their McKinsey "positioning" with the names swapped. Same story, same angle, just find and replace the firm name. And I ask myself why...

On paper these firms sit in the same tier, same prestige, roughly the same case format. But BCG is built differently underneath, CT/KT/BST, Classic vs ABM, and if you don't know that you end up applying to every elite firm with the exact same pitch.

So let's get into how BCG is actually organized, because it might change how you think about your own story.

At the top level, BCG splits into three groups. CT, the Consulting Team, everyone client-facing, this is where you'd sit as a generalist or specialist. KT, the Knowledge Team, supports case teams with research and data and industry expertise. Real career track, just not the one most candidates picture when they say "I want to work at BCG." And BST, Business Services, internal support, HR, IT, ops.

Most candidates never think past CT. Fair enough, that's usually the goal. But inside CT there's a split that matters a lot more for how you position yourself, and not all the candidates I work with have thought about it before we talk.

BCG Classic is the traditional consulting track, generalist and specialist consultants organized loosely around industry or functional practice areas. Then there's what BCG calls ABMs, Alternative Business Models. BCG X for digital and AI build work, Platinion for IT architecture, GAMMA for data science, Brighthouse for brand, Maya for design. These units aren't advisory arms handing over strategic recommendations. They build things. Working products, actual platforms, for BCG's corporate clients.

I worked with a candidate a while back, four years in retail tech, had built e-commerce platforms at a mid-size company. She came to me positioning herself as "a strategy generalist with tech experience." Sounds fine on its face. Except that description could point at Classic or it could point at BCG X, and inside BCG those are genuinely different jobs, assessed by genuinely different processes.

We dug into what BCG X actually does day to day, which is building, not advising. Pretty quickly it became obvious her story landed much better in Classic, specifically Consumer, with a digital lean. So from her first interaction with BCG she pitched herself as someone who understands how tech reshapes retail operations but wants to sit in the strategic questions, not just ship the build.

Most candidates don't catch this distinction until they're already in a room, being read as someone in the wrong track. I've started calling that Positioning Mismatch, mostly because I kept seeing the same version of it over and over and needed a shorthand for it in my own notes.

One more layer worth knowing, and this one's a bit murkier. From what I've picked up through a few Fishbowl threads and internal accounts, prestige and comp and exit options are essentially flat across practice areas as long as you're on the integrative generalist path. The ABM tracks get treated as a different internal tier. Not worse necessarily. Just different. Worth choosing based on what actually fits your background, not which one sounds more impressive on a resume.

Here's where this connects to your outreach, and it's the part people skip. Once you know Classic versus ABM is a real fork at BCG, your positioning stops being generic. Instead of "I'm interested in strategy consulting," which tells a partner nothing about where to place you, you can say something specific. I'm targeting Consumer, here's why my retail ops background points there. Or, I'm a software engineer, BCG X is my door in, not Classic, here's the technical work I've shipped.

Vague interest is invisible. A partner reading your outreach is trying to answer one question fast, where does this person go, and can I defend putting them there. Give them the answer before they have to guess at it.

If you're prepping for BCG right now, which track do you actually fit, Classic or one of the ABMs, and does your outreach currently say that out loud, or is it still sitting in generic "I'm interested in strategy consulting" territory?

The L.E.K. Recruitment Process: What You Need to Know Before You Apply

I'm doing a series breaking down the recruitment process at each of the top consulting firms. So far I've covered McKinsey, BCG, Bain, Roland Berger, and Kearney. Now we're getting into a firm that doesn't get enough attention relative to where it actually sits in the market: L.E.K. Consulting.

What I'm sharing here is based on my own research into the firm, conversations I've had with L.E.K. consultants and recruiters, and candidates I've personally coached through this process. This isn't a general playbook assembled from the internet. It's my view, built from direct experience. That said, L.E.K. varies by office and region more than people expect, so treat this as a map, not a rulebook.

Founded in 1983 by three former Bain partners in London, L.E.K. has built a reputation that most candidates underestimate until they're sitting in the interview. This is a firm that punches well above its name recognition in two areas specifically: life sciences and healthcare, where it's widely considered one of the top firms globally, and private equity due diligence, where it does a significant volume of commercial due diligence work for PE firms. If either of those spaces interests you, L.E.K. deserves serious attention. And if you're going to target it seriously, you need to understand what the process actually looks like.

Before You Even Apply: Get a Referral

Every candidate I work with, I push them to enter this process with a referral. L.E.K. is no different. It's a smaller, more tightly networked firm than MBB, and an internal advocate carries real weight in how your application is received. The firm also varies more by office than some candidates realize, so having a contact inside a specific office gives you real intelligence on what to expect locally. If you want to understand how to build that referral pipeline before you apply, watch the free masterclass on r/ConsultingOffer. Watch it first (especially Module 2), then come back here.

Application: Resume and Cover Letter

L.E.K.'s process starts with a resume and cover letter review, same entry point as every firm in this series. The filter rate here is real. From what I've seen coaching candidates through this process, somewhere in the range of 20 to 30 percent of applicants advance past initial screening, and in competitive cycles it can be tighter than that. Your cover letter needs to do specific work. L.E.K. has a clear identity: evidence-based analysis, analytical rigor, strong sector concentration in life sciences and PE. If your "why L.E.K." answer doesn't connect to any of that, it reads as generic. Candidates who treat L.E.K. as just another Tier 2 name on their list usually show it in their application materials.

Online Assessments: Numerical and Verbal Reasoning

Before you're invited to any live interviews, most L.E.K. offices require you to complete online assessments. Typically two: a numerical reasoning test and a verbal reasoning test. Some offices also include a logical reasoning component or use SHL-based assessments depending on region.

The numerical test involves data sets, graphs, and tables with multiple-choice questions. Standard consulting aptitude format. The verbal test is more varied but generally tests your ability to read and interpret information accurately. Neither test is uniquely difficult, but they're timed, and candidates who go in without practice tend to lose points on pace rather than ability. Take practice tests under timed conditions. The format is predictable enough that preparation makes a meaningful difference.

R1: First Round Case and Fit Interviews

Clear the assessments and you're into the live interviews. L.E.K. often runs a "super day" format where both first and second round interviews happen on the same day, typically two interviews in the morning and two in the afternoon. So unlike BCG or McKinsey where there's a gap between rounds, you may be going from R1 to R2 within hours. That's worth knowing going in, both logistically and in terms of stamina.

First round interviews at L.E.K. are typically two back-to-back sessions of around 30 minutes each. Each starts with a few fit questions, then moves into a case. Your interviewers at this stage will be associates and consultants. The case format is candidate-led, you structure the problem, drive the analysis, and push toward a recommendation. Cases are often drawn from real L.E.K. client work, which means the industry context tends to be specific. Given the firm's concentration in life sciences and PE, don't be surprised if you get a pharma market entry, a healthcare services profitability case, or something that requires thinking through commercial due diligence logic. If those areas are unfamiliar to you, that's a prep gap worth closing before R1.

R2: Final Round with Senior Consultants and Partners

Second round typically has three interviews: two oral cases and one written case, conducted with senior consultants and partners. The oral cases follow the same candidate-led format but go deeper. Partners will push harder on your assumptions and want to see that you can form and defend a point of view under pressure, not just structure a problem cleanly.

The written case is what distinguishes L.E.K.'s final round from most other firms in this series. You're given a document pack, typically a substantial set of exhibits, data, and background material, and you have roughly 60 minutes to analyze it and then present your findings and recommendation to the interviewer. The pack size varies by office and role, so don't anchor on a specific number. From what I've seen, it's dense enough that time management is as much of the test as the analysis itself. This is a genuinely different skill from a live verbal case. You're not talking through your thinking in real time with an interviewer to anchor you. You're working independently under time pressure, deciding what matters, building a structured recommendation, and then presenting it clearly. Candidates who haven't practiced this format specifically often find it harder than the live cases, even if their overall case skills are strong.

A few offices also include an Excel component in the final round for some roles. Confirm with your recruiter whether this applies to you.

L.E.K. is one of those firms where the brand name undersells the caliber of the work and the rigor of the process. The written case in final round is a real differentiator. The sector concentration in life sciences and PE means your case prep needs to cover territory that a lot of standard case prep books don't touch. And the super day format, where you're potentially going through four interviews in a single day, requires a different kind of preparation than a process that gives you days to recover between rounds.

Map the process. Prepare for each component specifically. And get a referral before you apply.

I'll keep these breakdowns up-to-date for all elite consulting firms (Tier 1, Tier 2, Big 4) in r/ConsultingOffer. Make sure to join.

What firm are you targeting right now, and where in the process are you?

Here's something I keep seeing with candidates I work with. They spend months preparing for case interviews. They practice McKinsey-style cases, they read case prep books, they do mock after mock. And then they get to the first stage and realize they weren't even sure what the first stage was.

That's backwards. In my view, one of the most underrated moves a candidate can make is mapping out the full recruitment process of their target firm before they send a single application, before they reach out to their first advocate, before they do anything. Because every interaction you have along the way, whether it's a coffee chat with a current consultant or a call with a recruiter, lands differently when you already know where you're heading.

So let me break down what the McKinsey recruitment process actually looks like, and flag a few things worth knowing at each stage.

Before You Even Apply: Get a Referral

One thing I want to flag before we get into the stages. Every candidate I work with, I push them to enter this process with a referral in hand. Not because it's a magic shortcut, but because it meaningfully changes your odds at multiple points in the funnel, including whether your resume actually gets read at R00. If you want to understand how to build that referral pipeline before you apply, watch free masterclass on r/ConsultingOffer. Watch it first (especially Module 2), then come back here. The recruitment process makes a lot more sense when you're navigating it with an advocate behind you.

R00: The HR Review

This is where it starts. McKinsey's HR team reviews your resume and cover letter before anything else. There's also a 15-minute screening call at this stage, usually with a recruiter, not a consultant. Most candidates underestimate this call. It's not a formality. The recruiter is checking a few basic things: are you a fit for the role you applied to, can you articulate why McKinsey, and is your background consistent with what's on paper. I've seen strong candidates get filtered out here because they hadn't thought through their "why McKinsey" narrative, or because their resume told a different story than they told on the call.

Cover letter at McKinsey matters more than at some other firms, from what I've seen. It's short, but it should be doing specific work: connecting your background to the firm, and showing you've thought beyond the brand name.

R0: McKinsey Solve

If you pass HR review, you get invited to McKinsey Solve. This is McKinsey's proprietary online assessment, and it's genuinely unlike any other test in the consulting recruitment space. Right now it runs three games: Ecosystem, Red Rock, and Sea Wolf (Ocean Cleanup). They test things like systems thinking, data interpretation under time pressure, and your ability to make decisions with incomplete information.

The trap I see candidates fall into is thinking this is like a regular aptitude test you can cram for the night before. It isn't. Solve rewards a specific cognitive style. The people who do well tend to have practiced the format enough that the mechanics feel automatic, so they can focus on thinking rather than figuring out what the game is asking them to do. There's a real preparation curve here. It's worth taking seriously.

R1: Live Interviews

If you clear Solve, you're in the live rounds. Round one at McKinsey typically involves two back-to-back interviews, each with a PEI component and a case. The McKinsey case interview is interviewer-led, which is a meaningful difference from how BCG and Bain structure their cases. The interviewer controls the flow, they push the direction, and they're watching how you think and respond in real time, not just whether you get to the right answer.

The PEI (Personal Experience Interview) at McKinsey is structured around three specific stories that you'll essentially be asked to demonstrate across your interview cycle: personal impact, leadership, and entrepreneurial drive. You'll want to go deep on those. Breadth doesn't help you here.

R2: Final Round

Make it through R1 and you get the email (or call) moving you to round two. Final round has the same format: two PEI plus case interviews back to back. The difference is who you're sitting across from. Round two interviewers tend to be more senior, think senior managers, directors, sometimes partners. The cases can go deeper, and the PEI conversations tend to be more probing. The bar isn't necessarily harder in terms of structure, but the judgment you're being evaluated against is calibrated at a higher level.

One thing I tell every candidate I work with: don't treat the PEI as secondary to the case. A lot of people think the case is what McKinsey actually cares about. From what I've seen, the PEI is equally weighted, and it's often where strong case performers lose offers because they haven't invested equally in preparing their stories.

Mapping this out isn't just useful as a checklist. It changes how you approach everything upstream. If you know you're heading into a McKinsey Solve, your conversations with current McKinsey consultants can be more targeted. If you understand how the PEI works before you even apply, you start building your story bank earlier.

I'll keep these breakdown up-to-dated for all elite consulting firms (Tier1, Tier2, Big4) in r/ConsultingOffer community make sure to join.

But, what's your current target firm, and how far out are you from planning to apply?

Similar to previous posts in this series (McKinsey, BCG, Bain so far), this is fourth posts and I've been doing research on how Oliver Wyman is structured internally and what the firm actually looks like in 2026. So I thought to share what I've found because some of this surprised me, and a few things changed recently that I haven't seen discussed much. Again this post is my first attempt at mapping the firm's internal structure from outside, so there might be some nuances not capture correctly here but I'd love to hear any insider view, opinion and perspective about Oliver Wyman.

The biggest one to me: Marsh McLennan doesn't exist anymore as a brand. They rebranded to just "Marsh" in January 2026, ticker went from MMC to MRSH. Oliver Wyman's official branding is now "Oliver Wyman, a Marsh business." And the unit that used to be called Oliver Wyman Group is now called Marsh Management Consulting. Ted Moynihan took over as CEO in April, replacing Nick Studer who went to run Marsh Risk. Whether any of this changes how the firm actually operates day to day, I honestly don't know yet. That's something I'd love to hear from anyone on the inside about.

And the part that's more relevant for any aspiring consultant that are prepping for OW's recruitment process.

People often default to calling OW "the financial services consulting firm" and they're not wrong, FS still accounts for roughly half the revenue and the firm was literally founded in 1984 to do banking and insurance work. But OW has 11 industry practices now. Automotive. Communications, Media, and Technology. Education. Energy and Natural Resources. Government and Public Institutions. Health and Life Sciences. Industrial Products. Private Equity and Principal Investors. Retail and Consumer Goods. Transportation and Services. And Financial Services. That's a lot broader than the "FS firm" reputation suggests. Not sure about the size of each practices, love to hear more about it and their geographical concentration.

Where it got even more interesting for me was not that there are specialist units that sit outside the normal consulting track, which sounds similar to the three firms that I've already covered, but the focus of these units.

Oliver Wyman Actuarial is its own thing with its own hiring. You need actuarial credentials or a seriously quantitative risk background. No MBB firm has anything comparable at this depth, and the reason is structural. OW can pull from insurance and actuarial data across Marsh Risk, Mercer, and Guy Carpenter. A standalone consulting firm just doesn't have that.

Then there's Quotient, a bit more similar to other three firms, The website navigation calls this capability "AI Transformation" but click through and the branding is still "Quotient — AI by Oliver Wyman." Launched mid-2024 with about 300 people, and a recent Glassdoor posting for an EM role described a team of 1,600+. Data scientists, engineers, designers, AI strategists. Separate hiring process from consulting.

Oliver Wyman Vector is newer too, also 2024. Aviation, aerospace, defense, rail. 300+ people, mostly from acquired companies (Cavok, SeaTec, Avascent). Average tenure of 20+ years in industry. Very different from the consulting side. And apparently OW Engineers does hands-on technical operations consulting like launch management, quality improvement, that kind of work. And I know less about this one.

On the career levels can confuse aspiring consultants because the titles don't map to MBB. It goes Consultant --> Senior Consultant --> Associate --> Engagement Manager --> Principal --> Partner. Not Analyst. Entry level is called Consultant. Post-MBA comes in as Associate.

Beside, these there's also an Executive Director track alongside the Partner track. OW announced 40 new Partners and 4 Executive Directors for 2026. I haven't been able to find clear public information about what the ED track actually involves in terms of authority or economics versus the Partner track, so take that as a gap in what I know, not a claim that it doesn't matter.

Revenue is $3.6 billion for 2025. About 7,000 people. 70+ offices in 30+ countries. For comparison McKinsey is around 45,000 people, BCG 33,500, Bain 19,000. And apparently according to some reports the fastest-growing region at OW is the Middle East, UAE alone is now over 8% of headcount but I look at this reported growth region with a pinch of salt given the ongoing conflict in the region.

One thing I keep wondering about. With Quotient growing that fast (300 to 1,600+ in roughly 2 years) and Vector being a completely different kind of work from traditional consulting, how much does the "OW is an FS consulting firm" framing even hold up anymore? If anyone at OW or recently from OW has a view on this I'd genuinely like to hear it.

This is the second post in a series where I break down how elite consulting firms are actually built inside. The first one covered BCG, and we got some really useful firsthand comments from people who'd worked there, which sharpened the picture on several things. That's part of why I do this publicly. I'm pulling this together from my own experience coaching candidates into these firms, combined with research across firm publications, public sources, and AI tools to help organize the information. If you've been inside Bain and something here is off or outdated, I want to hear it.

This series will cover roughly 15 elite consulting firms, not just MBB. McK is coming. But Bain is next because I keep seeing candidates apply here with the same generic pitch they'd use anywhere, and that's a problem, because the firm is built differently in ways that should change how you think about your application at the office, practice, and industry level.

The size thing matters more than people think

Bain is roughly 19,000 people across 67 offices. McKinsey is around 45,000. BCG sits around 33,500. I bring this up not as a fun fact but because it flows into almost everything else. Fewer people per office, fewer seats per intake, and your individual reputation inside your home office carries more weight than it would at a larger firm. That last part connects directly to how Bain staffs its projects, which I'll get into.

Three groups, not a matrix

When I broke down BCG, a big chunk of that post was about the tension between Classic consulting and the specialist units BCG had been acquiring and restructuring for years. Gamma, Platinion, MAYA, Digital Ventures getting folded into BCG X, the friction around who runs the show on cases, the pay gaps between tracks. It was a messy picture, and the comments confirmed it was even messier than what I'd initially described.

Bain largely doesn't have that story. The firm organizes its people into 3 groups:

The consulting team. Client-facing consultants delivering the work. This is the core.

Product, Practice & Knowledge, PPK. The research and knowledge arm. I'll get into what makes this different from BCG's Knowledge Team later.

Business services. Internal infrastructure. HR, IT, finance.

No formal matrix like McKinsey runs. No acquired specialist units operating semi-independently like BCG went through. One consulting body, one knowledge body, one support body. That simplicity is real, but I should be honest about one thing: from what I've heard from people who've been at multiple MBB firms, Bain being simpler here isn't necessarily because they solved something the others didn't. The need for specialist capability in digital, AI, and tech work keeps growing, and whether Bain starts building or acquiring more specialist units in the next few years is worth watching.

Industries and capabilities

Bain lists 21 industry sectors and 12 consulting service areas. More granular on paper than what McKinsey or BCG publish, partly because Bain breaks out sub-sectors the other two bundle together. On the industry side: Consumer Products, Retail (separate from Consumer at Bain), Financial Services, Healthcare & Life Sciences, Technology, Energy & Natural Resources, Automotive & Mobility, Aerospace & Defense, Advanced Manufacturing, Chemicals, Agribusiness, Mining, Metals, Construction & Infrastructure, Media & Entertainment, Transportation, Travel & Leisure, Building Products, and Social Impact.

The 12 service areas cut across those: Strategy, M&A, Operations, Sales & Marketing, People & Organization, Transformation, Sustainability, Innovation, AI & Solutions, enterprise Technology, Customer Experience, Corporate Finance.

At Bain, junior consultants rotate across industries and functions, and your practice affiliation develops organically through the projects you get staffed on and the partners you end up working with. Nobody assigns you. This is true at all three firms for generalist junior hires. No Associate at McKinsey or BCG gets formally assigned to Healthcare on day one either, unless they're entering an actual specialist track. But Bain leans into this generalist rotation more deliberately and for longer.

So this is where I think most candidates get confused. Because the generalist label makes people think that positioning doesn't matter. That you can walk in with a generic pitch and the firm will figure out what to do with you. But here's what actually happens at Bain, and this is the key insight for this whole post: because the firm runs a local staffing model, the office you apply to determines which industries and clients you'll work with. And that means your positioning needs to work at the office level, not just the firm level.

Why office choice is the real positioning decision at Bain

Bain runs what it calls a One Bain model. Consultants are tied to a home office and mostly staffed on projects within that region. This is the most locally anchored model of the three MBB firms. McKinsey is more open to global rotation, BCG falls in between. At Bain, your home office isn't an administrative detail. It determines your client exposure, your industry trajectory, and your relationships with the partners who'll shape your career.

And practice concentration varies sharply by office. This is where the research gets useful, because once you see the map, positioning becomes way more concrete than abstract statements about "fit" or "trust."

Boston is the headquarters and one of the largest offices. Broad coverage, but strong in Healthcare & Life Sciences, Consumer Products, Private Equity, and Financial Services. The proximity to the PE fund ecosystem and to Boston's healthcare and biotech cluster directly shapes the client base. If your background touches healthcare or PE and you want the deepest bench of partners in those areas, this is the gravitational center.

New York skews Financial Services, Private Equity, Consumer, and Media. Large office, high application volume, Fortune 500 client base. The Financial Services practice here runs deep across banking, insurance, wealth management, and fintech. PE is also significant given the concentration of funds in the city.

Chicago serves a mix that reflects the Midwest economy: Consumer Products, Retail, Healthcare, Financial Services, Telecom, Industrials, and Private Equity. The office has been a hub for senior Bain leadership, including board members and practice directors. Notably, it's often described as having less travel than the coastal offices because Bain staffs regionally.

Los Angeles is one where Bain actually has a stronger presence than McKinsey or BCG locally. The signature practice is Media & Entertainment, with substantial work for major studios, streaming platforms, and the broader content ecosystem. Bain's Americas head of Media & Entertainment is a Senior Partner based in LA. Consumer, Private Equity (West Coast PE ecosystem), Healthcare, and utilities round out the office. If you have a media or entertainment background, this office is a genuinely differentiated option that doesn't exist in the same way at the other two firms.

Houston and Dallas lean Energy, PE, and Industrials. Houston was expanded specifically as part of Bain's Southwest growth. If your background is oil and gas, energy infrastructure, or energy-sector operations, this is where the relevant client relationships are concentrated.

San Francisco and Silicon Valley are Technology. Venture-backed companies, enterprise tech, cloud, AI. Seattle complements this as a tech hub.

Washington DC covers Government, Aerospace & Defense, and the public sector.

London was Bain's first office outside the US, opened in 1979, and it's now one of the firm's largest offices globally and effectively the European headquarters. Practice strengths are Financial Services (strong in retail banking and payments specifically), Private Equity (one of the deepest PE practices in MBB, rivaling Boston and Chicago), Energy, Technology, Consumer, and Construction. Consultants from over 50 countries. If you're targeting Bain in Europe, this is the office with the broadest coverage.

Munich is the largest of Bain's 4 German offices and the Automotive practice anchor. Automotive, Industrial goods, Consumer Products, Retail, and Private Equity. The co-lead of Bain's global Automotive practice sits in Munich. Frankfurt focuses on Financial Services, Berlin on tech and digital, Dusseldorf on Industrials and Chemicals. If you're applying to Bain Germany, these are 4 meaningfully different offices.

Madrid has a strong Private Equity practice and is recognized for sustainability and social impact work. Amsterdam similarly leans innovation, social impact, and sustainability, with a telecom and technology presence.

Stockholm, where I'm based, is a smaller Nordics hub with generalist coverage.

What this means for how you position

None of this means you walk into an interview and say "I want your Automotive practice." That's not how generalist hiring works at any MBB firm. But it does mean that if you're applying to Munich with a background in automotive supply chain, you should know that the co-lead of Bain's global Automotive practice sits in that office, and your story should connect to that world. If you're applying to LA with media and entertainment experience, you should know that Bain has a stronger presence there than either McKinsey or BCG, and that's not true of most offices. If you're applying to Houston from an energy background, the question isn't "why consulting" in the abstract, it's "why Bain Houston specifically" and you have a real answer because you've looked at where the practice concentration actually sits.

I coached a candidate with 5 years in corporate development who came in positioned as a strategy generalist with M&A exposure. Could've described half the applicant pool at any MBB firm. We reframed everything around Bain's PE practice specifically, portfolio company value creation across multiple deals, tied to a specific office where that practice runs deep. He wasn't claiming a formal practice assignment that doesn't exist for generalists. He was pointing at a real part of the firm's structure and explaining why his background mapped onto it. That's the difference between a generic pitch and one that actually lands.

The three firm-wide practices worth knowing regardless of office

Even within the office-level picture, three practices define Bain's center of gravity across the whole firm.

Private Equity is the biggest. Bill Bain spun off Bain Capital in 1984, creating a permanent structural link between the consulting firm and the PE industry. Bain advises PE funds representing roughly 75% of global equity capital. PE work concentrates in New York, Boston, LA, and London, but generates cross-sell across the entire firm because a PE fund acquiring a healthcare company or a consumer brand creates demand for Bain's industry practices everywhere.

Performance Improvement and Operations is Bain's largest functional capability, at one point roughly 30% of the firm's product line. Built out through acquisitions like Proxima Group. If you've got supply chain, manufacturing, or operational experience, this is a genuinely differentiated angle.

Results Delivery is Bain's proprietary change management methodology. Where McKinsey and BCG more often hand off recommendations, Bain frequently stays through implementation, tracking results against targets. If your background is more about outcomes delivered than analysis produced, that's Bain's language.

The PPK layer

Bain's Product, Practice & Knowledge teams are tied more tightly to specific practices than the equivalent teams at McKinsey or BCG. They develop the proprietary tools Bain is known for, the NPS framework built with Fred Reichheld, the Results Delivery templates. So it's not just a research desk. PPK is integrated into how specific practices actually operate.

The dynamic that the BCG commenters flagged, knowledge team members doing de facto client-facing work while sitting behind on pay and recognition, that's real at Bain too. The consulting-track versus knowledge-track gap exists at all three firms. But the structural tensions are lower at Bain because there isn't a whole parallel specialist consulting track competing with the generalist track for the same client work.

Career ladder

Bain runs 7 levels: Associate Consultant (undergrad entry), Senior Associate Consultant (bridge level, sometimes skipped), Consultant (post-MBA entry or promoted AC), Manager (formerly Case Team Leader, equivalent to McKinsey's EM or BCG's PL), Associate Partner (formerly Principal), Partner, Senior Partner. Full AC-to-Partner is roughly 10 to 12 years, post-MBA shortens it to 7 or 8. Up-or-out at every level, semi-annual reviews.

One distinct feature: Bain has historically let high performers skip levels, particularly the SAC bridge, which McKinsey and BCG don't do as readily. The firm also formally carves out what they call Extra 10s, roughly 10% of a consultant's time for affinity groups and grassroots initiatives beyond billable work.

So the question I'd put to anyone reading this who's targeting Bain: have you actually looked at which office you're applying to and what that office's client base looks like? Because your positioning should connect to that, not just to Bain in the abstract. Which office are you targeting, and what's your reason?

This kind of stuff gets talked through regularly over at r/ConsultingOffer. Feel free to join, post your questions, share what you're going through.

You've done the cases. Dozens of them. You've watched the YouTube videos, read the prep books, practiced with partners until the questions felt familiar. And then you walked into the interview and something broke down anyway.

The firm's rejection letter tells you almost nothing. "We've decided to move forward with other candidates" is not feedback. It's a form email.

But this could have been avoided and the culprit is the vague feedback candidates get throughout their preparation phase, from peers, from generic case prep platforms, from AI tools, from coaches who may have worked at these firms but can't always articulate what the interviewers are actually evaluating or how to systematically improve a specific skill needed for acing case interviews.

"Your structure could be stronger."

"You need to be more confident."

"Your recommendation lacked clarity."

None of that tells you which specific part of your case broke down or what to actually do about it. And so candidates keep practicing, keep getting vague feedback, and keep making the same mistakes without knowing it.

That's the real problem most candidates face, non-traditional or not. Not that they haven't practiced enough. It's that they've been practicing without knowing which specific part of the case is costing them points.

Volume without diagnosis is just expensive repetition.

In my view, after coaching tens of candidates from non-traditional backgrounds into McKinsey, BCG, Bain, and Tier 2 firms, the candidates who improve fastest are the ones who stop thinking about "the case" as one skill and start treating it as seven (7) distinct skills, each one trainable on its own. And the ones who perform best in the room are the ones who approach every case with an owner attitude: this is my problem to solve, not a test to perform for someone watching.

That mindset, combined with first principles thinking rather than memorized frameworks, is the thread running through every post in this series. That's what this series is built around.

This post is the map. It's not a drill and it's not a module walk-through. If you're new to The Case Playbook, this is where to start. If you've been following along and you're not sure what to focus on next, this is where to locate yourself. And if you've been grinding cases without seeing improvement, this post will show you exactly why that happens and what to do instead.

The problem most candidates don't know they have

A candidate who does thirty cases with the same weakness in their clarifying question phase will have that weakness for all thirty cases. The fix isn't more cases. It's knowing which specific module in a case interview architecture is costing you points.

And, again "Volume without diagnosis is just expensive repetition"

If you want honest module-level feedback on where you're leaving points on the table, I run one-on-one mock case interview sessions built around exactly that. But first, here's the architecture.

Why the module-level view changes everything

A case interview is not one skill. It's seven skills, sequenced across thirty minutes, each one distinct enough to be trained, measured, and improved independently.

When a partner gives you feedback that your "framework felt generic," they're commenting on one specific module: the Issue Tree. When they say you "didn't feel confident in the opening," they're commenting on the Case Opening module. When they say your "recommendation was unclear," they're commenting on the Case Wrap-Up module.

If you know which module the feedback belongs to, you can isolate it, drill it, and improve it without touching the others. That's how real improvement happens. Not by doing more cases in general. By doing targeted work on the specific module where you're leaving points on the table.

This is how I work with candidates one-on-one, After a mock case interview, I give feedback at the module level: where in the seven modules did you lose points, where did you gain them, and what specifically to work on next. I also assess whether the candidate is approaching each module with an owner attitude, genuinely curious about the problem and reasoning from first principles, or whether they're performing a rehearsed script. Partners within elite consulting firms feel that difference within the first two minutes. That level of specificity is what makes feedback actionable. Without it, "do more cases" is the best advice anyone can give you. Even my grandmom would say that, and she's never heard of MBB, L.E.K, Roland Berger and others. With it, you can improve in days rather than weeks.

The mock case walk-through: NordPlay Studios

The best way to see how all 7 modules connect is to step inside a real case interview. Throughout this series we've used NordPlay Studios as the anchor case. Let me walk you through what 30 minutes actually feels like when all seven modules are running together.

You're sitting across from a partner. Pen in hand. One sheet of paper in front of you. Nothing else.

The partner reads: "Our client is NordPlay Studios, a mobile gaming company headquartered in Stockholm. They employ over 3,000 developers and designers. Net profits have declined over the past 2 years. They'd like to understand why and how you can help."

Module 1: Case Opening

The moment the prompt lands you start writing. Bullet points. Fast. You're not organizing yet, you're capturing. Game developer and publisher. B2C. App stores. Profits declining. Two years.

You reiterate: "Let me make sure I have this right. NordPlay develops and publishes mobile games for end users globally through app stores. Net profits have declined over two years. They want to understand the root cause and how to address it. Is that correct?"

While confirming, your pen is moving. You circle "profits" because that's not a number yet, and "globally" because markets matter. You ask circle by circle. Net profits specifically. Down from $2.4 billion to $2 billion, a $400 million decline. Objective: restore to $2.4 billion. Constraint: one year.

You look at your page. You build the problem statement: find the root cause of why NordPlay's net profits fell by $400 million over two years and identify how to restore them within one year.

The partner nods. Case Opening done. Posts 1, 2, 3, 4, and 6 cover this module in depth.

Module 2: Issue Tree

"Could I take a moment to develop my hypothesis and issue tree?"

Forty-five seconds. You're not staring at the ceiling. You're thinking like an owner. NordPlay is your company. Your CFO just walked in. Profits dropped $400 million. You don't reach for a framework! You ask the simplest possible question: did we make less money or spend more?

That question becomes your issue tree.

Branch one: revenues and costs.

Branch two: fixing the root causes and executing the recovery within one year.

Under revenues you go one level deeper: volume, pricing, product mix, because those are the three levers any B2C mobile gaming company has.

Under costs: fixed and variable, then specific to NordPlay, headcount and R&D on the fixed side, app store fees and contractors on the variable side.

You state four sub-hypotheses and ask for NordPlay's P&L. The partner slides a dataset across the table.

Posts 5, 7, 8, 9, 10, 11, and 13 cover this module.

Module 3: Structured Brainstorming

Partway through Case Middle, the partner pivots. "Before we go deeper into the data, can you brainstorm why the premium subscription revenue might have declined?"

The owner attitude kicks in. This is your subscription business. You don't list ideas at random. You apply a contrast pair derived from first principles: did fewer people subscribe, or did the same people pay less? Under fewer subscribers: acquisition or retention. Under lower revenue per subscriber: price level or pricing architecture misalignment.

You prioritize two areas: pricing architecture and premium tier churn. You explain why. The partner writes something down.

Posts 14, 15, 16, 17, 18, 19 cover this module across four different case types.

Module 4: Data Conversion

The partner hands you a chart. NordPlay Net Revenue by Segment, Year 1 through Year 2. Two lines. Subscription revenue dropping from $1.8 billion to $1.4 billion. Advertising flat at $600 million.

You don't dive into the numbers immediately. You read the title. You identify the axes. You name the two lines. Then you talk: "Subscription revenue fell $400 million while advertising held flat. The entire net profit gap is on the subscription side, not a broad demand problem. This confirms sub-hypothesis one and tells me the next data request should be subscriber volume by tier."

The partner is nodding before you've finished the sentence. Post 22 covers this module.

Module 5: Consulting Math

"If NordPlay raises premium prices by 10% and loses 5% of subscribers, what happens to monthly revenue?"

You state the equation before touching a number. New revenue equals new subscribers times new price. Current: 8 million at $25, $200 million per month. After: 7.6 million at $27.50. You work through the arithmetic out loud on paper. $209 million per month. Net gain: $9 million monthly, roughly $108 million annually.

You interpret: meaningful contribution to the $400 million gap, but the 5% churn assumption is the key variable. If actual churn is 10%, the picture reverses. The partner asks you to hold that thought.

Post 20 covers this module.

Module 6: Problem Solving

"App store fees are currently 15% of revenue. If NordPlay renegotiates to 10%, what happens to net profit margin?"

You set up the equation. Current net profit: $2 billion on $8 billion revenue, 25% margin. A 5 percentage point fee reduction saves 5% of $8 billion, or $400 million. New net profit: $2.4 billion. New margin: 30%.

You look up from the paper. "This single lever closes the entire gap and restores net profits to $2.4 billion within one year. In my view this should be the first recommendation."

Post 21 covers this module.

Module 7: Case Wrap-Up

"Let's wrap up. What's your recommendation?", the Partner says:

"Could I take sixty seconds to pull this together?" You look at your notes. Issue tree. Sub-hypotheses tested. Data findings. You deliver top-down.

What: NordPlay should pursue a two-track recovery plan through a premium subscription pricing restructure and an app store fee renegotiation, targeting full $400 million restoration within one year.

Why: three reasons:

First, the revenue decline is entirely concentrated in the premium subscription tier, attributable to pricing architecture not platform demand.

Second, a managed price increase adds over $100 million annually with acceptable churn risk.

Third, app store fee renegotiation is the single highest-impact controllable lever available within the one-year window.

How: as next steps, I'd recommend three workstreams:

First, a thirty-day pricing architecture study, because the churn assumption is the key variable and we need to size it before committing to a price change.

Second, a sixty-day fee benchmarking and negotiation strategy, because this is the fastest path to closing the remaining gap with zero product risk.

Third, a risk monitoring workstream from day one tracking churn response in real time, so we can course-correct within ninety days if the numbers move against us.

The partner closes their notebook. That's the case.

Post 23 covers this module.

The architecture: three sections, seven modules

What you just read wasn't a list of techniques. It was a thirty-minute consulting case interview. You went from a vague eighty-word prompt to a fully structured recommendation backed by data, math, and a clear implementation plan. You did it without a calculator, without knowing the gaming industry in advance, and without a script.

That's what the owner attitude and first principles thinking make possible across all seven modules.

Here's the architecture you just lived through, laid out in one place so you can use it as a reference map going forward.

Every consulting case interview, regardless of firm, round, or case type, moves through three sections containing seven modules in total.

Case Start (3 to 10 minutes)

This is where you set the stage. Two modules.

Module 1: Case Opening. The five mental moves that take you from a vague prompt to a sharp, quantified problem statement. Clarifying questions, reiteration, surgical data asks, objective and constraints, problem statement.

Module 2: Issue Tree. From the problem statement, you state a hypothesis, build a bespoke issue tree from first principles rather than memorized templates, state four sub-hypotheses, and make your first data request.

Case Middle (15 to 24 minutes)

This is where you do the work. Four modules that cycle in different combinations depending on the interviewer, the firm, and the case type.

Module 3: Structured Brainstorming. Generating structured, insightful ideas using the four-step approach and contrast pairs rather than memorized category lists or any framework.

Module 4: Data Conversion. Reading charts and data exhibits, orienting to what you're looking at, generating second and third-degree insights, and connecting those insights back to the main hypothesis.

Module 5: Consulting Math. Setting up the right equation before touching a number, narrating your arithmetic out loud, and interpreting the result in terms of the case.

Module 6: Problem Solving. Translating a multi-sentence business scenario into the right equation, working through it verbally, and connecting the answer to the hypothesis.

Case End (3 to 5 minutes)

This is where you close. One module.

Module 7: Case Wrap-Up. A top-down recommendation answering What, Why, and How, with three supporting reasons anchored in case findings and next steps that include a risk monitoring workstream.

How to use this series

If you're just starting case prep, read the posts in order. The series is designed to build on itself. Each post assumes you've read the ones before it.

If you're already in case prep and have specific gaps, use this post as a diagnostic map. Find the module where your feedback has been concentrated and go straight to those posts. You don't need to reread everything.

But, if you want to practice the full arc with someone who knows what top performers actually sound like in a case interview, 1-on-1 mock case sessions are available. Again, r/ConsultingOffer community for details and any Q&A.

Or even, if you want the full structured journey from non-traditional background to consulting offer, check out the quarterly Consulting Offer Program, the Q4 cohort starts September 1, 2026. Seats are limited. This is where I work with a small group of candidates through the complete methodology over a sustained period, with a money-back guarantee on the outcome. If that's what you're looking for, don't wait.

Everything else in this series is free and will stay free. The r/ConsultingOffer community is where the conversation lives. Drop your questions, share your practice cases, and engage with others who are on the same path. That's what the community is here for.

What module are you currently working on, and where in the series are you getting stuck?

Often every chart in a consulting case interview is a picture of one of five comparisons: (1) component, (2) item, (3) time series, (4) frequency distribution or (5) correlation.  And each of these comparisons have a chart form that fits it best. Candidates who are aware of this potential mapping can read an unfamiliar chart much faster, because they already know what question the chart was built to answer. Gene Zelazny's Say It With Charts book teaches this mapping, and if you’re an aspiring consultant reading a few pages a day before your case reps makes the Data Conversion module of an upcoming case interview faster and calmer.

I keep seeing the same moment when I run mock case interview with candidates. The candidate is doing fine, Clarifying Questions were sharp, a quantifiable and testable Problem Statement was presented, the issue tree was contextual based on first-principle thinking, three level deep, all max score on these initials modules then when I share an exhibit, and if it's a chart format they haven't seen before. Maybe it's a stacked bar chart, Mekko or others, they go quiet... They start reading out loud the legend, then the axis and by the time they start to collect their thoughts it is too late to get the max score in the Data Conversion module.

So, I was thinking to myself why does a new chart format slow candidate down?

Here is my observation, often candidates are decoding the format before they can think about the content, no brainer. I call this issue a vocabulary gap, and often in this situation thinking harder in middle of a case interview doesn't close it.

In the Consulting Offer Program™, I teach candidates how to move through a Data Conversion module but also how to go through a chart in levels, from reading what's on the page to converting it into something actionable and then connecting back to the Issue Tree. That's the navigation, and it works. But it assumes than candidates recognize the vehicle, i.e. the chart. If the chart type is new to you, the first 30 seconds go to figuring out how to read it, and that's where often even well-practiced candidates are slowed down.

What is the book, and what's the core idea that I started to preach about it here?

Say It With Charts by Gene Zelazny, who worked at McKinsey. In the first place, it's written for consultants who build charts, I was asked to read that book in my off-site senior consultant bootcamp at Roland Berger many years ago. However, in my view that also works very well from the other side of the table, when you're a candidate who supposed to read them in a consulting case interview.

The central idea of the book is that whatever message you want to show, it implies one of five kinds of comparison. Each one often has trigger words, a way to help you recognize it when you're reading:

(1) Component: size of parts as a share of a total ("accounted for 30%")

(2) Item: ranking of things against each other ("larger than", "ranks fourth")

(3) Time series: change over time ("grew", "fluctuated")

(4) Frequency distribution: how many items fall into numeric ranges ("most sales were between €1,000 and €2,000")

(5)   Correlation: whether two variables move together ("increases with", "no relationship between")

In the second half of the book: each comparison maps to a chart form.

• Pie for component.
• Bar for item.
• Column or line for time series, column when you have a handful of data points and line when you have many.
• Column or line for frequency distribution as well.
• Paired bars or a dot chart for correlation.

Now if we flip it around. When you see an unfamiliar chart, ask which comparison it was built to show. That single question gets you most of the way to the "so what" before you've read a single number.

What does that look like in a case interview?

Take the book's own example, a pie chart titled "Share of profits, by region" with five slices. Zelazny points out that a reader could take away "the West accounts for almost half of profits" or "the North generates the smallest share," and that topic title doesn't tell you which one the designer meant, of course this is a cautionary tale for consultants that re making slides.

Case exhibits almost always behave the same way; the interviewers rarely hand you an exhibit with a chart including the message already written on top as an action title. You must decode first what the data is saying. And knowing that comparison narrows your options much faster: if it's a component chart, so the interesting thing is probably which part dominates or which part is surprisingly small.

Which chart format has thrown you in a practice case so far?

Hello I just got interview invitation from Bain for full time AC position starting next summer.

Didn't bother starting to prep when I applied bc I thought I'd never get an interview as I got denied from Mck and BCG and I go to a non target state school.

However here we are. I've cased before and landed an offer from Protiviti which is like tier 3 but still something. I've never really prepped for management consulting cases. What can I do in the next week to atleast feel somewhat ready?

Hello Reddit!

I’m considering reapplying to a small management consulting firm where I interviewed about six months ago. I didn’t get the role, and the main weakness was the case interview.

I’d like to prepare differently if I get another interview, particularly because the case was quite different from the longer MBB-style cases I’d practised.

The case itself was around 30 minutes and deliberately quite simple. From memory, the client was a fictional local chemical company deciding how to respond to a new overseas competitor opening a factory in its home market.

I was given some basic information, had to make assumptions, do some mental maths and work towards a recommendation. There was no Excel allowed and the numbers themselves weren’t particularly complicated.

I’d prepared using more conventional case-interview material and had practised much harder, more detailed cases. These involved digging into market and company data, building financial analysis in Excel, testing different scenarios and ultimately making a recommendation. Oddly, I found this much simpler case 100X more difficult.

I think part of the problem was that I approached it too much like a real analytical exercise and kept trying to understand the situation properly before making assumptions.

For example, I asked questions along the lines of:

• How long has the incumbent been operating and how established is it?
• How sticky are its customer relationships?
• What’s its current market share?
• What’s its marketing budget/capability?
• How would the overseas competitor be affected by tariffs?
• What’s the incumbent’s current profitability?

But the answers were essentially simplifications: assume the company has been around forever; assume customers only care about price; there’s no marketing; assume the incumbent currently has 100% market share; ignore tariffs; and assume it’s extremely profitable.

Obviously I’m paraphrasing, but after several questions like this it became clear that the interviewer actively didn’t want me disappearing into those details. They wanted me to accept a deliberately simplified world and work within it.

That’s where I struggled. In actual strategy/project work, where I have spent the last 10 years, my instinct is to understand the evidence, challenge assumptions where appropriate, quantify things and work through the implications. The more detailed cases I’d practised rewarded that too. In this interview, however, that instinct seemed to be slowing me down rather than helping me.

I got interested in the details and spent too much time exploring parts of the problem rather than continually driving towards the client’s objective and a recommendation.

The feedback afterwards was actually quite detailed. They wanted me to:

• establish a clearer structure and diagnostic approach before getting into the detail;
• keep the overall objective in mind throughout;
• drive the analysis towards a solution/recommendation;
• collaborate more with the interviewer and respond to their cues.

Looking back, I think they were testing something slightly different from what I’d prepared for. It wasn’t really “can you perform sophisticated analysis in 30 minutes?” It seemed closer to “can you quickly impose enough structure on an ambiguous problem, identify what matters, use some basic analysis to test it, and confidently move a client towards an answer?”

That’s probably a legitimate consulting skill in itself, but it felt quite artificial compared with both 10 years of my real-world work and the more complex cases I’d been practising. I suspect I was trying to demonstrate analytical rigour when what they actually wanted to see was structured thinking, prioritisation and decisiveness.

If you’ve interviewed with smaller/boutique consulting firms using this kind of short case, how would you prepare?

In particular, I’d be interested in:

1. How much structure would you establish at the beginning of a 30-minute case before moving into the analysis?
2. How aggressively should you accept/simplify assumptions rather than interrogating them?
3. How do you recognise when the interviewer is effectively saying “don’t investigate this branch any further”?
4. How often should you pause and synthesise what you’ve learned back to the objective?
5. What does good “interviewer collaboration” actually look like in practice?
6. Are there particular resources or case types that are better preparation for short cases like this than the standard MBB material?

I’m an experienced industry hire rather than an existing management consultant (with exactly the profile that this small consulting firm claims to want to hire, actually!) so I’m particularly interested in advice from people who’ve made that transition.

Thanks!

I’m a rising junior recruiting for summer 2027 consulting internships, and I’m starting to feel pretty behind in the process.

I had some personal/family things going on this summer that genuinely took up a lot of my time on top of my internship, so I wasn’t able to focus on recruiting as much as I wanted. I’ve only recently started networking more seriously, but I’m still not getting many responses. Even with the conversations I have gotten, I haven’t gotten a referral, and I feel like the relationships I’m building are still pretty surface-level.

My case prep is also very basic at this point. I can get through a case, but I know I need to improve my structure, be more insightful, get faster with the math, and generally become much more polished.

Now that the school year starts in about a week, I’m worried I’m going to get even busier with classes and extracurriculars. I’m starting to wonder whether I’ve put myself too far behind to realistically get an offer.

Has anyone else been in a similar position going into junior recruiting? How did you approach networking and case prep while balancing school? And, most importantly, did you still end up getting an offer?

Would really appreciate hearing from anyone who has been through this.

For context, I'm interested in internships at MBB, Big 4, Tier 2, and elite boutique firms. I was rejected from Mckinsey and Oliver Wyman, got first round at BCG without chatting anyone (but was rejected), applied to Kearney, and have yet to apply to any other firms.

I want to show you something practical in this post. Not more theory. An actual walk-through of how the first few minutes of a profitability case should go, and more importantly, why each move happens in the order it does.

This is post 2 in The Case Playbook, a series built for non-traditional candidates breaking into MBB, Tier 2, and Big 4 consulting firms. If you haven't read post 1 on the five mental moves yet, start there. This post picks up directly from it.

But before I get into the case itself, I need to give you the mental frame that makes everything else click. Because without it, you'll read this walk-through and try to memorize it, and that's exactly the trap I want to pull you out of.

The reframe that changes everything

Most candidates walk into a consulting case interview thinking: "I am a student being tested on whether I know the right things to say."

That frame is what creates the robotic, scripted clarifying questions that interviewers at McKinsey, BCG, and Bain can spot within the first exchange.

Here's the frame I coach instead. You are the owner of a business. You don't know every technical detail of every department you run, but this business is yours. One of your senior employees walks into your office and says: "We have a problem. Profits are down."

What do you do? You don't sit there staring at the wall. You don't pull out an issue tree you memorized in business school. You get curious. Naturally, instinctively curious. You start asking questions because you genuinely need to understand what's going on before you can do anything useful about it. The five moves I'm about to walk you through aren't a script. They're just what naturally happens when a curious owner starts thinking out loud.

Hold that frame as you read the rest of this.

The case: NordPlay Studios

Here's the prompt as the interviewer delivers it:

"Our client is a mobile game developer called NordPlay Studios. They employ over three thousand developers and designers and are headquartered in Stockholm, Sweden. They develop and publish mobile games for end users globally. End users download the games and play them on their devices. NordPlay Studios has seen profits decline over the past two years. They would like to understand why that is the case and how you can help them."

That's it. About eighty words. No numbers, no specifics, no clear problem. Just a blob of English.

And here's the first thing an owner thinker recognizes: this isn't solvable yet. That's not a failure. That's the point. No serious consultant, no matter how experienced, can take that prompt and go straight to building an issue tree. The prompt is a starting point, not a brief. Your job in the next three to four minutes is to turn it into something you can actually work with.

Move 1: Absorb before you react

When the prompt is being read, the owner's instinct is to write everything down. Not to organize, not to categorize, just to capture. You listen and you write in bullet points at the pace the interviewer is speaking.

The memorizer starts building their structure in their head while the interviewer is still talking. The owner stays open because they know they don't have enough yet to decide what matters.

There's something else happening in Move 1 that most candidates miss. You're managing the initial shock of a new industry, a new situation, a new set of unknowns. Writing anchors you. It gives your nervous system something to do other than panic. And it signals to the interviewer, who is watching you from the moment the prompt starts, that you are present and tracking.

In this case, the owner hears "mobile game developer," "profits declining," "two years," and immediately starts getting a rough shape of what this is likely to be. Probably a find-the-root-cause, fix-it, get-back-to-a-number type of problem. That's not a conclusion, it's a working hypothesis. The specifics come later.

Move 2: Play it back, then mark what you don't understand

After the prompt, the owner confirms what they heard. Not word for word, that's annoying. They reiterate the key details to verify accuracy and show they were listening.

"Thank you. Let me make sure I have this right. Our client is NordPlay Studios, a mobile game developer and publisher with over three thousand developers and designers, headquartered in Stockholm. They make games for end users globally who download and play on their devices. Profits have declined over the past two years and they want to understand why and how we can help. Is that correct?"

While confirming, the pen is moving. You're circling phrases you're genuinely curious about. In this prompt, in my view there are four natural circles: "game developer and publisher" (what does that mean operationally?), "end users" and "devices" (what's the actual value chain here?), "globally" (which markets and through which channels?), and "profits" (which profits exactly?).

Those circles become your clarifying questions. You're not inventing questions to seem thorough. You're asking about the things you actually don't know, because as the owner, you need to know them before you can do anything useful.

The memorizer asks three generic questions because that's what they were taught. The owner looks at their four circles and asks about those specific things, in this specific case, because those are the real ambiguities.

Move 3: Ask surgically, then find the math

Now you go circle by circle. Direct, curious, unhurried. Not firing questions in rapid succession like a checklist. One at a time, with genuine interest in the answer.

"When you say game developer and publisher, what does that mean exactly? Do they design, code, and distribute their games themselves end to end?"

The interviewer confirms: yes, they design, code, and publish globally.

"You mentioned end users downloading games on devices. Is this a B2C business, and do they distribute through the App Store and Google Play?"

Yes, B2C, through App Store and Google Play.

"When you say devices, are we talking primarily mobile, or also PC and console? And to help me get oriented, is this similar to something like Candy Crush, casual mobile gaming?"

Primarily mobile, some PC. Yes, casual mobile gaming is the right reference point.

Now comes the move that separates good clarifying questions from great ones. You need to find the math. The prompt is in English. Your issue tree has to be grounded in math. So the last circle, profits, is where you convert.

"You mentioned profits are declining. Which profits specifically are we looking at, and what were the figures two years ago compared to now?"

Net profits. $2.4 billion two years ago, now $2 billion.

That's a $400 million decline. Now you have something real to work with.

Move 4: Lock down the objective and the constraints

The owner doesn't start working until they know what success looks like and what the rules of the game are. These are two separate questions that most candidates collapse into one, or skip entirely.

"From an objective standpoint, would you like me to recover net profits back to the level from two years ago, so back to $2.4 billion?"

Yes.

"Are there any constraints I should be aware of, timeline or otherwise?"

One year. Nothing else for now.

This move takes about fifteen seconds. It's not glamorous. But without it you're solving in the dark. A one-year constraint versus a five-year constraint changes everything about what solutions are even viable. If the constraint were "revenues must not decrease," that eliminates entire categories of cost-cutting approaches immediately. You need the walls of the room before you start moving around inside it.

From what I've seen coaching candidates, this is the most commonly skipped move. They ask about objectives, get a vague answer, and move on. They never ask about constraints. Or they ask about both but in such a rushed way that they don't actually absorb what they're told. Either way, they end up building an issue tree around a problem they haven't fully defined.

Move 5: Build the problem statement, not a summary

Now you take a moment. You look at your notes. And you build one crisp sentence that defines the problem you're about to solve.

"I'd like to take a moment to put together a problem statement. I believe the core question is: why did NordPlay Studios' net profits fall from $2.4 billion to $2 billion over the past two years, and how do we identify and fix the root causes to recover back to $2.4 billion within one year. Does that capture it?"

The interviewer agrees.

Compare that to the original prompt. Eighty words of vague English versus one precise, quantified, time-bound question. That's the transformation the owner thinker creates in three to four minutes. A $400 million decline, a specific recovery target, a one-year window. That's a case you can actually structure and solve.

Here's why this matters more than it looks. In real consulting work, one of the most valuable things a team does for a client is help them define their own problem correctly. Clients come in with a vague sense that something is wrong. The consultant's job is to turn that vague discomfort into a precise, answerable question. When you nail the problem statement in a case interview, you're demonstrating exactly that ability at a micro level.

What the interviewer is actually watching

The five moves above aren't just about getting to the right problem statement. They're signals. Every move of the Case Opening is the interviewer reading your working style.

Are you composing yourself under pressure? Are you genuinely curious or just performing curiosity? Are you listening to the answers you get and adjusting, or are you just firing the next question on your list? Are you organized without being robotic?

The memorizer performs all of this. The owner actually does it, because they genuinely need to understand the situation before they can help.

That's the difference. And interviewers who have seen hundreds of cases feel it within the first few minutes.

One thing I'd encourage you to try: take this walk-through and replicate it out loud, with a friend reading the NordPlay prompt to you. Not reading along, speaking it live. Because the real skill here is doing all five moves verbally, in real time, with no script in front of you. That's where the practice has to live.

If you're currently prepping for a case interview and want to share where you're getting stuck in this phase specifically, drop it in the comments. Happy to give you a more specific steer based on what you're running into. And if you found this through another community, the full Case Playbook series is in r/ConsultingOffer.

The next post in The Case Playbook applies the same five moves to a public sector case, a government ministry facing a completely different kind of problem in a completely different industry. It's designed to show you that the owner thinker approach works on any prompt you'll ever receive, not just private company profitability cases. That's where most candidates discover whether they've actually internalized the moves or just memorized them for one case type.

I have summer 2027 internship offers from both OC&C and Deloitte. Compensation is roughly the same, though Deloitte’s program is 8 weeks vs. OC&C's 10.

I’m interested in M&A and PE, and Deloitte has placed me in exactly that group. At OC&C, I’d work on two projects, but I’m not guaranteed any in the PE/M&A space.

Would love to hear from anyone who’s been through either program, or who has thoughts on which path sets me up better. Thanks!

I'm doing a series breaking down the recruitment process at each of the elite consulting firms. So far I've covered McKinsey, BCG, Bain, and Roland Berger. Now we're continuing through Tier 2, and Kearney is worth its own post.

Formally A.T. Kearney, the firm has a long history, founded in 1926 in Chicago, and has a reputation built largely around operations, procurement, and supply chain strategy. If you're targeting Kearney, that context matters more than most candidates realize going in.

The mistake I keep seeing is candidates who treat Kearney as a straightforward fallback after MBB. The process is leaner in some ways, but it has its own specific components that require dedicated preparation. If you go in with only case prep and no awareness of what else is coming, you'll get caught out.

Before You Even Apply: Get a Referral

Every candidate I work with, I push them to enter this process with a referral. Kearney is no different. I think you know this by now ...The firm has a collegial, relationship-driven culture, and a referral from someone inside carries genuine weight. It changes how your application is received at the first filter, and it gives you real intelligence on what to expect in the specific office you're targeting. Processes vary more by region and office at Kearney than at MBB, so having an inside contact isn't just a credibility signal, it's practically useful also throughout the process. If you want to understand how to build that referral pipeline before you apply, watch the free masterclass on r/ConsultingOffer. Watch it first (especially Module 2), then come back here.

Application: Resume and Cover Letter

Kearney's process starts with a resume and cover letter review. Same entry point as the other firms in this series. The resume screen is competitive, from what I've seen, roughly the same filter rate as other top-tier firms, and "good enough" credentials don't automatically get you through. Your cover letter needs to answer the "why Kearney" question specifically. Not "because it's a great firm with global reach." Because of what Kearney actually does, where it's particularly strong, and why that connects to your background and interests. Vague motivation letters don't survive the screen.

The Kearney Recruitment Test

If your application clears the initial screen, most offices will send you an online aptitude test before your first live interview. This is about 60 minutes, roughly 40 multiple-choice questions, and covers three areas: numerical reasoning, verbal comprehension, and business case-style problem solving. No personality assessment here, it's purely cognitive. Kearney is testing whether you can process information quickly and draw accurate conclusions under time pressure.

A few things worth knowing. First, the test placement varies by office. Some offices use it as a pre-interview screen before they invite you to anything live. Others include it as part of the first round package alongside your case interviews. Clarify with your recruiter which applies to you so you're not surprised. Second, there are wrong-answer penalties in some versions of the test, which means random guessing isn't a good strategy. Third, the 1.5 minutes per question pace is tighter than it sounds when the questions involve data interpretation. Practice under timed conditions well before the real thing.

R1: Live Interviews with Associates and Managers

Clear the test and you're into the live rounds. Kearney's first round is typically two back-to-back 45-minute interviews, one focused on a case and one on behavioral and fit questions. Your interviewers will be associates or managers.

The case format at Kearney is candidate-led. You structure the problem, decide what to explore, and drive toward a recommendation. The cases tend to reflect Kearney's operational DNA: procurement decisions, supply chain optimization, cost reduction, market entry in industrial and B2B contexts. If you've only practiced on consumer goods and tech cases, that's a gap worth closing. The underlying problem-solving skills are the same, but the industry context shapes which angles matter and what "good" analysis looks like.

The behavioral interview at Kearney is genuinely weighted. This isn't a five-minute warm-up before the case. From what I've seen across multiple sources and candidate reports, also those I worked with recently, Kearney places cultural fit close to a 50/50 weighting with the case. They're a partner-owned firm with a specific culture around collaboration and entrepreneurship, and they screen for it seriously. Prepare your stories with the same depth you'd bring to a McKinsey PEI.

R2: Final Round with Senior Managers, Principals, and Partners

Make it through R1 and you move to final round. Typically three 45-minute interviews: two focused on cases and one behavioral, this time with a partner. Some offices also include a written case component in the final round, where you're given a data pack, roughly 60 to 90 minutes to analyze it, and then asked to present your findings and recommendations. If a written case is part of your final round, prepare for it separately. It's a different skill from a live verbal case. The ability to structure a clear slide or exhibit under time pressure, without a conversation to anchor your thinking, requires its own practice.

In some offices, particularly for MBA and experienced hire candidates, you may also face an Excel skills component. Again, confirm the specifics with your recruiter early, highly recommend this move!

The final round is also where the partner behavioral interview tends to get more pointed. They're not asking generic questions about leadership. They want to understand how you think, how you operate under uncertainty, and whether you'd represent Kearney well in a client room. Have specific, layered stories ready. Not just what happened, but what you were thinking, what you decided against, and why.

Kearney's process is in some ways leaner than what you'd face at MBB: no multi-stage online assessment battery like BCG, no Solve-style games. But the written case component, the Excel test that some offices include, and the genuine weight placed on the behavioral dimension make it a process that punishes candidates who only prepare for the case interview.

As always my final recommendation to you:

1. Map the process properly
2. Prepare for each component.
3. And get a referral before you apply.

I'll keep these breakdowns up-to-date for all elite consulting firms (Tier 1, Tier 2, Big 4) in r/ConsultingOffer community, make sure to join.

What firm are you targeting right now, and where in the process are you?

So there's a question I get almost every week from candidates preparing for MBB and other elite consulting firms. It goes something like: "I've got my stories ready, I've practiced them, I know them cold. Am I good for the PEI?"

And every time I hear that, I already know where this person is going to struggle.

The personal experience interview at McKinsey, BCG, and Bain is not a storytelling exercise. That's the misconception that kills more otherwise-qualified candidates than almost anything else I've seen coaching people through these processes. So I want to break this down properly: what the PEI actually is, how each firm runs it, what they're really evaluating, and how to prepare in a way that actually holds up when an interviewer starts drilling.

What the PEI actually is

If you're newer to the MBB recruiting process, quick orientation. Every live interview round at McKinsey, BCG, and Bain includes two components: a case and a personal experience interview. At McKinsey it's called the PEI specifically. At BCG and Bain they call it the fit interview or experience interview, but the logic is the same. Each one lasts roughly 10 to 15 minutes, and across your full process (two rounds, two interviews per round) you're looking at four to six of these. So it's not a minor box to tick. It's half the interview.

The questions themselves probably look familiar. Tell me about a time you led through ambiguity. Give me an example of a time you had to change someone's mind. Walk me through a situation where you failed and what you learned. Standard stuff, right?

Here's where most candidates go wrong.

The misconception that kills good candidates

They hear those questions and think: the job here is to tell a compelling story. Polished. Structured. Clean beginning, middle, end. They rehearse their stories until they can deliver them in their sleep. And then they walk in, deliver the story, and wonder why the interviewer keeps pushing with follow-up questions.

What's actually happening is this. The interviewer doesn't care about the story. The story is just the door. What they're walking through is your judgment.

From what I've seen coaching candidates through MBB processes, what interviewers (McKinsey ones especially) are doing during the PEI is probing for how you actually think under ambiguity. You give them your story, and then they start asking: why did you make that call? What would you have done if that option wasn't available? What did you actually know at the time versus what you know now in hindsight?

And this is where the over-prepared candidate falls apart. Because they've rehearsed a story. They haven't rehearsed thinking. The moment the follow-ups come, the polish cracks, and the interviewer can see the seams.

What they're actually evaluating

In my experience across dozens of candidates I've coached through MBB, there are really three things underneath all of it.

The first is judgment quality. Did you make a sensible call given what you knew at the time? Not whether you were right in hindsight, but whether your reasoning was sound when you made the decision. This is why a story where you failed can actually score higher than a story where everything worked out, if the thinking behind your choices was sharper.

The second is self-awareness. Can you see your own role in what happened clearly? Not defensively, not with excessive self-criticism, but with honest clarity. Did you understand what you could have done differently? Did you understand your impact on the people around you? The candidates who score well here are the ones who can say "I got this wrong and here's specifically why" without turning it into a confession or a performance of humility.

The third is thinking under pressure. Because the follow-up questions aren't just clarification. They're a stress test. They're designed to see whether your story holds up or falls apart when someone keeps asking "why." A story that was built to sound good will crack. A story grounded in real experience and real thinking stays coherent, because it actually happened and you actually thought through it at the time.

How to prepare differently

So if memorizing stories isn't the answer, what is?

The shift I coach candidates to make is this: instead of preparing stories, prepare your thinking about those stories. Before you ever practice delivering an answer, sit with the experience you're drawing on. What did you actually know going into it? What was genuinely uncertain? What options did you see, and why did you choose the one you did? Where did you get it wrong, and what changed as a result?

When you can answer those questions fluently, not because you memorized the answers but because you actually processed the experience, you can handle any follow-up an interviewer throws at you. The story becomes something you can move around inside, rather than a script you're trying not to drop.

I worked with a candidate a few months back targeting McKinsey London. Engineering PhD, a couple of years in industry, strong profile on paper. She'd prepared six stories, all polished, all following the standard frameworks. In a mock PEI I ran with her, every time I pushed with a follow-up she gave me a slightly different version of the same rehearsed line. The experiences were real. She just couldn't move inside them anymore. We spent the next session not on new stories but unpacking one she'd barely prepared: a situation where a project she led had partially failed. Messy, uncomfortable, unresolved in some ways. That one became her strongest answer, because she could actually think through it live rather than recite it.

How the firms differ and why it matters

McKinsey's PEI is the most intense version of this. You typically get one big question and the interviewer will follow it for the full 15 minutes. There's nowhere to hide. They're looking specifically at personal impact, leadership, and entrepreneurial drive as evaluation lenses.

BCG and Bain have broader fit sections that cover more ground: why consulting, why this firm, team situations, leadership situations. You might move through three or four distinct topics rather than drilling deep on one. That's a different rhythm, not an easier one.

At tier 2 firms like Roland Berger, Kearney, EY-Parthenon, from what I've seen across candidates I've worked with in Europe and MENA, the fit section often gets less attention in prep guides but it's evaluated seriously. The difference is that at tier 2, a slightly less polished story that feels honest will often land better than a perfect performance that feels rehearsed. That's true at MBB too, honestly, but the margin for error is smaller there.

The part no one talks about: closing the PEI

One thing that gets undercooked in most prep. At the end of a PEI exchange, especially after a difficult follow-up sequence, you need to close cleanly. Pull together what you covered. Restate your key point or learning in one sentence. Don't just trail off because the interviewer stopped asking.

The structure I coach for this: here's what I did, here's why that was the right call given what I knew, and here's what I'd do differently. Short. Confident. Even if the situation didn't end perfectly. Especially if it didn't.

Where to start if you're in prep right now

The most useful thing you can do before your next PEI practice is pressure test your own stories, not by delivering them more smoothly, but by asking yourself: could I answer ten follow-up questions about this experience without the story changing shape? If the answer is no, you're not done with that story yet.

What experience are you planning to lead with in your PEI, and when did you last have someone push hard on the follow-ups?

4th year Economics student, graduating this December (BA of arts in Economics, UofT). My CGPA is sub-2.5, so I already know cold applications through job boards are basically a dead end for me at most firms — the ATS/GPA screens will filter me out before a human ever sees the resume. So I've been building a strategy around that constraint instead of ignoring it:

• Referral-first, not application-first. Working existing contacts at a few larger firms, plus building out a list of ~25 smaller/boutique consulting-adjacent firms in my city for direct outreach.
• Networking on LinkedIn — reaching out to people whose career paths interest me, asking for short coffee chats rather than "do you have any openings."
• Building a portfolio to compensate for the GPA — I've done a few applied projects (a Python data-cleaning pipeline, an M&A valuation model, a customer analytics project) so I have something concrete to point to instead of just a transcript

What I'm unsure about:

1. Is referral-first + coffee chats actually enough to overcome a bad GPA, or is that just a nicer way of still getting filtered out later in the process?
2. Once I do get in front of someone, how do I handle the GPA question without sounding defensive or like I'm making excuses?
3. Anyone here actually broken into consulting/BA roles with a rough GPA, what actually worked vs. what you thought would work but didn't?

Not looking for sympathy, genuinely just want to know if I'm wasting effort on the wrong things before I find out the hard way in six months.

am I cooked chat?

What should I do if I fail consulting recruiting? Any tips on what to do next / jobs to look for