Product design question

How would you design a wedding registry?

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

Basic product design skill for a niche transactional use case, requiring the candidate to identify the multiple stakeholders involved.

Identify all stakeholders: the couple creating the registry, gift-givers browsing and purchasing, and potentially multiple retailers if items come from different stores.
Name the core pain points: couples wanting flexibility across multiple stores without managing separate lists, and gift-givers wanting to avoid duplicate purchases.
Propose a focused feature: a universal registry that aggregates items from multiple retailers into one shareable list with real-time purchased-status sync to prevent duplicates.
Consider monetization: an affiliate or referral fee from partner retailers when a registry item is purchased through the platform.
Define success as percent of registry items purchased before the event date, and duplicate-purchase rate as a guardrail.

Explicitly names both sides of the transaction, the couple and the gift-givers, rather than designing only for one.
Solves the real, well-known pain point of duplicate gifts with real-time sync across contributors.
Names a monetization model consistent with how registry and gifting products typically make money.

Designing only for the couple's experience and ignoring the gift-giver's browsing and purchasing flow.
No mention of the duplicate-purchase problem, one of the most well-known pain points in wedding registries.

How would you handle cash-fund gifts alongside physical registry items?
How would you convince retailers to integrate with a universal registry instead of keeping couples on their own platform?