Invent a Phone-Native Facebook Feature: Goal, Users, MVP and Metrics
Company: Meta
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
Suppose you are a product manager asked to create a new experience inside Facebook, designed for the phone first. What would you build?
Pick the idea, explain why it is the right bet for Facebook and for its users, and walk through who it serves, the problems it solves, what the first version includes and how you would judge whether it worked.
```hint Lean on the device
List what a phone offers that a laptop does not (the camera, location, being carried everywhere, notifications) and which moments in people's social lives depend on those. A phone-first idea should need at least one of them, not just fit on a smaller screen.
```
### Clarifying Questions
- Does "new experience" have to be a feature Facebook does not offer today, or may it be a substantial reinvention of an existing surface such as Events, Groups, Stories or Marketplace?
- Is there a company goal it should serve, for example daily engagement, winning back young adults or meaningful connection between friends, or is choosing the goal part of the exercise?
- Must it live inside the main Facebook app, or could it ship as a separate app?
- Which market comes first: one where most people have recent smartphones and fast data, or one where low-end Android phones and costly data are common?
### What a Strong Answer Covers
- A goal chosen up front and tied to Facebook's mission and business, followed by a survey of phone-specific opportunities across Facebook surfaces rather than a jump to a favorite feature.
- One clearly chosen user segment, its concrete pain points, and why current Facebook features and competing apps leave them unsolved.
- An idea that depends on what the phone uniquely offers, scoped to a first version and prioritized by impact against effort, with trade-offs such as overlap with Messenger or Events and time taken from Feed.
- A success metric tied to the chosen goal, plus guardrails for privacy, safety, notification fatigue and cannibalization of other surfaces.
- Risks, how the launch would be tested, and what would make you stop.
### Follow-up Questions
- The new surface grows quickly, yet total Facebook sessions per user stay flat. Is that a success?
- How would your idea change for people on low-end Android phones with patchy connectivity?
- Six months after launch, which results would make you shut the feature down?
Overview: A product sense prompt that asks a product manager to invent a new phone-first experience for the Facebook app. It tests choosing a goal and a user segment, finding real pain points, using what mobile devices uniquely offer, scoping a first version, and defining success metrics with guardrails.