Case Interviews Explained

A case interview is a strange hybrid of exam, conversation and improvisation. The interviewer describes a business problem, such as a company whose profits are falling or a startup deciding whether to enter a new market, and asks you to work through it with them. There is no single right answer.

What they are watching is how you think: how you break a messy question into parts, how you use numbers, how you respond to new information and how clearly you explain your reasoning. Case interviews are strongly associated with consulting, but variants appear in finance, technology, marketing and many other fields.

Formats and expectations differ between employers. This guide describes common patterns and invented examples. It quotes no success rates. It is general information, not career advice. Check what each employer expects, and use your careers service and practice resources.

What a case interview is

In a typical case interview:

1. The interviewer presents a situation orally or on paper.
2. You ask clarifying questions.
3. You structure your approach.
4. You analyze, often with data supplied on request, and do some calculations.
5. You discuss findings, and adapt as new facts emerge.
6. You give a recommendation.

Cases can last twenty to forty minutes. They may be interviewer-led, where the interviewer drives the questions, or candidate-led, where you decide what to explore.

Why employers use them

• To see structured thinking. Can you organize a complex problem?
• To assess analytical skill. Can you work with numbers and logic?
• To test communication. Can you explain clearly and concisely?
• To see composure. How do you handle pressure and ambiguity?
• To check curiosity and judgment. Do you ask sensible questions and make reasonable assumptions?
• To preview the job. Many roles involve solving problems with clients and colleagues.

Common types of case

Profitability. A company's profits have dropped. Why, and what should it do? You examine revenue and cost drivers.

Market entry. Should a company enter a new market or launch a new product? You assess market size, competition, capabilities and risks.

Market sizing (estimation). Estimate a quantity, such as the number of coffees sold in a city per day. You break it into logical steps with reasonable assumptions.

Growth strategy. How can a company increase revenue? You consider customers, products, channels and pricing.

Pricing. What price should a company charge? You consider costs, value, competition and demand.

Mergers and acquisitions. Should a company buy another? You consider fit, synergies, price and risks.

Operations. How can a company improve a process or reduce costs?

Public sector and nonprofit cases. How should a charity or agency allocate resources?

Brainteasers and logic puzzles. Less common today, but some interviews include them.

Creative or marketing cases. Design a campaign or product concept.

Technical or data cases. Interpret data or outline an analysis.

You do not need to know industries in depth. You do need to think systematically.

A simple structure for any case

1. Listen and clarify. Take notes. Repeat the problem in your own words. Ask clarifying questions about the objective, context, constraints and definitions: What does success mean? What time frame? What do we know about the company?
2. Take a moment to structure. Ask for a minute to organize your thoughts. Write down a simple structure with three or four key areas to explore.
3. Share your structure. Explain it briefly and logically.
4. Dive into the areas. Ask for data, analyze, and communicate as you go. Prioritize areas likely to matter most.
5. Summarize findings. Pull together what you have learned.
6. Recommend. State your recommendation, supporting reasons and risks, and suggest next steps.

Throughout, think aloud so that the interviewer can follow.

Using frameworks wisely

Well-known frameworks, such as breaking profit into revenue and costs, or considering customers, competitors, company and context, can help you start. But they are tools, not scripts.

• Use a framework as a starting point, then tailor it to the problem.
• Avoid reciting a framework mechanically. Interviewers notice.
• Make your structure specific. For a coffee chain, you might look at customer traffic, spend per visit, store costs and competitors, not generic categories.
• Be mutually exclusive and collectively exhaustive where you can: categories that do not overlap and cover the main possibilities.
• Prioritize. Say which area you will explore first and why.

Working with numbers

Most cases involve some math.

• Practice mental arithmetic: multiplication, division, percentages and rounding.
• Write numbers clearly and keep units straight.
• Round sensibly to make calculations manageable, and say that you are doing so.
• State assumptions and check that they are reasonable.
• Sanity check results. Does the answer make sense?
• Show your steps. Even if you slip, your logic is visible.
• Interpret the numbers. What do they mean for the decision?

Practice with simple problems until you feel comfortable. You will not be expected to use advanced math.

Market sizing example

Question: "How many sandwiches are sold in a mid-sized city each day?"

A possible approach, with invented assumptions:

