Data Requirements for a Tesla Low-Range Warning Before the Next Charger

You are a product manager at Tesla. Your team is building a feature that warns drivers when the car does not have enough charge left to get to the next charging station. What data would the team need to make this feature work? ```hint Recompute the comparison Treat the warning as a comparison the car keeps recalculating while it drives. List everything that can change either side of that comparison, and where each piece of information would come from. ``` ### Clarifying Questions - Does the car know the destination because the driver entered a route, or must the warning also work when no route is set? - Does "next charging station" mean only the company's own fast chargers, or any compatible public charger, including destination and home charging? - Should the feature only warn, or also suggest a charging stop, a reroute or a change in driving that stretches the range? - Which data can the feature use under drivers' privacy settings, and must it work without a network connection? ### What a Strong Answer Covers - A clear statement of the prediction the warning depends on and when the warning should fire. - Complete coverage of the inputs that change the energy available or the energy needed to reach a charger, with the reason each one matters. - Where each input comes from, how fresh it must be, and how the feature behaves when data is missing or stale. - How the team would validate prediction accuracy and set the threshold that balances missed warnings against false alarms. - Privacy, connectivity and driver-trust considerations. ### Follow-up Questions - Drivers start ignoring the warning because it fires too often. What data would you look at, and what would you change? - The charger the feature recommends shows as available but is out of service when the driver arrives. How does that change the data you need? - How would you measure whether the feature reduces the number of cars that run out of charge on the road?