Designing a goods-sharing marketplace so people can borrow home items instead of buying

Quick Overview

A product design case about building a marketplace where people borrow and lend household goods rather than money. It tests choosing borrower and lender segments, prioritizing pain points such as trust and returns, solving the cold-start problem, and picking success metrics and guardrails.

Designing a goods-sharing marketplace so people can borrow home items instead of buying

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design a new marketplace where people borrow household goods from one another and lend out their own. The marketplace is non-financial: what changes hands is the item itself, not a loan of money. Explain who you would build it for, which of their problems you would solve first, what the first version of the product would include, and how you would measure whether it is working. ```hint Picture the first successful borrow A marketplace is useful only when the item someone needs is close by and its owner is willing to hand it over. Think about which users and places make that happen soonest, and what worries each side when an item leaves the owner's home. ``` ### Clarifying Questions - Does "non-financial" mean no money changes hands at all, or only that the goods are items rather than loans of money, so that fees or deposits are allowed? - Are we building a standalone product, or a feature inside an existing marketplace or social app such as Facebook Marketplace or Groups? - Which household goods are in scope: tools, appliances, kitchen gear, baby and party supplies, or anything people keep at home? - What is the main objective for the first year: adoption and engagement, community value, or eventual revenue? ### What a Strong Answer Covers - A clear goal and a chosen segment on both the borrower and the lender side, with reasons. - Prioritized pain points, including the lender's worries about damage, loss and returns. - A first version that solves the cold-start problem of having enough items and borrowers in one area. - Concrete trust and safety mechanisms for handoff, item condition and returns. - Success metrics with guardrails, and risks such as liability and how rarely people need any one item. ### Follow-up Questions - A lender's item comes back broken and the borrower says it was already damaged. How should the product handle it? - How would you launch in a new city where nobody has listed anything yet? - If the company later wants revenue from this product, what model would you choose without breaking its community feel? - Suppose the exercise is set at Facebook and limited to neighbors. How would you design lending as a feature inside Facebook, and how would you use its real profiles, social graph and local Groups? - Suppose the prompt only says that Facebook wants to help its users borrow and lend, and does not say what changes hands. How would you decide between lending physical items and lending money, and how do the risks and the lending regulation of each option shape that decision? - Sketch the main objects the system must store and the states a single loan moves through, from the first request until the item is back with its owner. Where do reviews and notifications fit in?

Overview: A product design case about building a marketplace where people borrow and lend household goods rather than money. It tests choosing borrower and lender segments, prioritizing pain points such as trust and returns, solving the cold-start problem, and picking success metrics and guardrails.

Meta logo
Meta
Dec 28, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design a new marketplace where people borrow household goods from one another and lend out their own. The marketplace is non-financial: what changes hands is the item itself, not a loan of money. Explain who you would build it for, which of their problems you would solve first, what the first version of the product would include, and how you would measure whether it is working.

Clarifying Questions Guidance

  • Does "non-financial" mean no money changes hands at all, or only that the goods are items rather than loans of money, so that fees or deposits are allowed?
  • Are we building a standalone product, or a feature inside an existing marketplace or social app such as Facebook Marketplace or Groups?
  • Which household goods are in scope: tools, appliances, kitchen gear, baby and party supplies, or anything people keep at home?
  • What is the main objective for the first year: adoption and engagement, community value, or eventual revenue?

What a Strong Answer Covers Guidance

  • A clear goal and a chosen segment on both the borrower and the lender side, with reasons.
  • Prioritized pain points, including the lender's worries about damage, loss and returns.
  • A first version that solves the cold-start problem of having enough items and borrowers in one area.
  • Concrete trust and safety mechanisms for handoff, item condition and returns.
  • Success metrics with guardrails, and risks such as liability and how rarely people need any one item.

Follow-up Questions Guidance

  • A lender's item comes back broken and the borrower says it was already damaged. How should the product handle it?
  • How would you launch in a new city where nobody has listed anything yet?
  • If the company later wants revenue from this product, what model would you choose without breaking its community feel?
  • Suppose the exercise is set at Facebook and limited to neighbors. How would you design lending as a feature inside Facebook, and how would you use its real profiles, social graph and local Groups?
  • Suppose the prompt only says that Facebook wants to help its users borrow and lend, and does not say what changes hands. How would you decide between lending physical items and lending money, and how do the risks and the lending regulation of each option shape that decision?
  • Sketch the main objects the system must store and the states a single loan moves through, from the first request until the item is back with its owner. Where do reviews and notifications fit in?