Product Design: What Should a Meta-Built Mapping App Be and Who Is It For?

Quick Overview

A Meta product design interview question that asks the candidate to define a standalone maps app: its purpose, first users, core problems, launch features and success metrics. It tests differentiation against established map apps, use of Meta's social and local signals, and judgment about location privacy.

Product Design: What Should a Meta-Built Mapping App Be and Who Is It For?

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Meta. Leadership wants to explore a maps product that would be its own app rather than a feature inside Facebook, Instagram, WhatsApp or Messenger. Design it. Explain what the app is for and why Meta should build it, which users it serves first and which of their problems it solves, what the first version includes, and how you would measure success. ```hint Look for the job the incumbents miss Established map apps already handle directions well. Before you list features, ask which mapping job Meta's apps and data could serve better than they do, and build the app around that job. ``` ### Clarifying Questions - What does Meta want from the app: engagement, a new home for local business ads, or less reliance on other companies' maps? - Is a base map and turn-by-turn navigation in scope, or can the app use open or licensed map data and hand navigation off to other apps? - Which market comes first: countries where Meta's apps dominate daily communication, or the United States? - With user consent, may the app draw on data from Meta's other apps, such as friends, location tags, saved posts and Events? ### What a Strong Answer Covers - A clear reason for Meta to build a standalone maps app and a position that differs from established map apps - One chosen user segment with specific pain points, rather than everyone who needs directions - Features that draw on Meta's social graph and local content, prioritized into a focused first version - A north-star metric with supporting metrics and privacy guardrails - Risks specific to Meta and location data: user trust, map data quality and the cold start of a new app ### Follow-up Questions - Why a standalone app instead of a map tab inside Instagram or Facebook, and what result would change your mind? - How would you get map and place data good enough for launch without years of mapping work? - How would the app make money without eroding trust in how Meta handles location data?

Overview: A Meta product design interview question that asks the candidate to define a standalone maps app: its purpose, first users, core problems, launch features and success metrics. It tests differentiation against established map apps, use of Meta's social and local signals, and judgment about location privacy.

Meta logo
Meta
Jul 18, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Meta. Leadership wants to explore a maps product that would be its own app rather than a feature inside Facebook, Instagram, WhatsApp or Messenger. Design it.

Explain what the app is for and why Meta should build it, which users it serves first and which of their problems it solves, what the first version includes, and how you would measure success.

Clarifying Questions Guidance

  • What does Meta want from the app: engagement, a new home for local business ads, or less reliance on other companies' maps?
  • Is a base map and turn-by-turn navigation in scope, or can the app use open or licensed map data and hand navigation off to other apps?
  • Which market comes first: countries where Meta's apps dominate daily communication, or the United States?
  • With user consent, may the app draw on data from Meta's other apps, such as friends, location tags, saved posts and Events?

What a Strong Answer Covers Guidance

  • A clear reason for Meta to build a standalone maps app and a position that differs from established map apps
  • One chosen user segment with specific pain points, rather than everyone who needs directions
  • Features that draw on Meta's social graph and local content, prioritized into a focused first version
  • A north-star metric with supporting metrics and privacy guardrails
  • Risks specific to Meta and location data: user trust, map data quality and the cold start of a new app

Follow-up Questions Guidance

  • Why a standalone app instead of a map tab inside Instagram or Facebook, and what result would change your mind?
  • How would you get map and place data good enough for launch without years of mapping work?
  • How would the app make money without eroding trust in how Meta handles location data?