Profitability Case Interview: How to Solve It in 2026 (With Examples)

Last Updated on June 23, 2026

By Florian Smeritschnig, former McKinsey Senior Consultant. Updated June 2026

A profitability case interview asks you to diagnose why a company’s profit is changing, or how to grow it, and then recommend a fix. You start from Profit = Revenue – Costs, break each side into the drivers, isolate the one or two that actually matter, analyze the reasons of change, and link your diagnosis to a clear action.

Here is what trips up most candidates: a profitability case is not a formula exercise.

They memorize a generic framework, repeat “revenue minus costs,” and freeze the moment the problem gets even slightly messy. That is the opposite of what interviewers reward. Your real job is to break down what is happening, find the key drivers, and focus your analysis where it changes the answer.

I already saw profitability cases becoming less common during my time at McKinsey, but after coaching more than 2,200 case sessions, I still consider them one of the clearest tests of whether a candidate can move beyond formulas and diagnose a business problem properly.

This guide shows you how to do that from first principles, the way strong candidates actually do it, with a worked example and nine practice scenarios.

Key Takeaways

• Lead with diagnosis, not a template. Quantify the profit gap first, then structure your investigation around it.
• Break profit into drivers: Revenue (price, volume, mix) and Costs (fixed, variable), then go two to three levels deeper where the numbers point.
• Use the 80/20 rule. Spend your time on the segment or driver that explains most of the change, not on covering every branch equally.
• Profitability cases have become less common over time but are still employd by all firms.
• Profit can fall while revenue grows. Never analyze revenue and costs in isolation; watch the trade-offs between them.
• Interviewers score your thinking, not the “right” number. A clean diagnosis tied to a concrete recommendation beats a memorized framework every time.

What Is a Profitability Case Interview?

A profitability case gives you a company whose profit is moving in the wrong direction, or not moving at all, and asks you to figure out why and what to do about it. You will see it framed as falling profits, shrinking margins, a cost spike, or a target the company is missing.

It used to be a more common case type at McKinsey, BCG, Bain, and the rest of the top firms, however, its importance has gone down as it was replaced with more modern, wildcard cases and scenarios.

Firms still use it because it mirrors real client work. McKinsey describes its Problem-Solving Interview as a test of how you “structure tough, ambiguous challenges, identify important issues, deal with the implications of facts and data, formulate conclusions and recommendations, and articulate your thoughts.”

A profitability case is one way to test exactly that in 20 to 30 minutes.

The Profit Equation Is Your Starting Point, Not Your Answer

Every profitability case sits on one piece of arithmetic:

Profit = Revenue – Costs

That is true, and it is where you begin. But reciting it is not solving the case. The work is breaking each side into drivers you can actually investigate, then deciding which branch to chase.

The candidates who stand out do one more thing: they rename the buckets to fit the business.

For a beverage maker, “variable cost” becomes raw materials and distribution. For a SaaS company, it becomes hosting and customer acquisition.

That single move tells the interviewer you are thinking about this company, not regurgitating a case interview framework you found online or in some outdated book.

The First-Principles Structure: Diagnose, Then Drive

Forget the idea that there is one template to memorize. There is a repeatable way to think, and it has four moves.

Step 1: Quantify and Isolate the Problem -> What is happening?

Before you structure anything, pin down the change. How big is the profit drop, over what period, and is it revenue, cost, or both? Ask for the numbers. A 20% profit decline on flat revenue points you straight at costs. A profit decline with rising revenue points at margin or mix. You cannot structure an investigation until you know which side of the equation moved.

The goal is simple:

• Where exactly is the problem?
• How big is it?

Without this step, everything that follows is guesswork.

Step 2: Segment to Find Where It Lives (the 80/20 Rule) -> What is happening?

Before jumping into explanations, isolate the issue numerically. Profit problems are rarely spread evenly. Break the business into segments that matter: product lines, regions, customer types, or channels. Then find the 20% of the business driving 80% of the change. If one product line explains most of the decline, that is where your time goes. Analyzing every segment equally is how candidates run out of time without an answer.

Step 3: Run the Driver Analysis (Internal vs External) -> Why is it happening?

Once you know where the problem lives, work out why. Sort the causes into two groups:

