Product basics Part 3: Interview prep

Lesson 13 of 15

Guess- timates.

How to answer an estimation question step by step: clarify, choose a direction, write a formula, state assumptions, do the math in round numbers, check it a second way, and summarize.

By Nagesh Koritala, product manager October 2026

  • About 14 minutes
  • 7 parts
  • 6 quick questions
  • A worksheet
An estimate as a formula tree. Sofas bought in the US each year equals households (about 135 million, a Census fact) times the share with a sofa (assume 90 percent) divided by the years each sofa lasts before it is replaced (assume 10). The result is about 12 million. Sofas bought in theUS each year Householdsabout 135 million Census fact Share with a sofaassume 90% assumption Years a sofa lastsassume 10 assumption ×÷ 135 million × 0.9 ÷ 10 ≈ 12 million a year facts are cited; every guess is said out loud

Before you start

An interviewer leans back and asks: “How many sofas are bought in the US each year?” No phone, no internet, just a pen and a few minutes. It’s natural to freeze, or to reach straight for a number. Before you read on: what’s the very first thing you’d say? Write it in one sentence.

It stays on this device only. You’ll see it again at the end.

In this lesson, you’ll learn to

  • Explain what an estimation question tests, and why it isn’t a trick question
  • Clarify the question so you’re estimating the right thing
  • Choose between a top-down and a bottom-up approach
  • Break the number into a formula, and say every assumption out loud
  • Do the math in round numbers, then check it with a second approach
  • Summarize your answer as a number, a range, and the assumption that matters most

Key terms

Estimation question
An interview question that asks for a number you can’t look up, like a market size or a count. Also called a guesstimate, a market-sizing question, or a Fermi problem.
Fermi problem
An estimate built from rough, reasoned guesses about its parts. For a very large number, landing within about a factor of ten of the true value is usually good enough. Named after the physicist Enrico Fermi.
Top-down
Starting from a big number you know, like a country’s population, and narrowing it step by step to the thing you want.
Bottom-up
Starting from one small unit, like one store’s sales in a day, and multiplying it up.
Assumption
A value you choose and say out loud, with a short reason, because you can’t look it up.
Sanity check
A quick test of whether your answer is believable: a second approach, or a comparison with something you know.
Order of magnitude
Roughly how big a number is, in powers of ten: is it about 1 million, 10 million, or 100 million? A million and ten million are one order of magnitude apart.

The idea

“How many sofas are bought in the US each year?” Nobody expects you to know. That’s the point. The question tests whether you can take something that looks impossible, break it into pieces you can reason about, and get to an answer that’s roughly right, out loud and in a few minutes. It isn’t a trick question, either: there’s no clever answer to spot, only a path you can show.

Product managers do this for real, too. Before a team spends months on a feature, someone has to ask: how many customers could this help? This lesson teaches a seven-step method, with one example worked all the way through: sofas bought in the US, then sofas the made-up furniture store might sell in one city.

