I broke it down by starting with total cars on the road today, then tried to layer in adoption curves by region and use case (ride-share vs personal).
Start by clarifying the scope: which regions, what level of autonomy, and whether 'on the road' means actively driving or just registered. Then use a top-down approach: estimate total vehicles, adoption rate over time, and segment by key markets and use cases. Finally, sanity-check with a bottom-up view from manufacturers' production plans and regulatory timelines.
Pro tip: Acknowledge that this is a highly uncertain estimate and that the value is in the structured reasoning, not the precise number. Tie your answer back to product implications for Dropbox, such as data storage and collaboration needs for autonomous vehicle development.
Ask clarifying questions to define 'self-driving cars' (SAE levels), 'on the road' (active vs. registered), and geographic scope. This shows you can handle ambiguity and align on assumptions.
Calculate the total number of vehicles in the target regions (e.g., US, China, Europe) and project growth over 5-10 years. Consider population, vehicle ownership rates, and replacement cycles.
Break down adoption by autonomy level (L4/L5), use case (personal, robotaxi, commercial), and region. Use analogies from past technology adoptions (e.g., EVs, smartphones) and consider regulatory, technical, and cost barriers.
Multiply total vehicles by adoption rate for each segment and sum. Provide a range (e.g., low, medium, high) to reflect uncertainty. Show your math clearly.
Cross-check with bottom-up data: major automakers' production targets, regulatory timelines, and infrastructure readiness. Adjust your estimate if needed and state key assumptions.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.