Product design question

How would you select one particular zoom level for the MVP launch of the Google Maps mobile app?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests scoping an MVP decision under real constraints, balancing user context, device limits and a single launch default.

Clarify the goal: pick one sensible default zoom level for first launch, not build a fully adaptive zoom system yet.
Identify the primary use case: most mobile map opens are for immediate, nearby navigation or search, not broad regional browsing.
Consider constraints: small mobile screens limit how much detail is legible at once, and battery or data cost favors loading less map tile data by default.
Propose a street-level default, roughly showing a few nearby blocks, since it best serves the dominant nearby-navigation use case while staying legible on a small screen.
Define success as reduced manual zoom-adjustment actions per session and faster time to first relevant result after opening the app.

Anchors the decision in the dominant real use case, nearby navigation, instead of an arbitrary middle-ground zoom.
Explicitly weighs mobile screen and data constraints as real MVP-stage limits, not just an ideal-world answer.
Picks a measurable proxy, manual zoom adjustments per session, to validate the default choice after launch.

Picking a zoom level with no stated rationale tied to the dominant use case.
Ignoring mobile-specific constraints like screen size and data cost at MVP stage.

How would you personalize the default zoom level after MVP, based on past behavior?
How would you handle the very different needs of a driver versus a pedestrian?