The lesson, in seven parts

  1. What an estimation question is, and why it’s asked.

    Estimation questions are older than product management. In physics teaching they’re called Fermi problems, after Enrico Fermi, who, in the words of MIT physicist Peter Dourmashkin’s textbook, “was famous for making these sorts of ‘back of the envelope’ calculations.” For a very large number, the same textbook says, an estimate within an order of magnitude “should be satisfactory.”

    A famous example is Fermi’s own. At the first atomic test, in July 1945, he dropped small pieces of paper as the blast wave passed and watched how far they moved. In his report he wrote that the shift was “about 2½ meters, which, at the time, I estimated to correspond to the blast that would be produced by ten thousand tons of T.N.T.” The official figure, set in 1963, is 21 thousand tons, and a 2021 Los Alamos reanalysis put it nearer 25 thousand. He was off by a factor of two to two and a half, from a handful of paper and some reasoning. That’s the skill.

    In an interview, the number matters less than the path to it. Interviewers usually want to see that you:

    • Pin down what’s being asked before you start.
    • Break a big unknown into parts you can reason about.
    • Say your assumptions out loud, with reasons, so anyone can challenge them.
    • Handle the math calmly, in round numbers.
    • Check your own answer, instead of waiting to be told.
  2. The method, in seven steps.

    Here’s a method you can use on any estimation question. Learn the order, then practice it until it’s automatic:

    • Clarify: what exactly are we counting, where, and over what time?
    • Pick a direction: top-down from a big known number, or bottom-up from one unit.
    • Write the formula in words, before any numbers. Check it with the interviewer.
    • State an assumption for each part, with a short reason.
    • Do the math in round numbers, out loud.
    • Sanity-check: a second approach, or a comparison with something you know.
    • Summarize: one number, a range, and the assumption that matters most.
    The seven-step method for an estimate. 1, clarify what exactly, where, and when. 2, pick a direction, top-down or bottom-up. 3, write the formula before any numbers. 4, state assumptions and why each is fair. 5, do the math in round numbers. 6, sanity-check a second way or against a known fact. 7, summarize the number, the range, and the key assumption. 1 Clarifywhat exactly, where, when 2 Pick a directiontop-down or bottom-up 3 Write the formulabefore any numbers 4 State assumptionsand why each is fair 5 Do the mathin round numbers 6 Sanity-checka second way, or a fact 7 Summarizenumber, range, key assumption
    The seven steps, in order. Writing the formula and checking the answer are the easiest to skip under pressure.

    Writing the formula is the step that’s easiest to skip under pressure, and it matters most. Saying “I’ll estimate households, times the share that own a sofa, divided by how many years a sofa lasts” lets the interviewer redirect you before you’ve spent five minutes on the wrong path.

  3. Clarify what you’re estimating.

    “How many sofas are bought in the US each year?” sounds clear until you try to answer it. Does a loveseat count? A hotel buying 200 sofas? A secondhand sofa? Each choice changes the number, so ask, or say what you’ll assume. Two or three questions are plenty.

    Ask

    • “Should I count new sofas only, or secondhand ones too?”
    • “Just households, or businesses like hotels and offices as well?”
    • “Is a loveseat a sofa for this?”
    • “Is this the number of sofas, or the number of people or households buying one?”

    Avoid

    • Ten questions in a row. It looks like stalling.
    • “Do you know the population of the US?” Bring your own starting number instead, even a rough one, and say where it comes from.
    • Asking nothing, then estimating something slightly different from what they meant.

    For the worked example, we’ll agree: new sofas only (loveseats count), bought by households, in one year, in the US. And we’ll count purchases, assuming one sofa per purchase. And to keep it simple, we’ll count one main sofa per household, and say so out loud.

  4. Choose top-down or bottom-up.

    There are two directions to come at almost any estimate. Top-down starts from a big number you know and narrows it. Bottom-up starts from one small unit and multiplies it out:

    Two directions for an estimate. Top-down starts from a big known number and narrows it: people, then households, then households with a sofa, then the ones buying this year. Bottom-up starts from one unit and multiplies it out: sofas one store sells a day, times days open, times stores, gives sofas a year. Top-downPeopleHouseholdsHave a sofaBuy this year Bottom-upSofas a yearStoresDays openSofas a day start big, narrow downstart small, multiply up use one to answer, the other to check
    Top-down narrows a big known number; bottom-up multiplies a small one. Use one to answer, the other to check.
    Top-downBottom-up
    Starts fromA big known number: population, householdsOne unit: one store, one customer, one day
    Sofa exampleHouseholds × share with a sofa ÷ years each sofa lastsSofas a store sells a day × days open × number of stores
    Good whenYou know the big number wellYou can picture the small unit clearly
    Watch out forToo few steps, so one wild guess swings everythingNot knowing how many units there are

    Neither is “correct”. A good habit is to answer with one and check with the other.

    For sofas, top-down is easier: you can know roughly how many US households there are, but you probably don’t know how many furniture stores there are. So we’ll answer top-down, and check with a second approach.

  5. Write the formula, then state your assumptions.

    Say the formula in words first: sofas bought per year = households × share of households with a sofa ÷ years a sofa lasts before it’s replaced. The logic: if most households have a sofa, and each one replaces it every so many years, then each year roughly one in that many households buys one.

    Now give each part a value, and say which ones are facts and which are your assumptions:

    PartValueFact or assumptionWhy it’s reasonable
    US householdsAbout 135 millionFact: 134.8 million in 2025 (US Census Bureau, Current Population Survey)A round number worth remembering for US questions
    Share with a sofa90%AssumptionMost homes have one; some single rooms and student homes don’t
    Years a sofa lasts10AssumptionMany people keep a sofa for years, and some replace it sooner when they move

    The household figure is a real Census number. The other two values are assumptions made up for this example, and you should say so out loud.

    The template

    I’ll estimate [what] as [part A] × [part B] ÷ [part C]. For [part A], I’ll use [value], because [reason]. For [part B], I’ll assume [value], because [reason]. For [part C], I’ll assume [value], because [reason]. That gives [rounded math], so about [answer].

    Filled in, for the made-up furniture store

    I’ll estimate sofas bought per year as households × the share with a sofa ÷ years a sofa lasts. For households, I’ll use about 135 million, from the Census. For the share, I’ll assume 90%, because most homes have one. For the life of a sofa, I’ll assume 10 years, because people keep one for years but replace it sooner when they move. That’s 135 × 0.9, about 120 million, divided by 10, so about 12 million sofas a year.

    Then the math, in round numbers: 135 million × 0.9 is about 120 million households with a sofa. Divided by 10 years, that’s about 12 million sofas a year. Say each step as you go, and keep the zeros straight by thinking in millions.

  6. Sanity-check it a second way.

    Before you say you’re done, check. Two quick checks work well.

    First, check your starting number against another fact. The Census Bureau estimated the US population at about 342 million on July 1, 2025, and its survey puts the average household at 2.5 people in 2025. 342 million ÷ 2.5 is about 137 million households, close to the 135 million we used. Good.

    Second, estimate the answer a different way: by the moments that make people buy a sofa. Moving home is a big one. The Census Bureau’s survey counted about 30 million movers out of about 322 million people aged one and over in 2019 to 2020, roughly 9%. Then:

    Who buysCalculationSofas a year
    Households that move135 million × 9% (assume households move at the same rate as people) × 1 in 4 buy a sofa (assumption: many movers bring the sofa they have)About 3 million
    Households that don’t move, replacing a worn sofaAbout 123 million × 1 in 15 each year (assumption: people who stay put tend to keep a sofa longer than 10 years)About 8 million
    TotalAbout 11 million

    The mover rate is a real Census figure for 2019 to 2020; the rest are assumptions for this example.

    Eleven million from one direction, twelve million from the other. They don’t prove the answer is right, since both rest on assumptions, but two different paths landing close together is a good sign. As a rough guide, within two or three times of each other is close. If they’d been ten times apart, you’d look for the assumption that’s off, and say so out loud.

  7. Summarize, and bring it down to one store.

    End with a clear, short summary: the number, a range, and the assumption that matters most. Something like: “About 12 million sofas a year, probably between 10 and 15 million. The biggest uncertainty is how often people replace a sofa: if it’s every 8 years instead of 10, the answer goes up by about a quarter.” To get the range, try a low and a high value for your shakiest assumption. A sofa that lasts 12 years gives about 10 million; one that lasts 8 gives about 15 million.

    A follow-up often brings it closer to the business. Say the interviewer asks how many sofas the made-up furniture store might sell in one city a year. Reuse your formula, and add one step:

    StepValueFact or assumption
    People in the city1 millionAssumption: a made-up city
    Households1 million ÷ 2.5 = 400,0002.5 people per household is the 2025 US Census average
    Sofas bought in the city each year400,000 × 0.9 ÷ 10 ≈ 36,000Same assumptions as before
    The store’s share5% ≈ 1,800 sofas a yearAssumption: made-up market share
    Per week1,800 ÷ 52 ≈ 35Arithmetic

    A made-up example. The store, the city, and its market share are invented for this lesson.

    About 35 sofas a week. That’s a number a product manager can use: it tells you how many deliveries a week to plan for, and how many shoppers a new doorway-size check could help.

