Kids as Passengers: Extending a Car-Sharing App to Serve Children and Parents

Quick Overview

A product design prompt asking how an established car-sharing app could launch a product for kids, with parents booking and paying while children ride. It tests choosing an age group and use case, designing around safety and trust, keeping drivers engaged, scoping a first version and setting metrics with safety guardrails.

Kids as Passengers: Extending a Car-Sharing App to Serve Children and Parents

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at a well-established car-sharing app. Design a new product, built inside that existing app, that serves kids. Explain who the product is for, which problems it solves, what the first version includes, and how you would measure whether it succeeds. ```hint Two customers in one ride The child is in the car, but a parent or guardian usually decides, books, pays and carries the worry. Work out what each of them needs, and which concern stops families from using the app for their kids today. ``` ### Clarifying Questions - Does "car-sharing" here mean ride-hailing with a driver, carpools between families, or cars rented by the hour that people drive themselves? Children cannot drive, so this decides whether they are passengers in someone else's car or riders in a family's rental. - Which ages count as kids: young children who need car seats, pre-teens, or teenagers old enough to ride without an adult? - Will children ride without a parent in the car, and in which markets do we launch first, given that rules on unaccompanied minors and child seats vary by place? - What does the business want from this: new riders, more trips from parents who already use the app, or loyal future adult customers? ### What a Strong Answer Covers - The parent who books and pays, the child who rides and the driver who carries them, with the needs of each. - A chosen age band and use case, with the reasons the other ages are deferred. - Safety and trust as the foundation of the design: driver eligibility, live visibility, verified pickup and drop-off, and emergency handling. - A scoped first version that reuses what the app already does, and a clear list of what waits. - Success metrics for adoption and repeat use, with safety guardrails, plus the legal and driver-supply risks. ### Follow-up Questions - Drivers start declining kids' trips because they feel the extra responsibility is not worth it. How do you keep enough drivers in the program? - A serious safety incident occurs on a child's ride in the first month after launch. What do you do, in the product and beyond it? - What evidence would you need before extending the product to younger children?

Overview: A product design prompt asking how an established car-sharing app could launch a product for kids, with parents booking and paying while children ride. It tests choosing an age group and use case, designing around safety and trust, keeping drivers engaged, scoping a first version and setting metrics with safety guardrails.

Meta logo
Meta
Jan 13, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at a well-established car-sharing app. Design a new product, built inside that existing app, that serves kids. Explain who the product is for, which problems it solves, what the first version includes, and how you would measure whether it succeeds.

Clarifying Questions Guidance

  • Does "car-sharing" here mean ride-hailing with a driver, carpools between families, or cars rented by the hour that people drive themselves? Children cannot drive, so this decides whether they are passengers in someone else's car or riders in a family's rental.
  • Which ages count as kids: young children who need car seats, pre-teens, or teenagers old enough to ride without an adult?
  • Will children ride without a parent in the car, and in which markets do we launch first, given that rules on unaccompanied minors and child seats vary by place?
  • What does the business want from this: new riders, more trips from parents who already use the app, or loyal future adult customers?

What a Strong Answer Covers Guidance

  • The parent who books and pays, the child who rides and the driver who carries them, with the needs of each.
  • A chosen age band and use case, with the reasons the other ages are deferred.
  • Safety and trust as the foundation of the design: driver eligibility, live visibility, verified pickup and drop-off, and emergency handling.
  • A scoped first version that reuses what the app already does, and a clear list of what waits.
  • Success metrics for adoption and repeat use, with safety guardrails, plus the legal and driver-supply risks.

Follow-up Questions Guidance

  • Drivers start declining kids' trips because they feel the extra responsibility is not worth it. How do you keep enough drivers in the program?
  • A serious safety incident occurs on a child's ride in the first month after launch. What do you do, in the product and beyond it?
  • What evidence would you need before extending the product to younger children?