Product Sense: Help People Relocating to an Unfamiliar City Settle In

Quick Overview

A Google product manager interview question: design a product for people relocating to a city that is new to them. It tests segmenting movers, mapping pain points across the relocation timeline, scoping a focused first version, and choosing success metrics that suit an infrequent life event.

Product Sense: Help People Relocating to an Unfamiliar City Settle In

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are interviewing for a product manager role at Google. Design a product for people who are relocating to a city that is new to them. Decide whom you are building for and which part of the move to focus on, then describe the product, walk through how someone would use it, and explain how you would know it is working. ```hint Map the move as a timeline A relocation runs from deciding where to live, through the physical move, to the months of building a routine afterward. The biggest unmet need is not necessarily the most visible step. ``` ### Clarifying Questions - Should the product build on existing Google products such as Maps, Search or Calendar, or can it be anything, including a standalone app, a service or hardware? - Does the person already know which city they are moving to, or should the product also help them choose one? - Is the move within one country, or are international relocations, with visas, banking and language barriers, in scope? - Is success judged by user value alone, by engagement with Google products, or by a new revenue line? ### What a Strong Answer Covers - A goal for the product and a reason it fits Google's strengths and data. - Distinct mover segments, defined by life stage and reason for moving, with a justified choice of one. - Pain points across the relocation timeline, prioritized by severity and frequency. - A focused first version with a walk-through of the user's experience, plus what is deliberately left out. - Success metrics suited to an infrequent life event, with guardrails on privacy, accuracy and fair-housing risk. ### Follow-up Questions - People move only every few years. Would you design the product to be used intensely for a few months and then fade, or to stay relevant after someone has settled in, and why? - How would you reach people at the moment they decide to move without making them uneasy that Google knows about it? - If engineering could deliver only half of your first version, what would you cut first?

Overview: A Google product manager interview question: design a product for people relocating to a city that is new to them. It tests segmenting movers, mapping pain points across the relocation timeline, scoping a focused first version, and choosing success metrics that suit an infrequent life event.

Google logo
Google
Dec 25, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are interviewing for a product manager role at Google. Design a product for people who are relocating to a city that is new to them. Decide whom you are building for and which part of the move to focus on, then describe the product, walk through how someone would use it, and explain how you would know it is working.

Clarifying Questions Guidance

  • Should the product build on existing Google products such as Maps, Search or Calendar, or can it be anything, including a standalone app, a service or hardware?
  • Does the person already know which city they are moving to, or should the product also help them choose one?
  • Is the move within one country, or are international relocations, with visas, banking and language barriers, in scope?
  • Is success judged by user value alone, by engagement with Google products, or by a new revenue line?

What a Strong Answer Covers Guidance

  • A goal for the product and a reason it fits Google's strengths and data.
  • Distinct mover segments, defined by life stage and reason for moving, with a justified choice of one.
  • Pain points across the relocation timeline, prioritized by severity and frequency.
  • A focused first version with a walk-through of the user's experience, plus what is deliberately left out.
  • Success metrics suited to an infrequent life event, with guardrails on privacy, accuracy and fair-housing risk.

Follow-up Questions Guidance

  • People move only every few years. Would you design the product to be used intensely for a few months and then fade, or to stay relevant after someone has settled in, and why?
  • How would you reach people at the moment they decide to move without making them uneasy that Google knows about it?
  • If engineering could deliver only half of your first version, what would you cut first?