Estimation

Estimation questions are a staple of product management interviews at companies like Google, Amazon, and Facebook. They test your ability to think analytically, handle ambiguity, and solve problems on your feet. The actual number you arrive at is less important than your process and communication.

The trap most candidates fall into is jumping straight to a calculation without first clarifying the problem or structuring their approach. Your actual job is to slow down, ask smart questions, and reduce complexity by breaking the problem into manageable pieces.

Why estimation questions matter in PM interviews

Satyaki Benerji, Assistant VP of Product Management at IDFC FIRST Bank, explains:

"The first part of why guestimates matter is to understand how you approach problem solving. Are you analytical? Can you break down unknown questions into parts? Do you enjoy uncertainty or get frustrated? Finally, where do you focus your attention? Many candidates rush to answer without spending time in the problem space — defining the problem, understanding constraints, and clarifying scope. This is a missed opportunity."

Estimations show interviewers how you think, not how much you know. They reveal your ability to:

• Structure ambiguous problems,
• Make reasonable assumptions,
• Perform quick mental math,
• Communicate your rationale clearly.

If you cannot demonstrate these skills, you are unlikely to succeed as a PM.

The clarifying questions that unlock estimation problems

Before you start calculating, ask clarifying questions to define the problem precisely. Fernando Delgado, an experienced PM interviewer, says:

"You start with a general formula for the problem. For example, if asked, 'How much revenue does YouTube generate each day?' you might start with: Revenue = Number of views × Click-through rate × Cost per click. Then you break down each part and justify your assumptions."

Good clarifying questions include:

• What exactly am I estimating? (e.g., total revenue, active users, number of transactions)
• What is the scope? (global, India only, a specific city)
• Are we considering all revenue streams or just advertising?
• Should I include manual and automated actions?
• What timeframe? (per day, per month, per year)

Asking these questions narrows the problem and shows the interviewer you are thoughtful.

The 10-step structured approach to answering estimation questions

Satyaki shares a practical 10-step method he uses:

1. Clarify the question — Confirm what you are estimating and the scope.
2. Define the problem space — Understand the context and constraints.
3. Break down the problem — Decompose into smaller, measurable parts.
4. Make assumptions explicit — State your hypotheses clearly.
5. Estimate each component — Use known numbers or logical guesses.
6. Calculate intermediate results — Multiply or combine estimates stepwise.
7. Check for plausibility — Do sanity checks on your numbers.
8. Iterate if needed — Refine assumptions or calculations.
9. Summarize the process — Walk the interviewer through your steps.
10. State limitations and edge cases — What you did not consider and why.

This disciplined approach turns a daunting question into a manageable exercise.

Breaking down a real example: Estimating Google searches per day

Let's apply this method to a classic example: "Estimate the number of Google searches happening every day."

Step 1: Clarify the question

• Are we counting global searches or India only?
• Are we including automated API queries or just manual searches?
• Do we want total searches or unique users?

Step 2: Define problem space

• Assume global manual searches only for simplicity.
• Timeframe is per day.

Step 3: Break down the problem

Estimate:

• The number of internet users worldwide,
• The average number of searches per user per day.

Step 4: Make assumptions explicit

• Global internet users: ~5 billion.
• Average searches per user per day: 3.

Step 5: Estimate components

• Total searches = 5 billion × 3 = 15 billion searches per day.

Step 6: Check plausibility

• Does 15 billion seem reasonable? Given Google's dominance, yes.

Step 7: Summarize

"I estimated 5 billion internet users globally, assuming each does 3 searches per day, yielding 15 billion daily searches."

Step 8: State limitations

"I did not account for automated API queries or regional variations."

This example shows how to handle a large, complex problem by breaking it down logically.

The importance of communicating your reasoning clearly

An often overlooked part is explaining your thought process. Satyaki emphasizes:

"After solving, take your interviewer through each step in a snapshot way. This helps them follow your thinking and reduces cross-questions. Many estimation questions take 20-30 minutes, so a recap is essential."

If you just blurt out a number without explanation, you lose the signal interviewers want to see.

Top-down vs bottom-up approaches

There are two main ways to approach estimation problems:

• Top-down: Start from a broad number and narrow down with assumptions. For example, start with total population, then internet penetration, then usage patterns.
• Bottom-up: Start from small units and build up. For example, estimate the number of users in a neighborhood, then scale up to the city, state, and country.

Both are valid; choose the one that fits the problem and your comfort.

Asking for data or guidance during the interview

Candidates often wonder if they can ask interviewers for data points. The answer is yes — with care.

"If you don't know a key number, you can ask, 'Can I assume the population of Bangalore is 10 million for this calculation?' or 'Should I consider only advertising revenue or all revenue sources?' Interviewers expect clarifying questions and appreciate you working with assumptions rather than guessing blindly."

Never be afraid to ask, but do not rely on the interviewer to feed you all the data.

Estimation questions in the Indian context

Indian candidates face some unique challenges:

• Less access to precise data during preparation.
• Larger population and regional variation.
• Different user behavior and internet penetration.

This makes asking clarifying questions and stating assumptions even more critical.

MeetingScene: A PM interview with an estimation question

SlackChat: Clarifying questions during an interview

FromTheField: Satyaki Benerji on estimating WhatsApp chats in India

"One of the exercises I give candidates is to estimate the number of WhatsApp chats sent daily across India. This is a complex problem with no public data. The key is to break it down: India's population, percentage of smartphone users, active WhatsApp users, average messages per user per day. Then multiply these components. It's okay to make assumptions but state them clearly. Interviewers want to see your thought process, not a perfect answer."

FieldExercise: Practice your own estimation

JudgmentExercise

PracticeExercise

BranchingScenario: Handling an estimation question under pressure

Where to go next

• Build your problem-solving skills: Structured Problem Solving
• Master mental math for PMs: Mental Math and Quick Calculations
• Practice clarifying questions: Effective Communication in Interviews
• Learn about product metrics: Metrics and KPIs

PL alumni now work at Razorpay, Swiggy, Flipkart, PhonePe, and other leading Indian companies.