Product design question

How would you improve Google Flights?

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 improvement skill for a flight search tool, focused on a real, specific traveler pain point.

Segment users: price-sensitive flexible travelers versus fixed-date business travelers, since their needs differ.
Identify the pain point: uncertainty about whether now is a good time to book, since fares fluctuate and users fear missing a better deal.
Prioritize the flexible traveler segment, since price uncertainty affects them most and Google Flights already has price-tracking data.
Propose a solution: a clearer, more prominent price-confidence indicator, book now versus wait, with a short plain-language reason.
Add a notification layer: proactive alerts when a tracked route's price is unusually low relative to its own history.
Define success: booking conversion rate among users who see the confidence indicator versus those who don't.

Builds on Google Flights' actual existing capability, historical price data, rather than proposing an unrelated new feature.
Picks a real friction point, timing uncertainty, well known to frequent flight searchers.
Proposes a lightweight UI change instead of a large new system, appropriate for an improve prompt.
Uses conversion rate as a direct, measurable success signal.

Proposing unrelated features like loyalty programs that ignore the core search experience.
Not grounding the improvement in a specific, well-known pain point.
Ignoring that Google Flights already has some price-tracking functionality.

How would you validate the price-confidence prediction is actually accurate?
How would you handle a user who ignores the book-now signal and the price drops later?
How would you measure trust in the indicator over time?