BCG Case Interview Tips: What the Firm Actually Tests

At McKinsey, the case interview follows a fairly consistent structure: prompt, structure, data analysis, recommendation. It's a rigorous process that rewards systematic thinking. At BCG, the conversation moves faster and meanders more. The interviewer is more likely to interrupt your structure to push you in a new direction, ask a left-field question, or test whether you can hold your thinking while being challenged.

Think of it like two different types of chess players. The McKinsey interview is like playing a game where the rules are fixed and your job is to execute a sound opening: disciplined, structured, sequenced. The BCG interview is more like playing against someone who knows you've studied openings, so they take you out of book on move four, on purpose, to see if you can think when you can't rely on pattern recognition.

The implication: BCG rewards adaptive thinking. Knowing your frameworks cold is necessary. Being able to hold your framework loosely while listening hard to what the interviewer is actually telling you. That's what gets you the offer.

BCG popularized what they call hypothesis-driven consulting. Form a working belief early, test it ruthlessly, and update it as evidence comes in. They hire for this disposition explicitly.

Most candidates hear "hypothesis-driven" and think it means "guess early and often." It doesn't. Here's the real model.

Imagine you're a scientist who has just been handed a jar of unknown liquid. A bad scientist says: "I don't know what this is. I will run 40 tests and see what they show." A good scientist looks at the color, viscosity, and smell, forms a hypothesis ("I think this is a diluted acid"), and runs the one test that would either confirm or falsify it. If confirmed, they move on. If wrong, they update their hypothesis and run the next most informative test.

BCG analysts work this way. They don't collect data until they have a hypothesis the data could disprove. The hypothesis isn't a guess they're attached to. It's a bet they're willing to lose. When the interviewer hands you data that contradicts your hypothesis, the right move is not to rationalize your way out of it. It's to say: "That's interesting. That actually changes my hypothesis. Let me revise." BCG interviewers test for exactly that moment.

Many BCG offices use a written case component, sometimes called the Written Case Interview or a group case exercise. You receive a packet of exhibits (often 10 to 15 pages) and have a set time (usually 1 hour) to analyze and write up a recommendation. Then you present it to a panel.

This tests something most pure verbal case prep misses: the ability to synthesize a large body of evidence quickly and communicate conclusions concisely in writing. A one-hour clock on 15 exhibits is brutal if you haven't practiced reading charts efficiently.

The written case follows the same logic as any BCG case: hypothesis first, then exhibit analysis to confirm or revise. The difference is you have to be disciplined about time. Spend the first 10 minutes reading the prompt and every exhibit headline before analyzing any of them in depth. Get the lay of the land. Then form your hypothesis. Then go deep only on the exhibits that bear on your hypothesis.

Candidates who fail the written case almost always do so by spending 30 minutes on the first three exhibits and never reading the last six. The answer usually lives in exhibit 11.

Comfort with ambiguity. BCG will give you incomplete information and watch what you do with it. Do you ask for data that doesn't exist, or do you make a reasoned assumption, state it explicitly, and keep moving? The second approach is right.

Intellectual flexibility. When the interviewer challenges your hypothesis, do you defend it reflexively or update it based on logic? Defending a hypothesis in the face of contradicting evidence signals rigidity. Updating it signals intellectual honesty.

Communication under pressure. Can you explain a complex finding in plain English while being interrupted? BCG cases often involve an interviewer who plays a skeptical client. The ability to translate analytical findings into clear language without jargon, while holding your ground, is a core consulting skill.

Drive and curiosity. Are you engaged with the problem? BCG wants people who find business problems genuinely interesting, not people who are performing interest to get a job. This is hard to fake. Interviewers who've spent years in client meetings know the difference.

The Microsoft turnaround case is a strong analog for BCG preparation. It's a strategy problem with incomplete early data, multiple competing hypotheses, and a turning point where the evidence forces a complete reframe of the initial structure.

Practice getting challenged mid-structure. Most solo case prep lets you complete your structure uninterrupted. BCG won't. Ask a practice partner to interrupt you after your first branch and say "What if I told you cost isn't the problem. It's pure revenue?" Practice updating your structure in real time without losing composure.

Do at least 3 written case simulations. Find a 10-page BCG exhibit pack (BCG publishes samples on their website). Set a timer for 60 minutes. Write a one-page recommendation at the end. Grade yourself on: did your recommendation come from the data, or did you retrofit the data to a conclusion you'd already formed?

Practice saying "that changes my hypothesis." Out loud. It should feel natural. If it feels like admitting defeat, you haven't internalized BCG's actual definition of smart. Updating based on evidence isn't weakness. It's the whole method.