Product design question
As the Project Manager for the driver app at a rideshare company (similar to Uber or Lyft), brainstorm the implementation of a bathroom feature to assist our drivers in finding restrooms during their routes.
- Meta
- Product design
- Medium
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests product sense for a niche driver-welfare feature: can you scope something small, tie it to driver retention, and avoid over-building.
How to approach it
- Define the user and pain point: drivers on long shifts who cannot easily find a clean, accessible restroom, which affects shift length and satisfaction.
- Identify the underlying goal: this is a driver-retention and shift-duration feature, not a rider-facing one, so success should be measured on driver side metrics.
- Brainstorm a few concrete implementations: a map layer showing partner locations (gas stations, restaurants with agreements) with real-time availability, a crowdsourced driver-rated restroom list, or partnerships with chains like Starbucks for guaranteed access.
- Prioritize the crowdsourced list plus a curated partner layer as the MVP, since it needs no new hardware and can launch with existing map infrastructure.
- Consider rollout: start in one or two markets with high driver churn, gather feedback, then expand.
- Define success as driver-reported satisfaction lift and possibly a small reduction in mid-shift driver churn or shift cancellations.
What a strong answer includes
- Ties the feature explicitly to a business metric (driver retention or hours driven per shift), not just goodwill.
- Proposes a low-cost MVP (crowdsourced tags on existing map) instead of an expensive new partner network from day one.
- Flags a real constraint: restroom access varies hugely by location type (highway vs. dense urban), so the design must adapt to local density.
- Suggests a lightweight success metric: percentage of drivers who use the feature weekly, as a proxy for real need.
Common mistakes
- Over-engineering with a full partner-negotiation program before validating driver demand with a cheap crowdsourced version.
- Not connecting the feature back to a business metric like retention or utilization.
- Forgetting the safety angle: drivers may need this most in unfamiliar areas late at night.
Likely follow-up questions
- How would you validate driver demand for this before building it?
- How would you handle inaccurate or outdated crowdsourced restroom data?
- Would you build this for riders too, or keep it driver-only? Why?
More product design questions
- You’ve just joined Meta and have been tasked with launching a new product to help people at home during emergencies. What would you build?Meta · Product design · Medium
- How would you improve the Facebook Timeline?Meta · Product design · Easy
- Build a volunteer product for Facebook.Meta · Product design · Medium
- Design an application launching in the US marketplace that enables patients to find doctors.Meta · Product design · Hard
- Design a washing machine for Google.Google · Product design · Hard
- How would you make WhatsApp more user-friendly for the elderly to use?Meta · Product design · Medium
More questions from Meta
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop