Product design question

Create a new product relevant to Google's existing product line targeted at people using public transit.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Product strategy tied to an existing portfolio: extending a company's product line into an adjacent use case rather than inventing from scratch.

Clarify scope: which Google product line to extend, for example Maps, Pay, or Wallet, since public transit riders interact with several.
Identify the user: daily public transit commuters who juggle schedules, fares, and transfers across multiple transit systems.
Name the pain point: fragmented fare payment and unreliable real time arrival data across different transit agencies with inconsistent digital systems.
Propose a product: a unified transit pass within Google Wallet that aggregates fares and real time arrivals across agencies, building on Google Maps' existing transit data.
Prioritize fare aggregation first since payment friction is a daily, high frequency pain point compared with schedule information, which Maps partly covers already.
Define success as adoption rate among regular transit riders and reduction in fare-related support complaints.

Builds explicitly on an existing Google asset, Maps transit data and Wallet, rather than proposing a disconnected new product.
Targets a specific high frequency pain point, fragmented fare payment, instead of a vague 'better transit experience'.
Picks daily active rider adoption as the metric, appropriate for a high frequency utility product.

Proposing a product disconnected from Google's actual existing assets and data.
Ignoring the difficulty of partnering with many separate, often slow moving transit agencies.

Chapters of the AI PM course that teach what this question tests.