Quoting a Range Instead of a Single Number
Why interviewers reward a confident range with reasoning attached over a single guessed number, and how to build a range that actually reflects your uncertainty rather than padding it for safety.
Prerequisites: Breaking an Estimate Into a Decomposition Tree
Say an interviewer asks how many gas stations there are in your city, and after a decomposition tree you land on 214. If you say "214," you've just handed them a single number that is almost certainly wrong — not because your reasoning was bad, but because a Fermi estimate is built from several rounded inputs multiplied together, and each rounding compounds. The interviewer isn't testing whether you can recite 214. They're testing whether you know how wrong 214 might be, and whether you can say so out loud without flinching.
The problem with a bare point estimate
A point estimate hides its own uncertainty. If you say "214" and the true number is 340, you look like you got it wrong — even though your method might have been sound and the miss came entirely from one shaky assumption three steps back (average stations per neighborhood, say). A range communicates the opposite: "somewhere between 150 and 400, most likely around 200–250" tells the interviewer you understand where your estimate is shaky, not just what your best guess is. That's the actual skill being tested — the same skill a trader uses when quoting a market rather than declaring a single fair value.
Building the range, not just picking one
The range should come from the same decomposition you used to get the point estimate, not be bolted on afterward as a vague "give or take." Walk back through your chain of multiplications and ask which input you're least sure about — that's usually where the range should be widest. If your estimate was
where is population, is the fraction of the population that drives, and is customers served per station per day, you're probably confident in to within 10%, less confident in , and least confident in — station capacity assumptions are usually the roughest guess in the chain. Widen your final range mostly on the back of that weakest link, not evenly across all three.
Worked example: gas stations in a city of 2 million
Suppose your chain was: population 2,000,000; 60% of adults drive regularly, so roughly 1,000,000 drivers; each driver fills up roughly once a week, so about 143,000 fill-ups a day; a station can handle roughly 500 fill-ups a day. That gives
Now stress-test the shakiest input: "fill-ups per station per day" could reasonably be anywhere from 300 (a small, slow station) to 800 (a busy highway station), not just 500. Swapping in those bounds gives and . So instead of reporting "286," you report: "my point estimate is around 280–290, but because I'm least sure about throughput per station, I'd put the real range at roughly 180 to 480, with 280 as my best single guess." That's a far more defensible answer, and it shows the interviewer exactly which assumption you'd go check first if you had real data.
A range built from identifying your weakest input and propagating its uncertainty through the same formula you used for the point estimate is more informative — and more honest — than a single number dressed up as precise. State both: a best-guess point and a range, with the range explained by which assumption drives it.
A fast way to build a defensible range without redoing the whole calculation: multiply and divide your point estimate by a factor of roughly 1.5–2 for a "medium confidence" range, and say explicitly which single input you'd tighten first with real data. Don't manufacture false precision by giving a range like "281 to 291" — that implies confidence you don't have.
The common mistake is padding the range defensively — saying "somewhere between 10 and 10,000" to avoid ever being wrong. That's not a range, it's a refusal to estimate, and interviewers see through it instantly. A good range is narrow enough to be useful and wide enough to be honest, anchored to a specific input you can name as the source of the uncertainty.
Related concepts
Practice in interviews
Further reading
- Guesstimation, Weinstein & Adam, ch. 1