Meta Rooms: Why Build an In-House Video Chat Tool, Plus Goals and Success Metrics
Company: Meta
Role: Product Manager
Category: Analytics & Experimentation
Difficulty: medium
Interview Round: Other
You are a product manager at Meta. Meta created Rooms, an internal video-chat product in the same space as Zoom. Explain why Meta built it, then set goals for the product and describe how you would measure its success.
### Clarifying Questions
- Does "internal" mean Rooms is used only by Meta employees for their own meetings, or that Meta built it in-house for people on its consumer apps?
- Should Rooms support meetings with people outside Meta, such as partners, vendors and job candidates, or only calls between employees?
- Does Rooms replace a third-party meeting tool employees use today, and are they required to switch or free to choose?
- Is lowering spend on licensed meeting software an explicit goal, or is the motivation mainly strategic?
### Part 1 — Why Meta built Rooms
Give the most likely reasons Meta chose to build its own video-chat product instead of relying only on an existing tool such as Zoom.
```hint What Meta already has
Ask what makes building cheaper or more valuable for Meta than for a typical company of its size, and what Meta could learn from running its own calls every day.
```
#### What This Part Should Cover
- Reasons specific to Meta's position, not reasons any company could give
- Which reason matters most, and the logic behind that ranking
- The costs and risks of building instead of buying
### Part 2 — Goals and success metrics
How would you set goals for Rooms and measure its success? Name a primary metric, supporting metrics and guardrails, and explain how you would judge the results.
```hint Usage can be mandated
If employees are told to use Rooms, meeting counts mostly reflect the policy. Look for signals that show whether the meetings themselves work.
```
#### What This Part Should Cover
- Goals that follow from the reasons given in Part 1, in priority order
- A primary metric plus supporting metrics for adoption, call quality and satisfaction
- Guardrails, and a way to compare Rooms with the tool it replaces
### What a Strong Answer Covers
- Settling what "internal" means and stating the assumption before answering
- A consistent thread from the reasons for building, to the goals, to the metrics
- Judging Rooms against the alternative meeting tool, not against having no video at all
- Security, privacy and external-meeting risks of running employees' calls in-house
### Follow-up Questions
- A year after launch, most meetings with outside partners still happen on a third-party tool. Is that a failure, and what would you do about it?
- How would your goals and metrics change if Rooms were a consumer feature inside Messenger rather than an employee tool?
- Leadership proposes using recordings of employee calls to train video and avatar models. How would you evaluate that proposal?
Overview: A product manager case on Meta's Rooms video-chat tool: explain why Meta would build its own Zoom-like product, then set prioritized goals and success metrics. It tests build-versus-buy reasoning, choosing metrics when usage may be mandated, and guardrails for call quality, security and cost.