Product Sense: Building a Car Shopping Experience Buyers Can Trust

Quick Overview

A product sense prompt asking a product manager to design an experience that helps people shop for and buy a car. It tests scoping between new and used purchases, choosing a buyer segment, ranking pain points such as price fairness and vehicle trust, prioritizing solutions into an MVP, and defining success metrics.

Product Sense: Building a Car Shopping Experience Buyers Can Trust

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are asked to design a product that helps people buy a car. The prompt is deliberately broad, so part of the job is choosing a scope: new or used cars, which kind of buyer, and which stage of the purchase you want to improve. Then walk through the users, their problems, the solutions you would build, how you would prioritize them, and how you would know the product is working. ```hint Follow the purchase journey A car purchase is a long, expensive process with distinct stages, from deciding what to buy to transferring ownership. Find the stage and the buyer where anxiety is highest before you start listing features. ``` ### Clarifying Questions - Should this be a software experience, and if so a standalone app or a vertical inside an existing marketplace that already carries vehicle listings? - Are we focused on new cars bought from dealers, used cars sold by private owners, or both? Trust and pricing problems differ sharply between them. - Is only the buyer side in scope, or should seller tools be part of the design too? - What is the goal: more completed purchases, more confident buyers, or engagement with the listing surface, and in which markets do we launch first? ### What a Strong Answer Covers - A deliberate scope (new versus used, dealer versus private seller) with a reason tied to where buyers struggle most. - Distinct buyer segments, such as first-time buyers, car enthusiasts and resellers, and a reasoned choice of one to serve first. - Pain points mapped to journey stages (choosing a model, judging price, verifying condition and ownership, negotiating, paying and paperwork) and ranked by reach and severity. - Solutions tied to the chosen pains, prioritized by impact against effort into an MVP, including how existing platform assets give an advantage. - A north-star metric that reflects real purchases even when the sale closes offline, with guardrails such as scam reports and seller supply. ### Follow-up Questions - How would you stop scam listings and misrepresented vehicles from eroding buyer trust in a person-to-person car market? - A seller complains that your fair-price indicator labels their car as overpriced. How do you handle accuracy and fairness to sellers? - Most sales close in person after a chat. How would you measure whether the product actually helped someone buy a car?

Overview: A product sense prompt asking a product manager to design an experience that helps people shop for and buy a car. It tests scoping between new and used purchases, choosing a buyer segment, ranking pain points such as price fairness and vehicle trust, prioritizing solutions into an MVP, and defining success metrics.

Meta logo
Meta
Mar 5, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are asked to design a product that helps people buy a car. The prompt is deliberately broad, so part of the job is choosing a scope: new or used cars, which kind of buyer, and which stage of the purchase you want to improve. Then walk through the users, their problems, the solutions you would build, how you would prioritize them, and how you would know the product is working.

Clarifying Questions Guidance

  • Should this be a software experience, and if so a standalone app or a vertical inside an existing marketplace that already carries vehicle listings?
  • Are we focused on new cars bought from dealers, used cars sold by private owners, or both? Trust and pricing problems differ sharply between them.
  • Is only the buyer side in scope, or should seller tools be part of the design too?
  • What is the goal: more completed purchases, more confident buyers, or engagement with the listing surface, and in which markets do we launch first?

What a Strong Answer Covers Guidance

  • A deliberate scope (new versus used, dealer versus private seller) with a reason tied to where buyers struggle most.
  • Distinct buyer segments, such as first-time buyers, car enthusiasts and resellers, and a reasoned choice of one to serve first.
  • Pain points mapped to journey stages (choosing a model, judging price, verifying condition and ownership, negotiating, paying and paperwork) and ranked by reach and severity.
  • Solutions tied to the chosen pains, prioritized by impact against effort into an MVP, including how existing platform assets give an advantage.
  • A north-star metric that reflects real purchases even when the sale closes offline, with guardrails such as scam reports and seller supply.

Follow-up Questions Guidance

  • How would you stop scam listings and misrepresented vehicles from eroding buyer trust in a person-to-person car market?
  • A seller complains that your fair-price indicator labels their car as overpriced. How do you handle accuracy and fairness to sellers?
  • Most sales close in person after a chat. How would you measure whether the product actually helped someone buy a car?