← Google Interview Insights

Google·Product Manager·Onsite - Product Sense / Strategy·Senior

Senior
May 2026

Summary

Google PM interview with a product design and estimation question rolled into one. Not the hardest thing I've ever done but the estimation piece tripped me up more than I expected.

Questions Asked (1)

Q1

How would you design an elevator system for a skyscraper, and how many elevators would you estimate are needed?

System DesignProduct Sense & IdeationAdaptability & Ambiguity
Author's notes

I spent way too long on the design half and then rushed the estimation, which I think was the wrong call.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then break the problem into user needs, system components, and capacity estimation. Use a structured framework to design the elevator system and estimate the number of elevators based on peak demand and service level targets.

Pro tip: Always state your assumptions explicitly and validate them with the interviewer; this shows you can navigate ambiguity and collaborate effectively. Also, consider both quantitative (e.g., waiting time) and qualitative (e.g., user experience) factors in your design.

1. Clarify Requirements and Constraints

Ask questions to understand building specifics (height, floors, population), user expectations (wait time, capacity), and any constraints (budget, space, technology).

2. Define User Needs and Service Level

Identify key user groups (employees, visitors) and their patterns (peak hours, traffic flow). Set service level targets such as average wait time and maximum wait time.

3. Design System Components

Outline the elevator system architecture: number of shafts, elevator types (passenger, freight), control algorithms (smart grouping, destination dispatch), and safety features.

4. Estimate Capacity and Number of Elevators

Calculate peak demand using building population, arrival rates, and elevator capacity. Use formulas or simulation to determine the number of elevators needed to meet service level targets.

5. Validate and Iterate

Check if the design meets requirements, consider trade-offs (cost vs. performance), and propose optimizations or alternatives (e.g., double-deck elevators, sky lobbies).

Key Points to Mention

  • Building population and peak traffic patterns (e.g., morning up-peak, lunchtime two-way traffic).
  • Elevator capacity (number of passengers) and speed (floors per second).
  • Round-trip time calculation and handling capacity formula.
  • Service level metrics: average waiting time, 95th percentile waiting time, and handling capacity.
  • Advanced technologies: destination dispatch, double-deck elevators, and sky lobbies.
  • Trade-offs between cost, space, and user experience.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.