Case Interview Prep for Non-Business Majors: A 2026 Plan

Non-business majors can prepare for case interviews by treating the gap as a skills map, not an identity problem. Consulting firms test structured problem solving, business judgment, quantitative analysis, clear communication, and synthesis. That is good news if you come from engineering, science, humanities, social science, health, law, policy, or another non-business field: your degree already trained useful muscles. The work is translating those muscles into client-ready case behavior. You need enough business basics to understand revenue, costs, margins, customers, competitors, and operations, plus live practice so your weakest point becomes visible under pressure. This guide gives you the concrete numbers (hours, cases, a timeline scaled to your background), the exact business concepts and math to learn, the mistakes to avoid, and a practice loop that does not waste your reps.

If you want the broader, major-agnostic roadmap, the case interview prep guide is the canonical hub; this article is the non-business-major lane that complements it.

Are non-business majors actually at a disadvantage?

No, and the firms say so directly. McKinsey's interviewing guidance frames its interviews around problem solving and personal experience, not finance coursework, and its careers material speaks to candidates across disciplines. Yale Office of Career Strategy describes consulting as a field that recruits from social sciences, humanities, and STEM, with generalist roles that expose new hires to many industries. The competitive reality is that top firms make offers to only about 1% of applicants, so the deciding factor is how well you perform in the room, not which department issued your diploma.

The mistake is assuming you must become a business student before you can case. You do not. Engineers bring decomposition. Scientists bring hypothesis testing. Humanities majors bring argument clarity. Social science and policy candidates bring stakeholder judgment and research discipline. Computer science and data candidates bring analytical rigor. STEM training maps cleanly onto structured, math-heavy cases, and humanities training maps onto the communication and synthesis that interviewers grade just as hard.

The real gap is translation. Interviewers need to hear your thinking in business terms: What is the client trying to decide? What drives profit? Which segment changed? What data would prove the cause? What recommendation follows from the evidence? Your background gives you raw material. Case prep turns it into interviewer-visible behavior. If you are an engineer specifically, the case interview for engineers guide goes deeper on that translation; PhD and postdoc candidates should read the case interview PhD guide.

What should you learn in the first 10 hours?

Do not try to learn every business concept before you practice. That is how smart candidates hide inside prep. Your first goal is to become functional in the few concepts that appear in almost every case.

How long does prep take, and how many cases?

Treat the numbers as planning anchors, not promises. Across published prep guidance, most successful MBB candidates spend 60-80 hours and complete 30-50 practice cases. Your background shifts the timeline more than your raw ability does.

Two caveats keep these numbers honest. First, the spread is wide: some people pass with 10 cases and others need 100. Second, candidates with prior consulting internships or strategy roles often need 30-40% less time than career changers from unrelated fields, which is exactly the situation most non-business majors are in. The fix is not more hours; it is targeted hours, which is why quality beats volume. Ten cases with real feedback move you further than thirty cases talking to yourself. For the full major-agnostic schedule, see the case interview prep guide; if you are switching fields entirely, the case interview prep for career changers guide covers the longer runway.

What are the business basics you actually need?

You need a compact foundation, not a mini-MBA. Start with revenue: price multiplied by volume, with mix explaining which products or customers drive the result. A coffee chain revenue problem might come from fewer transactions, a lower average ticket, weaker premium-drink mix, or a store-footprint issue. For deeper practice, the revenue decline case interview is the most useful follow-up.

Costs come in broad types. Some move with volume, like ingredients or delivery. Others are fixed over the relevant horizon, like rent or corporate overhead. Margin is the distance between revenue and cost. Breakeven logic asks how much volume, price, or contribution is needed to cover the cost base. The unit economics framework helps if margins, contribution, customer value, or breakeven still feel abstract.

Market size asks how big the opportunity could be. Customers explain who buys, why, and how behavior differs by segment. Competitors explain alternatives, pricing pressure, and differentiation. Operations explain whether the company can actually deliver the strategy. A retailer entering a new market must understand demand, local competition, supply chain, pricing, and store economics before recommending entry. BCG's case prep guidance emphasizes logic, calculations, communication, and intuition, which is why these basics should be practiced through cases rather than memorized as definitions.

Which case math formulas should you memorize?

Non-business majors usually have the arithmetic; what they lack is the standard set of business equations interviewers expect you to reach for instantly. These nine cover the large majority of case math:

1. Profit = Revenue - Cost
2. Profit margin = (Profit / Revenue) x 100
3. Market share = (Company revenue / Industry revenue) x 100
4. Growth rate = (New - Old) / Old
5. ROI = Profit / Cost of investment
6. Breakeven units = Fixed costs / (Price - Variable cost per unit)
7. Payback period = Investment cost / Annual profit
8. Capacity = Total capacity / Capacity per unit
9. Utilization rate = Actual output / Maximum output

The order of operations matters more than the formula. Write the equation first, do the arithmetic second, then state the business meaning third. Interviewers do not let you use a calculator, so practice clean mental setup rather than chasing speed tricks. If your calculations slow you down or you freeze when an exhibit appears, drill them directly with the case math drill and the chart and exhibit drill.

How do you turn an academic mindset into a case structure?

Use a simple profitability prompt:

A company operates EV charging hubs near highways. Profit is below expectations. What would you look at?

A weak academic answer might sound like this:

EV charging demand depends on climate policy, grid capacity, consumer adoption, battery technology, and infrastructure incentives.

That is thoughtful, but it is not a case structure. It describes the topic. It does not organize the client decision. A stronger consulting answer starts with the objective:

I would first confirm whether the client wants to restore profit to a target level or understand the root cause of underperformance. Then I would split the problem into revenue, cost, utilization, and operational reliability.

A clean first structure could be:

That structure translates a systems-thinking mindset into a business map. The candidate still uses decomposition, but the branches now answer a client question. Before building any issue tree, ask: What is the objective? What changed? Which segment is affected? What data would prove the cause? What decision must the client make? That last question is the anchor. A case structure is not a beautiful taxonomy; it is a decision tool. If you come from a technical or research field, the first principles thinking framework helps you break unfamiliar business problems into cleaner drivers, and the case structure vs case framework explainer clarifies why custom structures beat memorized templates.

What are the four case types you should know cold?

You do not need a framework library. You need to recognize the four patterns that cover most cases and know the logic each one demands:

• Profitability: revenue and cost decomposition to find why profit moved. Start here, because most cases bend toward it.
• Market sizing: estimate demand or revenue from population, segments, frequency, and price, with explicit assumptions and a sanity check.
• Market entry: market attractiveness, competition, the client's capabilities, and economics or risk, matched to the specific client context.
• Cost reduction: separate fixed from variable costs, find the largest addressable buckets, and weigh feasibility against savings.

Recognition is the skill. When you hear the prompt, name the underlying type to yourself, then build a custom structure for that specific client rather than reciting a generic tree. The case interview frameworks complete guide maps these types in detail without encouraging rote memorization.

What clarifying questions sharpen your structure?

Good clarifying questions do not make you look insecure; they make your structure sharper. BCG's interview process describes evaluation signals around problem solving, analytical ability, communication, motivation, curiosity, collaboration, and drive. The right question shows you understand the client needs a decision, not a speech. Use question groups before you structure:

• Objective: What does success mean? Profit, growth, market entry, cost reduction, or a strategic choice?
• Economics: How does the company make money? What are the main revenue streams, cost drivers, and margin pressures?
• Customer: Which segment matters most? Has behavior changed? Do needs or willingness to pay differ by segment?
• Competition: Who are the alternatives? Is the market fragmented, concentrated, commoditized, or differentiated?
• Operations: What constraints could block the answer? Capacity, supply, talent, regulation, technology, or service quality?
• Risks: What could make the recommendation fail? What assumption needs validation before the client acts?

For non-business majors, the goal is not to ask more questions. It is to ask the few questions that improve the first structure.

What mistakes make non-business candidates look unready?

The most common mistake is sounding smart but being hard to follow. A candidate can know a lot about economics, medicine, public policy, or data science and still lose the interviewer because the answer has no clear branches. A slightly less polished candidate who gives a clean structure, explains calculations calmly, and synthesizes the answer is easier to evaluate, and easier to hire.

Avoid over-explaining academic theory; the interviewer does not need a lecture on the industry before you identify the client problem. Avoid hiding from math; if the equation is simple, write it clearly and talk through the setup. Avoid business jargon you cannot define, because misused jargon signals insecurity faster than plain language. Avoid memorized frameworks, since the useful structure depends on the prompt. And avoid silence while thinking; BCG's preparation guidance encourages candidates to communicate, stay structured, and avoid panic when the problem changes. If you do not know a business term, recover simply: "Here is what I understand from the context. Could I clarify whether this refers to the revenue side or the cost side?" Then continue with the logic.

Finally, your recommendation needs a so-what. Do not end with a list of facts. End with the decision, the evidence, the risk, and the next step. The synthesis drill exists for exactly that weak closing pattern, and the case interview mistakes to avoid guide catalogs the rest.

What is the right practice plan for a non-business major?

Reading helps, but case interviewing is a practiced skill. UC Berkeley Career Engagement stresses mock interviews, feedback, and self-practice, and Penn Career Services points students toward case guides and practice cases. The same point holds: you need applied reps with feedback, not passive study.

Start with a full case to diagnose readiness, then route your weakest skill into a focused drill. If your opening structure is vague, use the case structure drill. If assumptions feel random, use the market sizing drill. If calculations slow you down, use the case math drill. If exhibits produce observations but no implication, use the chart and exhibit drill. If your case ends in a recap instead of a recommendation, use the synthesis drill. Across thousands of diagnostic cases run on Road to Offer, non-business majors most often surface synthesis and case-math gaps first, not structure, which is why a diagnostic beats guessing where to start.

You also need a feedback network. Non-business majors often have to recreate what business-school peers get from consulting clubs: alumni calls, practice partners, and quick feedback loops. The case interview practice partner guide helps you find and run those sessions, and if you are recruiting from undergrad without a business program nearby, the undergrad consulting recruiting guide maps the timeline and outreach.

If you want to test which gap is real before committing weeks to a plan, run a free diagnostic case with AI feedback and let the result pick your next drill. The sequence is simple: case, feedback, drill, repeat. Diagnose the skill, drill the gap, then return to a live case before you convince yourself the problem is solved.

Sources

• McKinsey & Company, Interviewing at McKinsey (checked June 17, 2026)
• Boston Consulting Group, Case Interview Preparation (checked June 17, 2026)
• Boston Consulting Group, Interview Process (checked June 17, 2026)
• Yale Office of Career Strategy, Consulting (checked June 17, 2026)
• My Consulting Offer, Case Study Interview Prep (checked June 17, 2026)
• Hacking the Case Interview, Time to Prepare for Case Interviews (checked June 17, 2026)
• Wall Street Oasis, How does a non-business major prepare for case interviews? (checked June 17, 2026)
• UC Berkeley Career Engagement, Interview Preparation (checked June 17, 2026)
• University of Pennsylvania Career Services, Case Interview Guide (checked June 17, 2026)