• Internal: pricing decisions, production or distribution issues, cost inefficiencies, a shift in product mix, an aging contract.
• External: commodity prices, new competition, regulation, tariffs, a demand shift, FX moves.

This is where you show business judgment. The number tells you a cost rose 8%; the driver analysis tells you whether that is a one-off commodity spike or a structural problem with a single-supplier dependency.

Step 4: Link the Diagnosis to a Recommendation -> What can we do about it?

A diagnosis with no action is half a case. Close the loop: state the driver you found and the specific move that addresses it. Weak candidates stop at “costs went up.” Strong candidates say “raw-material costs rose 8% because of an external commodity spike and an over-reliance on one supplier, so I would hedge the contract, qualify a second supplier, and pass part of the increase through on low-elasticity SKUs.”

This is not a framework to memorize. This is a diagnostic map to understand what is actually happening in the business.

How Top Candidates Think (and Why Most Fail)

The pattern that separates the top 1% is simple to describe and hard to execute under pressure:

• Breadth first, then depth. Lay out all the relevant areas, then drill two to three levels into the one that matters. Most candidates either stay shallow everywhere or tunnel into the first idea they have.
• Hypothesis-led, not exhaustive. They form an early view (“I would bet this is a cost problem in one product line”) and test it, instead of mechanically walking every branch.
• Numbers in service of a story. They use the case math to confirm where the problem is, then explain what it means for the business.

Average candidates apply a template. Top candidates use structure to diagnose a real business problem.

A Worked Profitability Case Example (With Numbers)

Here is a clean walk-through so you can see the method in motion.

Note: this is a condensed version for illustration. In a real interview, you would not be given all numbers upfront. You would need to build the structure, ask for data, and analyze it step by step.

Case context

Your client is a mid-sized European manufacturer of packaged food products. Over the past year, profits declined by 20% while revenues remained stable. The CEO wants to understand what is driving the decline and how to respond.

How to approach this (process first, not numbers)

Before jumping into analysis, define your approach clearly.

You are solving this in two layers:

First, build your structure:

• A numerical analysis: where is the change coming from and how large is it
• A driver tree: what could be causing it and why

Then execute sequentially:

• First isolate the issue numerically
• Then analyze the underlying drivers

In the process, the interviewer will provide data:

• verbally
• through exhibits (charts, tables, graphs)

Your job is to:

• interpret the data correctly
• quantify impact where possible
• extract insights, not just describe numbers

Step 1: Isolate the issue (numerical analysis)

You start by clarifying the financials:

• Revenue = €100M (unchanged)
• Costs increased from €80M → €84M
• Profit dropped from €20M → €16M (−20%)

Conclusion:
The entire profit decline is driven by a €4M increase in costs.

Step 2: Segment the problem

Break costs down further:

• Fixed costs: €30M → €30M (no change)
• Variable costs: €50M → €54M (+€4M)

Insight:
The issue is fully concentrated in variable costs.

At this point, you have answered:

• Where is the problem?
• How big is it?

Step 3: Drill down (structured driver analysis)

Now move to your driver tree.

Variable costs typically include:

• raw materials
• labor
• logistics

You probe each area and receive the following:

• Raw material costs increased by 8%
• Labor and logistics remained stable

Step 4: Quantify impact

• Raw materials: €50M
• 8% increase → +€4M

Conclusion:
This fully explains the profit decline.

Step 5: Explain the “why” (driver analysis)

Now go beyond the numbers.

External drivers:

• Increase in global commodity prices
• Supplier market consolidation

Internal factors:

• Dependence on a limited number of suppliers
• Lack of long-term pricing agreements

This step is critical. Many candidates stop at the numbers. Strong candidates explain the underlying cause.

Step 6: Implications and actions

You can now form a clear, structured story:

• Profit decline is not driven by revenue
• It is fully explained by higher raw material costs
• The root cause is external cost pressure, amplified by supplier dependence

From here, recommendations follow logically and through structured case interview brainstorming:

• Renegotiate supplier contracts
• Diversify supplier base
• Explore hedging strategies
• Evaluate selective price increases

