Roadmap for Collecting and Using Connected EV Sensor Data in Future Vehicle Programs

Quick Overview

A product strategy question about planning how an electric vehicle maker should use the data from its cars' many sensors in future programs. It tests use-case prioritization, getting data off the vehicle under volume and cost limits, data infrastructure, a phased technology roadmap, and privacy.

Roadmap for Collecting and Using Connected EV Sensor Data in Future Vehicle Programs

Company: Lucid Motors

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are the product manager for an electric vehicle that carries many onboard sensors. Lay out a strategy and roadmap for using the data those sensors produce to support the company's future programs. Your plan should cover how the data gets from the car to the company, the infrastructure needed to store and use it, and how the technology would evolve over time. ```hint Purpose before plumbing A vehicle can produce far more data than any connection can carry. Decide which programs the data must serve first, then let those uses determine what gets collected, how often, and how it leaves the car. ``` ### Clarifying Questions - What does "future programs" mean here: the next vehicle platform, driver-assistance features, after-sales services, or new revenue lines? - Which sensors are on the car, and what connectivity does it have today (cellular, Wi-Fi, a wired port at service centers)? Can its software be updated over the air? - Which markets does the car ship in, and what consent and data-protection rules apply to owners and to people captured by the cameras? - Is the company willing to build its own data platform, or should the plan rely on cloud and partner services? ### What a Strong Answer Covers - A prioritized set of use cases tied to business value, with a clear reason for the order. - A realistic plan for moving data off the vehicle given volume, cost and connectivity limits, including what is processed on the car itself. - An infrastructure design covering ingestion, storage, processing, access and governance. - A phased technology roadmap with milestones, including how the data shapes requirements for the next vehicle. - Privacy, security and customer trust treated as design constraints, with success metrics and guardrails. ### Follow-up Questions - Your camera data team wants every clip uploaded, and finance says connectivity costs are already too high. How do you settle it? - In one major market, regulators require driving data to stay inside the country. How does your architecture change? - Which single use case would you deliver first to prove the program's value to leadership, and how would you measure it?

Overview: A product strategy question about planning how an electric vehicle maker should use the data from its cars' many sensors in future programs. It tests use-case prioritization, getting data off the vehicle under volume and cost limits, data infrastructure, a phased technology roadmap, and privacy.

Lucid Motors logo
Lucid Motors
Feb 12, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are the product manager for an electric vehicle that carries many onboard sensors. Lay out a strategy and roadmap for using the data those sensors produce to support the company's future programs. Your plan should cover how the data gets from the car to the company, the infrastructure needed to store and use it, and how the technology would evolve over time.

Clarifying Questions Guidance

  • What does "future programs" mean here: the next vehicle platform, driver-assistance features, after-sales services, or new revenue lines?
  • Which sensors are on the car, and what connectivity does it have today (cellular, Wi-Fi, a wired port at service centers)? Can its software be updated over the air?
  • Which markets does the car ship in, and what consent and data-protection rules apply to owners and to people captured by the cameras?
  • Is the company willing to build its own data platform, or should the plan rely on cloud and partner services?

What a Strong Answer Covers Guidance

  • A prioritized set of use cases tied to business value, with a clear reason for the order.
  • A realistic plan for moving data off the vehicle given volume, cost and connectivity limits, including what is processed on the car itself.
  • An infrastructure design covering ingestion, storage, processing, access and governance.
  • A phased technology roadmap with milestones, including how the data shapes requirements for the next vehicle.
  • Privacy, security and customer trust treated as design constraints, with success metrics and guardrails.

Follow-up Questions Guidance

  • Your camera data team wants every clip uploaded, and finance says connectivity costs are already too high. How do you settle it?
  • In one major market, regulators require driving data to stay inside the country. How does your architecture change?
  • Which single use case would you deliver first to prove the program's value to leadership, and how would you measure it?