Choose and Design a Product for the 2028 Los Angeles Summer Olympics Host Committee

Quick Overview

A product sense question that puts you on the organizing committee for the 2028 Los Angeles Summer Olympics and asks what product you would build. It tests choosing a stakeholder group, grounding pain points in the host city, prioritizing a first version for a fixed launch date, and picking metrics that can be read during a short event.

Choose and Design a Product for the 2028 Los Angeles Summer Olympics Host Committee

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You sit on the organizing committee for the 2028 Summer Olympic Games in Los Angeles. What product would you build? ```hint Start from what the host is judged on An organizing committee succeeds or fails over a few weeks of competition spread across one very large metro area. Ask which group's Games-day experience most decides that verdict, and what makes that experience hard in Los Angeles in particular. ``` ### Clarifying Questions - Is the product for spectators, athletes and team staff, volunteers and workforce, or residents living around the venues, or is that choice mine? - Which outcome matters most to the committee here: ticket and sponsorship revenue, a smooth operation on competition days, or a legacy that lasts after the Games? - Should it cover only the Olympic Games, or also the Paralympic Games that follow and the months of build-up before them? - Can we partner with transit agencies, the ticketing provider and existing map apps, or must the committee build and run everything itself? ### What a Strong Answer Covers - A goal tied to what an organizing committee is accountable for, and a clear reason the product serves it - A deliberate choice among stakeholder groups, with the alternatives considered and set aside - Pain points specific to these Games and this city, and a prioritized solution whose first version can be ready and reliable by opening day - Success metrics that can be read inside a short, fixed event window, with guardrails - Risks such as peak-day load, dependence on outside partners, and a product used intensely for weeks and then not at all ### Follow-up Questions - Usage will spike for a few weeks and then collapse. How does that change what you build yourself, what you buy, and what you get partners to own? - On the first competition day your live travel estimates are wrong and thousands of fans are sent to the same station. What safeguards should the design have had? - With no time for a long experiment before the Games, how would you know whether the product helped, and what would you measure during the Games versus afterward?

Overview: A product sense question that puts you on the organizing committee for the 2028 Los Angeles Summer Olympics and asks what product you would build. It tests choosing a stakeholder group, grounding pain points in the host city, prioritizing a first version for a fixed launch date, and picking metrics that can be read during a short event.

Meta logo
Meta
Feb 12, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You sit on the organizing committee for the 2028 Summer Olympic Games in Los Angeles. What product would you build?

Clarifying Questions Guidance

  • Is the product for spectators, athletes and team staff, volunteers and workforce, or residents living around the venues, or is that choice mine?
  • Which outcome matters most to the committee here: ticket and sponsorship revenue, a smooth operation on competition days, or a legacy that lasts after the Games?
  • Should it cover only the Olympic Games, or also the Paralympic Games that follow and the months of build-up before them?
  • Can we partner with transit agencies, the ticketing provider and existing map apps, or must the committee build and run everything itself?

What a Strong Answer Covers Guidance

  • A goal tied to what an organizing committee is accountable for, and a clear reason the product serves it
  • A deliberate choice among stakeholder groups, with the alternatives considered and set aside
  • Pain points specific to these Games and this city, and a prioritized solution whose first version can be ready and reliable by opening day
  • Success metrics that can be read inside a short, fixed event window, with guardrails
  • Risks such as peak-day load, dependence on outside partners, and a product used intensely for weeks and then not at all

Follow-up Questions Guidance

  • Usage will spike for a few weeks and then collapse. How does that change what you build yourself, what you buy, and what you get partners to own?
  • On the first competition day your live travel estimates are wrong and thousands of fans are sent to the same station. What safeguards should the design have had?
  • With no time for a long experiment before the Games, how would you know whether the product helped, and what would you measure during the Games versus afterward?