What this example teaches. Notice what did the work. Not a memorized tree, but a sequence: isolate, segment, find the driver, size the fix. The structure followed the numbers, and the numbers led to an action.

How Profitability Cases Differ by Firm and Experience Level

The core method is the same everywhere, but the emphasis shifts. Knowing this lets you read the room instead of running one script.

If you are short on time, build the universal method first, then spend your last few sessions tuning for your target firm. Our guide to case interviews maps the format differences in detail.

Common Profitability Case Mistakes

After thousands of mock cases, the same five errors cost candidates the offer:

1. Jumping into analysis without structure. Diving into numbers before you have isolated revenue versus cost reads as panic, not problem-solving.
2. Treating it as a formula exercise. Reciting “revenue minus costs” with generic buckets signals memorization. Interviewers see it instantly.
3. Going too shallow. Stopping at “costs went up” without finding the specific line and driver leaves the case unsolved.
4. Analyzing everything equally. Spreading time evenly across every branch instead of chasing the 80/20 means you run out of clock with no answer.
5. Weak linkage between diagnosis and recommendation. A great diagnosis that does not connect to a concrete action is an incomplete case. Always close the loop.

Advanced Insights for the Top 1%

These are the points that separate a strong pass from a great one.

Profitability cases are rarely “pure.” A profit prompt routinely opens into pricing, operations, market entry, growth strategy, or even an M&A discussion. Treat the case types as connected lenses on one problem, not separate templates to swap in.

Profit can decline even when revenue grows. This is the trap that catches over-confident candidates. If the company chased volume by discounting, or grew a low-margin product line, revenue rises while profit falls. The mix driver is doing the damage. Always check whether growth is the cause, not the cure.

The interviewer is testing your thinking, not your answer. There is rarely one correct number. What they grade is whether your structure was clean, your prioritization was sharp, and your logic held under pressure. A defensible recommendation built on clear reasoning beats a “perfect” answer with no visible path to it.

Revenue and costs interact. Cutting a cost can shrink revenue; raising price can drop volume. Strong candidates name the trade-off instead of optimizing one side in a vacuum.

How to Practice Profitability Cases Effectively

Volume is not the goal; deliberate practice is. The fastest-improving candidates I coach at StrategyCase do four things:

• Stop memorizing frameworks. Practice building structure from scratch on a blank page. The skill is generating a fit-for-purpose tree, not recalling one.
• Train math inside cases, not in isolation. Profit math is easy on a drill sheet and hard mid-conversation. Practice the arithmetic the way you will use it, embedded in a live case. The same applies to MECE structuring and brainstorming.
• Simulate pressure. Solve out loud with a partner or coach, not silently in your head. Communication is graded too; practice the top-down delivery interviewers expect.
• Reflect after every case. What did you miss, where did the structure sag, what would you do differently? One reviewed case beats five rushed ones.

Practice Profitability Case Questions

Work these nine scenarios. Each one pushes a different driver, so you cannot reuse the same structure twice.

For fully worked solutions, see our collection of case interview examples from McKinsey and other firms.

Profitability Cases vs Other Case Types

Profitability is the hub that other case types branch off. Recognizing the connection helps you pivot smoothly when the interviewer changes direction.

Frequently Asked Questions

Related Guides

• The Complete Guide to Case Interviews (start here)
• Case Interview Frameworks: When to Use Them and When Not To
• Case Interview Math: The Ultimate Guide
• Market Entry Case Interview
• Pricing Case Interview

Final Thoughts: Master the Method, Not the Template

Profitability cases reward the candidate who can diagnose a real business problem, not the one who recites the cleanest framework. Get the method right, quantify, segment, find the driver, recommend, and you will handle any profit prompt the interviewer throws at you, in any industry.

That is the whole philosophy behind StrategyCase: build the skill, not the template. Start with the Case Interview Academy. If you want direct feedback on your structuring, charts analysis, math, and communication, book a coaching session and we will pressure-test your approach together.

About the author: Florian Smeritschnig is a former McKinsey Senior Consultant who evaluated candidates at the firm and has delivered 2,200+ mock interviews and coaching sessions. Through StrategyCase, he has helped 700+ candidates win offers at McKinsey, BCG, Bain, and other top firms.