Design a self-driving car product: riders, trip experience and safety metrics

Design an automated car: a vehicle that can drive itself. Treat it as a product problem: decide whom the car is for and which trips it serves, describe the experience you would build around it, and explain how you would know it is succeeding. ```hint Who gains the most Automation matters most to whoever no longer has to drive, and that is not the same person on every trip. Decide which riders and which journeys you are building for before you choose features. ``` ### Clarifying Questions - How much automation is expected: assistance that a human driver supervises, or a car that drives with nobody at the wheel? - Is this a car people buy and own, or a vehicle that serves riders as part of a shared ride service? - Are we designing the whole vehicle, or mainly the rider-facing experience in and around it? - Where must the first version operate: a defined city area, highways, or anywhere a person can drive? ### What a Strong Answer Covers - A stated automation level and ownership model, with reasons. - A chosen rider segment and trip type, with the pain points that self-driving actually solves for them. - The end-to-end experience before, during and after a trip, including what happens when the car cannot continue. - Safety, trust and regulation treated as requirements, plus a prioritized first version. - Metrics that balance adoption with safety and reliability. ### Follow-up Questions - Mid-trip, the car meets a situation it cannot handle with a passenger aboard. What should the car do, and what should the passenger see and hear? - How would the design change for a rider who is blind or uses a wheelchair? - Safety data shows the car is performing well, yet riders still say they feel unsafe. What would you do?