With AI: AI can look up a population in seconds and run any calculation you like, so you might wonder why this skill still matters. It matters because the hard part was never the arithmetic. It’s choosing a sensible way to break the problem down, and knowing which assumption to question. AI tools can also produce confident numbers that are wrong. The habit this lesson teaches, checking a figure a second way and asking “does that seem right?”, is exactly how you catch them.

Check your understanding

Answer each one in your head or on paper first. Then open the answer to check.

1Why do interviewers ask estimation questions if they don’t know the exact answer either?

They’re testing how you reason: whether you clarify, break the problem into parts, state assumptions, and check your result. The process is what they’re judging.

2When would you choose bottom-up over top-down?

When you can picture the small unit clearly (one store, one customer, one day) but don’t know a reliable big number to start from.

3Why say the formula in words before doing any math?

So the interviewer can follow your logic and redirect you early if you’re estimating the wrong thing, before you’ve spent minutes on calculations.

4Your first approach gives 12 million and your second gives 120 million. What do you do?

Say so, and look for the assumption that’s most likely off by a factor of ten, such as the rate of replacement or a dropped zero. Fix it, or explain which estimate you trust more and why.

5What three things belong in your final summary?

The number, a range around it, and the assumption that matters most, with how the answer changes if that assumption changes.

6What did Fermi’s Trinity estimate show about this kind of reasoning?

That a careful estimate from simple observations and reasoning can land in the right range: he estimated ten thousand tons of TNT, and the real yield was about 21 to 25 thousand tons, within a factor of three.

Practice: plan the deliveries

You’re the product manager at the made-up furniture store. The delivery team asks: “How many sofa deliveries a day should we plan for in our city during the busiest month?” Use the numbers from the last part of the lesson (about 1,800 sofas a year) as your starting point. Write down your clarifying questions, your formula, your assumptions, the math, a sanity check, and a one-sentence summary. Then open the model answer.

  1. Ask two clarifying questions
  2. Write the formula in words
  3. State and justify each assumption
  4. Do the math in round numbers
  5. Sanity-check it
  6. Summarize in one sentence
Show a model answer

One possible answer. Clarify: “Deliveries of sofas only, or all furniture?” (sofas only) and “Do all sofas get delivered, or do some customers pick up?” (assume all are delivered, one sofa per delivery). Also assume deliveries run 6 days a week. Formula: sofas a year × the busiest month’s share of the year ÷ delivery days in that month. Assumptions: 1,800 sofas a year (from the lesson); the busiest month sells about one and a half times an average month (an assumption: average is 1/12 of the year, so about 1/8); about 26 delivery days a month. Math: 1,800 ÷ 8 ≈ 225 sofas in the busiest month; 225 ÷ 26 ≈ 9 a day. Sanity check: 35 a week on average is about 6 a day over 6 days; × 1.5 for the busy month is about 9, so it matches. Summary: “Plan for about 9 sofa deliveries a day in the busiest month, more on the busiest days, so plan a little slack. The biggest unknown is how much busier that month really is, so check last year’s order data if we have it.”

Back to where you started

The short answer

An estimation question asks for a number you can’t look up. Clarify what’s being counted, break it into a formula of smaller parts, state an assumption for each part, multiply in round numbers, and check the result a second way. The interviewer is judging your reasoning, not whether you hit the exact number.

