Product design question

How would you improve Facebook Pay?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Product sense for a payments product competing against dominant, trusted incumbents like Venmo and Zelle.

Clarify the core use case: peer to peer payments and small purchases within the Meta app ecosystem.
Identify the pain point: users default to Venmo or Zelle out of habit and trust, so Facebook Pay needs a distinct reason to switch.
Prioritize a unique advantage, such as seamless payment inside Marketplace transactions or group event expense splitting, over copying Venmo's feed.
Propose deep integration with existing high intent flows, like paying directly within a Marketplace chat or splitting a group event's cost.
Address trust: clear fraud protection messaging and fast, visible dispute resolution to build confidence with a skeptical audience.
Define success as payment completion rate within existing high intent flows and repeat usage within those specific contexts.

Correctly frames the challenge as overcoming habit and trust in dominant incumbents, not a feature gap.
Proposes context specific integration, Marketplace and event payments, leveraging Facebook's unique surfaces rather than copying Venmo directly.
Gives an illustrative number, e.g. assumes 20 percent of Marketplace transactions currently move to external payment apps, a target to capture.
Addresses trust explicitly, since payment products live or die on perceived security and fraud protection.

Proposing a generic Venmo clone with a social feed, ignoring Facebook's actual differentiated surfaces.
Not addressing the trust and habit barrier that is the real reason users default to incumbents.
No specific context or use case named where Facebook Pay has a genuine advantage.

Chapters of the AI PM course that teach what this question tests.