Facebook Echo expansion: find, rank and validate an adjacent revenue stream for Meta

Quick Overview

A product strategy question that asks how a Meta product manager would create a new line of business around Facebook Echo. It tests grounding an ambiguous product, generating and scoring options from Meta's assets, validating a business model with stage gates, and choosing success metrics, guardrails and risks.

Facebook Echo expansion: find, rank and validate an adjacent revenue stream for Meta

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Meta working on Facebook Echo, and you have been asked to create a new line of business around it: a source of revenue that goes beyond what Echo does today. Explain how you would approach this, from understanding the starting point and generating options to choosing one, testing it, bringing it to market and deciding whether it is working. ```hint Start from what Echo already owns Before listing markets, take stock of what Echo and the rest of Meta bring: where the product sits in people's lives, who uses it, and which Meta products and relationships it can draw on. The strongest options are businesses those assets give Meta a reason to win. ``` ### Clarifying Questions - What is Facebook Echo today (a home device, a feature inside Meta's apps, or a standalone service), and how many people use it and how often? - Does "new line of business" mean charging current Echo users for something new, serving a new kind of customer such as businesses, or either? - What does Meta want most from it: revenue that matters on its own, or a stronger pull toward Meta's apps, ads and business messaging? - Are any business models ruled out, for example advertising inside Echo or selling hardware below cost? ### What a Strong Answer Covers - A stated and confirmed understanding of what Echo is, who uses it and what Meta wants from a new business, before any ideas. - Several distinct candidate businesses generated from Echo's and Meta's assets, not a single idea. - Explicit criteria such as market size, willingness to pay, Meta's right to win, fit with Echo and risk, used to choose one. - A cheap validation plan with stage gates, plus the business model and go-to-market for the chosen option. - Success metrics with guardrails and the main risks, especially privacy and trust in a Meta-owned product. ### Follow-up Questions - Your choice depends on people paying a subscription, which is not how Meta usually earns money. How would you test willingness to pay before building much? - The business would grow faster if signals from Echo were used to target ads. Would you allow that, and how would you decide? - A year into the pilot, engagement is strong but revenue is well below plan. Do you continue, change course or stop, and what evidence decides it?

Overview: A product strategy question that asks how a Meta product manager would create a new line of business around Facebook Echo. It tests grounding an ambiguous product, generating and scoring options from Meta's assets, validating a business model with stage gates, and choosing success metrics, guardrails and risks.

Meta logo
Meta
Sep 8, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Meta working on Facebook Echo, and you have been asked to create a new line of business around it: a source of revenue that goes beyond what Echo does today. Explain how you would approach this, from understanding the starting point and generating options to choosing one, testing it, bringing it to market and deciding whether it is working.

Clarifying Questions Guidance

  • What is Facebook Echo today (a home device, a feature inside Meta's apps, or a standalone service), and how many people use it and how often?
  • Does "new line of business" mean charging current Echo users for something new, serving a new kind of customer such as businesses, or either?
  • What does Meta want most from it: revenue that matters on its own, or a stronger pull toward Meta's apps, ads and business messaging?
  • Are any business models ruled out, for example advertising inside Echo or selling hardware below cost?

What a Strong Answer Covers Guidance

  • A stated and confirmed understanding of what Echo is, who uses it and what Meta wants from a new business, before any ideas.
  • Several distinct candidate businesses generated from Echo's and Meta's assets, not a single idea.
  • Explicit criteria such as market size, willingness to pay, Meta's right to win, fit with Echo and risk, used to choose one.
  • A cheap validation plan with stage gates, plus the business model and go-to-market for the chosen option.
  • Success metrics with guardrails and the main risks, especially privacy and trust in a Meta-owned product.

Follow-up Questions Guidance

  • Your choice depends on people paying a subscription, which is not how Meta usually earns money. How would you test willingness to pay before building much?
  • The business would grow faster if signals from Echo were used to target ads. Would you allow that, and how would you decide?
  • A year into the pilot, engagement is strong but revenue is well below plan. Do you continue, change course or stop, and what evidence decides it?