82% of my students land consulting offers
Stop piecing together random resources. Get everything in one place: a step-by-step case interview course from a former Bain interviewer.
Author: Taylor Warfield, Former Bain Manager and Interviewer

You walk into your McKinsey interview and the consultant across from you asks: "How many golf balls would fit in a school bus?"
Your first thought might be panic. But here's the thing: they don't actually care about golf balls. Consulting guesstimate questions test how you think, not what you know.
I’m a former Bain Manager and interviewer. This guide will walk you through everything you need to ace consulting guesstimate questions.
But first, a quick heads up:
Learning case interviews on your own can take months.
If you’re looking for a step-by-step shortcut to learn case interviews quickly, enroll in my case interview course and save yourself 100+ hours. 82% of my students land consulting offers (8x the industry average).
Consulting guesstimate questions ask you to estimate something you probably don't know off the top of your head.
These aren't trick questions. Consulting firms use them because consultants spend half their time making educated guesses with incomplete information.
Think about it.
When McKinsey advises a client on entering a new market, they don't have perfect data. They need to estimate market size, potential revenue, and customer segments based on logic and reasonable assumptions.
That's exactly what guesstimate questions test.
There are two main types you'll see:
Market sizing questions ask you to estimate the value or volume of a market.
Estimation questions can be about anything quantifiable.
Both types follow the same approach. Break down the problem, make logical assumptions, do simple math, and check if your answer makes sense.
Interviewers don't care if your answer is 100 million or 120 million. They care about three things:
First, can you structure a messy problem?
Consulting is about taking complex situations and breaking them into manageable pieces. If you can't organize a simple estimation, you won't handle a three-month client project.
Second, do you make reasonable assumptions?
You'll never have all the data you need in consulting. Interviewers want to see if you can make assumptions that are logical, defendable, and grounded in reality.
Third, can you communicate clearly?
The best analysis means nothing if you can't walk someone through your thinking. Interviewers watch how you explain your logic, not just what numbers you reach.
Here's what they're not testing:
Most guesstimate questions don't even have a right answer. If you justify your logic well, being off by 20 percent doesn't matter.
Stop trying to memorize different approaches for different questions. Every consulting guesstimate follows the same five steps.
Never jump straight into math. Take 30 seconds to make sure you understand what you're estimating.
If the interviewer asks about "smartphone market size in India," you may want to ask:
Ask these questions out loud. It shows you think before acting and it prevents you from solving the wrong problem.
This is where most people mess up. They try to go from the question straight to a number.
Take a minute to map out your approach. Draw a simple tree or framework that shows how you'll get to the answer.
For market sizing, you usually pick between two approaches:
Top-down:
Start with a big number and narrow it down.
To estimate coffee shop revenue in New York, start with NYC's population, estimate how many drink coffee, calculate spending per person, and multiply.
Bottom-up:
Start with a small unit and build up.
For the same question, estimate one coffee shop's daily revenue, figure out how many coffee shops exist in NYC, and multiply.
Pick whichever feels more natural for the question. Both work.
The key is showing your structure before calculating anything. Tell the interviewer: "I'm going to estimate the total population first, then narrow to coffee drinkers, then calculate per-person spending."
Now you'll fill in the numbers for each piece of your structure.
This is where your judgment matters. Don't make assumptions you can't defend. Base them on common sense, personal experience, or facts you know to be true.
If you're estimating US population and you know it's around 330 million, say so.
If you're guessing what percent of people drink coffee daily, explain your logic: "From my own experience and what I see around me, I'd estimate about 50 percent of adults drink coffee regularly."
Always explain your reasoning. "I'm assuming X because Y" is much better than just stating numbers.
Round aggressively to make math easy. Use 330 million instead of 331 million. Use 50 percent instead of 48 percent. The goal is clean calculations, not precision.
Walk through your calculations out loud. Don't go silent and scribble on paper.
Keep it simple.
If you're multiplying 330 million by 50 percent, break it down: "Half of 330 million is 165 million."
Use your structure from Step 2. Work through each piece methodically. If you laid out three factors to estimate, calculate each one in order.
If you make a mistake, acknowledge it and fix it. "Actually, let me recalculate that" shows way more maturity than pretending you got it right.
Write everything down clearly. The interviewer might ask you to revisit a calculation or test a different assumption later.
Before you present your final number, pause and ask yourself: does this make sense?
If you estimated that Americans drink 10 billion cups of coffee per day, think about what that means. That's about 30 cups per person per day.
Clearly wrong.
Compare your answer to something you know. If your estimate says there are 500,000 gas stations in the US and you know the population is 330 million, that's one station per 660 people.
Does that feel right? Actually, yes.
If your number seems off, don't start over. Identify which assumption is probably wrong and adjust just that piece.
Then present your final answer confidently. "Based on these assumptions, I estimate approximately 50 million smartphones are sold in India annually."
Let's walk through real questions so you can see exactly how to apply the framework.
Clarify: I'll estimate the number of gas stations currently operating in the US that serve the general public.
Break it down: I'll use a demand-based approach. Total gas stations equals total cars divided by how many cars each station can serve.
Assumptions:
Calculate: 90 million cars refueling weekly divided by 4,500 cars per station equals 20,000 gas stations.
Clarify: I'll estimate the annual revenue of all coffee sold in the US, including coffee shops, home consumption, and workplace coffee.
Break it down: I'll use a top-down approach based on population and per-person spending.
Assumptions:
Calculate: $900 million per day × 365 days = $328.5 billion annually
Clarify: I'm estimating pizzas sold to consumers in NYC, including restaurant dining, takeout, and delivery.
Break it down: I'll use frequency-based logic. Total pizzas equals population times the percentage who eat pizza times frequency.
Assumptions:
Calculate: NYC sells approximately 200,000 pizzas daily.
Clarify: I'm estimating total hotel rooms across all categories in India, from budget to luxury.
Break it down: I'll segment by city tiers and estimate hotels per tier.
Assumptions:
Calculate: Total hotel rooms in India: approximately 700,000.
Once you master the basics, these techniques help you stand out.
Don't just solve the problem one way. If you have time, approach it from two angles and see if you get similar answers.
For "coffee shop revenue in NYC," you could estimate from total coffee drinkers (top-down) or from number of coffee shops times revenue per shop (bottom-up). If both approaches land near the same number, your estimate is probably solid.
Don't treat everyone the same. If you're estimating car sales, segment by income level. High-income buyers replace cars more frequently. Low-income buyers buy used.
Better segmentation leads to better estimates and shows sophisticated thinking.
After you reach an answer, identify your most uncertain assumption. Then say: "If I'm wrong about X, here's how it would change the answer."
"I estimated 50 percent of adults drink coffee. If it's actually 40 percent, my market size drops to $260 billion instead of $328 billion."
This shows you understand which assumptions matter most.
If you know any related facts, use them to validate your answer.
"I estimated 150,000 gas stations. I know California has about 10,000, and California is roughly 10 percent of the US population, so that tracks."
There are a lot of misconceptions about what consulting interviewers actually look for in asking guesstimate questions.
Here's what will get you points:
Show your approach first. Don't dive into numbers immediately.
Explain where your estimates come from. "Based on my experience" or "Given that X, I'd assume Y" works great.
Round numbers. Don't waste time on exact calculations. 3.14 becomes 3. 47 percent becomes 50 percent.
Talk through everything. The interviewer should understand your logic without reading your notes.
If you realize you made a mistake, fix it. "Actually, I need to adjust that assumption" shows good judgment.
Now, here's what doesn't matter:
Work through these on your own using the five-step framework:
Start with the easier ones and work your way up. Practice until the framework becomes automatic.
Here are the six best ways to prepare for consulting guesstimate questions.
The single best way to improve is to practice out loud. Don't just think through questions in your head. Actually speak your answers as if an interviewer is sitting across from you.
You don't need to memorize hundreds of statistics, but know approximate populations for major countries, rough household sizes, and basic economic indicators.
Real guesstimate questions usually take 8-12 minutes. Practice with a timer so you know what appropriate pacing feels like.
If you know nothing about the coffee industry, research it for 20 minutes. Understanding basic market structures helps you make better assumptions.
Have a friend ask you questions and give feedback. Or better yet, work with someone who's been through consulting interviews before.
After solving a guesstimate, write down what worked and what didn't. Over time, you'll notice patterns in how you think and where you get stuck.
Consulting guesstimate questions feel intimidating at first. Most people walk into their first one thinking "I have no idea."
But here's the truth: interviewers know you have no idea. That's the point.
They want to see how you handle not knowing. Do you panic and guess randomly? Or do you break down the problem logically and work through it piece by piece?
Now stop reading and start practicing. Pick a random object near you and estimate how many exist in your country. Then walk through the five steps out loud.
That's how you get good at this.
Ready to stop struggling and start landing consulting offers?
Enroll in my step-by-step case interview course:
Join 3,000+ candidates who've landed offers at McKinsey, BCG, Bain, and other top firms. 82% of my students land consulting offers.
👉 Enroll Now