Look back at the first thing you said you’d say. If it was a clarifying question, like “new sofas only, or secondhand too?”, you started exactly right. If it was a number, you’re in good company. Next time, lead with a question. Clarify, pick a direction, write the formula, state assumptions, do the math in round numbers, check it a second way, and summarize with a range.

Common mistakes

Most of these come from treating it as a test of the right number.

  • Starting to multiply before saying the formula, so nobody can follow you.
  • Hiding assumptions, or stating them without a reason.
  • Losing track of zeros. Think in millions, and write units next to every number.
  • Never checking. A quick second approach catches most big mistakes.
  • Freezing because you don’t know a number. Pick a reasonable value, say why, and move on.
  • Giving an over-precise answer like 12,150,000 instead of “about 12 million”.

Try this week

Estimation gets easier with repetition. Do one a day, out loud, in five minutes.

  1. Estimate how many mattresses are bought in the US each year, top-down.
  2. Estimate how many cups of coffee a café near you sells in a day, bottom-up.
  3. For each one, write the formula in words before any numbers.
  4. Check each answer a second way, and note which assumption mattered most.

Copy this worksheet: an estimate on one page

QUESTION:

1. CLARIFY
   What exactly are we counting?
   Where?            Over what time?
   What's in, what's out:

2. DIRECTION
   [ ] Top-down (start from a big known number)
   [ ] Bottom-up (start from one unit)

3. FORMULA, IN WORDS
   ______ = ______ x ______ / ______

4. ASSUMPTIONS
   Part | Value | Fact (source, year) or assumption | Why

5. MATH (round numbers, units on everything)

6. SANITY CHECK
   Second approach:
   Compare with something I know:
   Do they land close together (within about 2 or 3 times)? If they're 10 times apart, which assumption is off?

7. SUMMARY
   About ______ , probably between ______ and ______.
   The assumption that matters most: ______
   If it changes to ______, the answer becomes ______.

Questions people ask

What is a guesstimate question?

An interview question that asks you to estimate a number you can’t look up, like a market size or how many of something are sold. You answer by breaking it into parts, making reasoned assumptions, and checking the result.

How do you answer an estimation question in a product manager interview?

Clarify what’s being counted, choose top-down or bottom-up, say the formula in words, state each assumption with a reason, do the math in round numbers, check it a second way, and summarize with a number, a range, and the key assumption.

What is the difference between top-down and bottom-up estimation?

Top-down starts from a big known number, like population, and narrows it. Bottom-up starts from one small unit, like one store’s daily sales, and multiplies it up.

What is a Fermi problem?

An estimation problem solved with rough, reasoned guesses about its parts, for very large numbers, often aiming to land within about a factor of ten of the true value. It’s named after the physicist Enrico Fermi, who was known for these calculations.

Do I need to memorize population numbers for estimation questions?

It helps to know a few round numbers for the country you’re interviewing in, like its population and number of households. If you don’t know one, say so, pick a reasonable value, and explain why.

How accurate does my estimate need to be?

Not very. Interviewers care about clear reasoning and stated assumptions. A reasonable answer in the right order of magnitude, with a sanity check, is a strong answer.

Sources and further reading

All lessons

Keep going

Up next:
critique an app.

You can reason your way to a number now. Next, learn how to look at any app the way a product manager does, and say clearly what works, what doesn’t, and what you’d change.

Got a question this lesson didn’t answer? Email me. I read every note.

Seven steps of an app critique, in order: 1 purpose, what the app is for and how it earns; 2 user, one person and one job; 3 journey, one task walked twice; 4 principles, Nielsen’s 10 heuristics; 5 severity, rank each problem 0 to 4; 6 fixes, two or three with trade-offs; 7 measure, with goals, signals, and metrics. 1 Purposewhat it’s for, how it earns 2 Userone person, one job 3 Journeyone task, walked twice 4 PrinciplesNielsen’s 10 heuristics 5 Severityrank each problem 0 to 4 6 Fixestwo or three, with trade-offs 7 Measuregoal, signals, metrics judge it against what it’s for