1. Define the market. Sandwiches bought from shops and cafes, not homemade.
2. Estimate the population. Suppose the city has 500,000 people.
3. Segment people. Working adults, students, children and others. Suppose 60 percent are adults likely to buy lunch out sometimes.
4. Estimate frequency. Suppose each such person buys a sandwich out once every four days.
5. Calculate. 500,000 times 0.6 gives 300,000 adults. Divided by four, that is about 75,000 sandwiches per day from this group.
6. Add other groups and adjust. Perhaps add students and visitors, and note uncertainty.
7. Sanity check. Does 75,000 per day seem plausible compared with the number of shops?

The point is the logic, not the final number. State assumptions, explain steps and invite correction.

Profitability example (outline)

Prompt: "A regional bakery chain's profits have fallen over the past year. What is happening, and what should it do?"

A possible structure:

• Revenue: number of customers, average spend, product mix, pricing.
• Costs: ingredients, labor, rent, equipment, waste.
• External factors: competitors, customer trends, input prices.
• Internal factors: product quality, service, marketing, operations.

You might start by asking whether the decline is due to revenue or costs, then ask for data. If revenue fell because of fewer customers, you would explore why. If costs rose, you would look at which items. You would then propose actions, such as changing pricing, reducing waste or improving marketing, and discuss risks and priorities.

Communication

Cases test how you talk, as well as what you think.

• Think aloud in a structured way.
• Be concise. Make a point, then stop.
• Signpost. "I'd like to look at three areas. First..."
• Pause to think. It is fine to take a moment.
• Summarize at natural points.
• Listen to hints. If the interviewer nudges you, use it.
• Be open to feedback. Adapt without defensiveness.
• Keep a professional, friendly tone.
• Write clearly if using paper or a whiteboard.
• Conclude clearly. "My recommendation is... because..."

Handling mistakes and uncertainty

• Stay calm. Mistakes are normal.
• Correct yourself openly. "I see that I mis-added that, let me fix it."
• Admit what you do not know. Ask for information or state a reasonable assumption.
• Do not freeze. If stuck, return to the objective and your structure.
• Do not argue with the interviewer.
• Recover quickly. Interviewers watch your response to setbacks.

How to practice

1. Learn the basics. Read about the case interview format. Many careers services and consulting clubs provide guides.
2. Practice mental math daily.
3. Do cases aloud with a partner. Alternate roles of interviewer and candidate. Use published cases or ones you create.
4. Time yourself.
5. Record or note feedback on structure, math and communication.
6. Practice a range of case types.
7. Read business news to build commercial awareness.
8. Join a student consulting or business club.
9. Ask your careers service for mock interviews.
10. Review and repeat. Improvement comes from repetition and feedback.

Avoid relying on memorized answers. Interviewers vary their cases.

Non-business and other versions

• Public policy and nonprofit cases use similar structures with different goals, such as outcomes, equity and cost-effectiveness.
• Technical cases for data or engineering roles may ask you to design an analysis or system.
• Marketing and product cases involve customers, value and testing.
• Group case exercises in assessment centers add teamwork.
• Written cases require an individual written analysis.

The same principles apply: clarify, structure, analyze, recommend.

For students without a business background

• You are not at a disadvantage if you practice. Cases test reasoning.
• Learn basic business terms: revenue, cost, profit, margin, market share, fixed and variable costs.
• Use everyday examples to practice, like estimating foot traffic for a cafe.
• Draw on your own field. Science and engineering students are used to structured problem solving.

Common mistakes

• Jumping into calculations without structure.
• Reciting frameworks mechanically.
• Silence while thinking.
• Ignoring the interviewer's hints.
• Not summarizing or recommending.
• Math errors without sanity checks.
• Getting rattled by mistakes.

A quick checklist

• Do I have a simple structure for any case?
• Can I do basic mental math quickly?
• Have I practiced cases aloud with a partner?
• Do I clarify, structure, analyze and recommend?
• Can I stay calm and adapt when I make mistakes?

Final thoughts

A case interview is an exercise in clear thinking out loud. Learn a flexible structure, practice numbers and communicate your reasoning. Treat the interviewer as a collaborator, adapt to new information and finish with a clear recommendation. With practice, the format becomes familiar and even enjoyable.