Google Flights after purchase: rank traveler pain points and pick one to fix

Quick Overview

A product prioritization question about Google Flights that asks how to find the most painful part of a traveler's experience after a flight is booked and decide what to fix first. It tests journey mapping beyond search, a clear definition of the worst problem, airline and agency constraints, and success metrics.

Google Flights after purchase: rank traveler pain points and pick one to fix

Company: DoorDash

Role: Product Manager

Category: Product / Decision Making

Difficulty: medium

Interview Round: Other

After a traveler books a flight they found on Google Flights, what is the worst part of their experience, and how would you prioritize solving it? ```hint Follow the trip, not the app Most of what happens after booking takes place away from the search results page. List the moments between purchase and getting home, and agree on what makes one of them "worst" before you rank them. ``` ### Clarifying Questions - Does "post-booking" include trips the traveler completed on an airline or travel-agency site after Google Flights handed them off, or only bookings completed within Google? - Is the goal traveler satisfaction and trust, more return visits for the next trip search, or booking revenue for Google and its partners? - Which travelers matter most: occasional leisure travelers, frequent business flyers, or international travelers with connections? - Are we limited to what Google Flights itself owns, or can the solution use other Google surfaces such as Gmail, Maps or Search? ### What a Strong Answer Covers - A clear view of what Google Flights can and cannot do after booking, given that it usually does not hold the ticket. - A post-booking journey map (confirmation, airline changes and fare drops, check-in, day-of-travel disruptions, refunds) with pain points at each stage. - An explicit definition of "worst" (severity, frequency, reach, ability to act) applied to rank the pain points. - A chosen problem with a feasible solution, its airline and agency dependencies, and a sequenced plan. - Success metrics and guardrails, plus risks such as data accuracy and partner relationships. ### Follow-up Questions - Airlines own the booking record and may not share changes with you. How does your solution work if a major airline refuses to integrate? - How would you show that fixing a post-booking problem brings travelers back to Google Flights for their next search? - Your worst pain point is disruptions, but fare-drop alerts after purchase are far cheaper to build. How do you decide what ships first?

Overview: A product prioritization question about Google Flights that asks how to find the most painful part of a traveler's experience after a flight is booked and decide what to fix first. It tests journey mapping beyond search, a clear definition of the worst problem, airline and agency constraints, and success metrics.

DoorDash logo
DoorDash
Dec 28, 2025
mediumProduct ManagerOtherProduct / Decision Making
0
0

After a traveler books a flight they found on Google Flights, what is the worst part of their experience, and how would you prioritize solving it?

Clarifying Questions Guidance

  • Does "post-booking" include trips the traveler completed on an airline or travel-agency site after Google Flights handed them off, or only bookings completed within Google?
  • Is the goal traveler satisfaction and trust, more return visits for the next trip search, or booking revenue for Google and its partners?
  • Which travelers matter most: occasional leisure travelers, frequent business flyers, or international travelers with connections?
  • Are we limited to what Google Flights itself owns, or can the solution use other Google surfaces such as Gmail, Maps or Search?

What a Strong Answer Covers Guidance

  • A clear view of what Google Flights can and cannot do after booking, given that it usually does not hold the ticket.
  • A post-booking journey map (confirmation, airline changes and fare drops, check-in, day-of-travel disruptions, refunds) with pain points at each stage.
  • An explicit definition of "worst" (severity, frequency, reach, ability to act) applied to rank the pain points.
  • A chosen problem with a feasible solution, its airline and agency dependencies, and a sequenced plan.
  • Success metrics and guardrails, plus risks such as data accuracy and partner relationships.

Follow-up Questions Guidance

  • Airlines own the booking record and may not share changes with you. How does your solution work if a major airline refuses to integrate?
  • How would you show that fixing a post-booking problem brings travelers back to Google Flights for their next search?
  • Your worst pain point is disruptions, but fare-drop alerts after purchase are far cheaper to build. How do you decide what ships first?