How to answer market sizing questions in PM interviews
When faced with a market sizing question, break the problem into logical steps, state your assumptions, and sanity check your math. Prioritize clarity over precision. Explain your reasoning, choose a structure that fits the product, and always validate your answer with a practical sense-check.
PMMockr.com
Start by clarifying the scenario
A common mistake is answering a market sizing question—like 'How many electric bikes are sold in New York City each year?'—without clarifying scope. Rushing in can waste time estimating the wrong market. Instead, define the target: does the interviewer mean all bikes, just new sales, or a specific customer segment? State your understanding and ask for adjustment if needed. This ensures your calculation reflects the real business challenge.
Choose a logical breakdown, not a template
Candidates often default to stock structures ('top-down' or 'bottom-up') regardless of fit. For electric bikes, you could start with NYC’s population, but if the market is driven by specific user types—like commuters or delivery workers—it’s better to segment by use case. Pick a breakdown that matches how real-world demand arises, explaining your rationale. This makes your answer credible and easier to follow.
State assumptions explicitly and estimate with round numbers
Interviewers expect you to make up reasonable numbers, but you must say which are assumptions. For NYC, assume a population of 8 million for easy math. If you estimate that 10% of adults are potential buyers, say so. Use round numbers to keep calculations simple, and mention that you’ve rounded for efficiency. This signals comfort with ambiguity and keeps the discussion moving.
Work through a detailed example: electric bikes in NYC
Suppose the question is: 'Estimate the number of electric bikes sold in New York City each year.'
First, clarify: focus on new electric bike sales to individuals, excluding rentals and businesses. Assume NYC’s population is 8 million, with 70% adults (5.6 million). Assume 20% of adults are potential buyers—those interested in biking, living near safe routes, or needing last-mile transport—giving 1.1 million potential buyers (5.6 million × 20%).
Next, estimate purchase frequency. Assume an average electric bike lasts 5 years; so, each year, 20% of these buyers (1.1 million × 20% = 220,000) would be in the market. But not all will actually buy: assume 10% conversion (220,000 × 10% = 22,000 sales per year).
Sanity check: Does 22,000 new electric bikes annually for a city the size of NYC seem reasonable? If it feels high, consider competing transport options and price sensitivity. You might adjust the buyer pool or conversion rate after discussion.
If new evidence—say, a city report shows only 5,000 new e-bike registrations per year—emerges, revisit assumptions: perhaps the target market is smaller, or replacement cycles are longer. Articulate what would prompt you to revise your estimate, and show you’re open to correction.
Segment users before prioritizing variables
It’s tempting to estimate sales based on population alone, but this rarely reflects real demand. Instead, segment users: are they commuters, students, delivery workers, or recreational riders? Understanding who buys helps you choose which variables matter most—like commute length, disposable income, or storage space. Prioritize variables that drive differences in behavior rather than those easy to measure. This leads to more realistic and insightful estimates.
Prioritize clarity and communicate trade-offs
Some candidates try to impress with complex math or excessive precision, but this can confuse the interviewer. Explain why you chose a given assumption over another. For example, you might estimate a higher conversion rate for delivery workers than for recreational users, but choose a weighted average for simplicity. Be transparent about these trade-offs, and state the impact on your estimate. Clarity is more valuable than hitting a precise number.
Sanity check and adjust your estimate
Before sharing your answer, pause to ask: does this number make sense given the scenario? Compare your estimate to familiar benchmarks—such as the number of yellow cabs, subway rides, or bike racks in NYC. If your answer seems off by an order of magnitude, revisit your assumptions. This step distinguishes thoughtful candidates from those who simply calculate without context.
Compare with a competing approach
Suppose instead you tried a top-down estimate: start with the number of bikes sold per year in the US, then estimate NYC’s share. If the US sells 1 million electric bikes annually (assumption), and NYC is 3% of the population, that’s 30,000 bikes. If your earlier bottom-up estimate was 22,000, discuss the gap. Differences could arise from urban density, higher adoption rates, or limited storage. Explaining both approaches shows you understand the market’s complexity and can triangulate.
Example of weak reasoning and how to improve it
A weak response might assume 1% of NYC’s population buys an electric bike each year, without justification. This ignores product lifespan, actual user demand, and competing options. A stronger answer builds up from plausible user segments and purchase frequencies, explaining each step. The difference is transparency: the better answer shows how the number was reached, making it easier to critique and refine.
Timed practice exercise
Set a timer for seven minutes. Estimate the number of monthly gym memberships sold in San Francisco. State your scope, segment users, make explicit assumptions, and sanity check your answer. When finished, review your steps using the checklist below. Practice one new market sizing problem every other day for two weeks, using different products and cities.
Self-review checklist
Check your answer against these criteria:
- Did I clarify the question and scope? - Are my assumptions explicit and reasonable? - Did I segment users relevantly? - Did I choose a breakdown that fits the product? - Are my calculations clear and justified? - Did I sanity check the final answer? - Did I discuss what would change my estimate? - Did I avoid unnecessary complexity?
FAQ
What if my estimate is way off from the real number?
Explain your assumptions and show how your answer would change with new data. The interviewer cares more about your reasoning than the exact number. If you realize a major error, state how you'd correct it.
Should I use a top-down or bottom-up approach?
Choose the breakdown that best fits the product and question. For niche or new products, bottom-up is often clearer. For broad markets, top-down can provide a useful check. Explain why you chose your method.
How much detail should I go into with my math?
Prioritize clarity and logic over precision. Use round numbers for ease, explain each step, and avoid getting bogged down in decimals. Focus on the reasoning behind the math, not just the calculation.