Market sizing questions show up in almost every PM interview loop. You might face a classic like "How many vending machines are in Manhattan?" or a product-flavored variant like "Estimate the revenue opportunity for a new feature." Either way, the goal stays the same: show the interviewer how you think under pressure.
Most candidates freeze. They reach for a guess. They blurt a number. They lose the room.
The strong candidates do something different. They build a model out loud, label every assumption, and walk the interviewer through each step. The number matters less than the reasoning behind the number.
What interviewers actually want to see
A market sizing question is not a math test. It is a structured-thinking test. The interviewer wants to watch you break a fuzzy problem into smaller parts that each have a defensible answer.
Marty Cagan, the founder of the Silicon Valley Product Group, makes this point often. He argues that the strongest product managers come from teams where discovery and delivery are tightly linked, and where the PM can articulate a problem with clarity before suggesting a solution (Cagan).
That same skill is what an interviewer probes during a sizing question. Can you frame a vague prompt? Can you name the inputs that drive the answer? Can you make trade-offs out loud and pick a path? Can you sanity-check yourself at the end?
Lenny Rachitsky, who writes the most-read PM newsletter on Substack, has surveyed hundreds of hiring managers about what they actually weight in interviews. His finding is simple: structured thinking and clear communication beat raw quantitative skill almost every time (Rachitsky).
That is the bar. Numbers help the answer. Structure wins the room.
The five-step sizing playbook
Use this same five-step pattern on every market sizing question.
Step 1: Restate the question. Say it back to the interviewer in your own words. Confirm the unit, the geography, and the time window. If they ask for "the market for electric scooters," ask whether they mean revenue, units sold, or active riders. Ask whether they mean the United States or the world. Ask whether they mean today or in five years. The wrong unit at the start ruins the rest of the answer.
Step 2: Pick top-down or bottom-up. Top-down starts with a big number, like total population, and slices it down with filters. Bottom-up starts with one customer and multiplies up. For consumer markets, bottom-up usually feels more grounded. For B2B markets, top-down is often faster.
Step 3: Build the equation. Write a single line that lists every variable you need. For example: market size equals population times adoption rate times average price times purchases per year. The variables are now clear, named, and easy to attack one at a time.
Step 4: Estimate each variable. Anchor each number to something you actually know. The US population is about 335 million. The number of US households is about 130 million. Smartphone penetration is roughly 90 percent. State each anchor out loud. Round generously. Precision is a trap.
Step 5: Multiply, then sanity-check. Run the math. Then ask yourself if the final number passes a smell test. Compare it to a known reference, like the size of the US car market or the global music industry. If your number is off by an order of magnitude, walk back and find the bad assumption.
Common traps to avoid
Two traps account for most failed sizing answers.
The first trap is anchoring on a vague number too early. Candidates often blurt "let's say 20 percent" without saying what 20 percent means. The interviewer then loses track. Always name the variable before you name the value.
The second trap is skipping the sanity check. A candidate runs the math, lands on $14 trillion for the US dog food market, and says "great, done." A quick reference check would show that the entire US grocery market is around $800 billion. The number is wrong by a factor of seventeen. The skill the interviewer wants to see is the muscle to catch that error in real time.
Teresa Torres, who teaches continuous discovery to product teams, frames this kind of self-correction as the core of good PM work. She writes that strong product managers treat assumptions as risks to test, not as facts to defend (Torres). The same mindset belongs in a sizing answer. Every variable is a guess. Every guess deserves a quick check.
A worked example
Question: estimate the annual US revenue for paid meditation apps.
Restate: revenue, US, paid subscriptions only, last twelve months.
Pick approach: bottom-up, one user at a time.
Equation: revenue equals total US adults times smartphone penetration times share who try a meditation app times share who pay times average annual spend.
Estimate: 260 million adults times 0.9 smartphone share times 0.10 who try meditation apps times 0.15 who actually pay times $70 average annual spend.
Math: 260M times 0.9 equals 234M. Times 0.10 equals 23.4M. Times 0.15 equals 3.5M paying users. Times $70 equals about $245 million in annual revenue.
Sanity check: Calm and Headspace are the two largest players, and public reporting puts their combined US revenue near $400 million. The estimate is in the right zip code, slightly low, which suggests the "share who pay" number could be a bit higher. State that out loud.
The interviewer now sees three things. You broke the problem into parts. You picked anchors with reasoning. You caught your own gap.
How to practice
Jeff Gothelf, the author of Lean UX, recommends one habit for any PM who wants to sharpen their thinking: write the assumption down, then test it with the smallest possible experiment (Gothelf). For market sizing, the experiment is a quick reference search. Spend five minutes a day on Wikipedia or a public earnings report. Look up the size of one market. Compare it to a number you would have guessed. Over a month you will build a mental library of anchors that make every future sizing question faster.
The candidate who walks into the interview with that library in their head is the candidate who gets the offer.
Works cited
Cagan, Marty. Inspired: How to Create Tech Products Customers Love. 2nd ed., Wiley, 2017.
Gothelf, Jeff, and Josh Seiden. Lean UX: Designing Great Products with Agile Teams. 3rd ed., O'Reilly Media, 2021.
Rachitsky, Lenny. "What Hiring Managers Actually Look For in PM Interviews." Lenny's Newsletter, 2024, www.lennysnewsletter.com.
Torres, Teresa. Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value. Product Talk LLC, 2021.