Quick Commerce Explained: Operations and Economics Behind 15-Minute Delivery

Quick Overview

A product manager interview question that asks how apps promising delivery in about 15 minutes actually work behind the scenes. It tests whether a candidate can connect the customer-facing promise to the operations, technology and economics that support it, and reason about where the model breaks.

Quick Commerce Explained: Operations and Economics Behind 15-Minute Delivery

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Some apps promise to get an order to the customer's door within about 15 minutes. Explain how an app like this works behind the scenes, from the moment a customer taps to order until the bag arrives. ```hint Spend the 15 minutes Split the promise into stages from checkout to doorstep and give each stage a time budget. Then ask what physical setup and which software decisions let every stage fit inside its budget. ``` ### Clarifying Questions - Are we talking about groceries and household essentials, or also restaurant meals, where cooking time is outside the app's control? - Should I cover only the customer-facing flow, or also the warehouses, delivery fleet and economics that keep the promise affordable? - Is there a market in mind? The model behaves very differently in a dense city with low labor costs than in a spread-out, high-wage one. ### What a Strong Answer Covers - A breakdown of the delivery promise into a time budget for each stage, from checkout to doorstep - The physical network behind the promise: where inventory sits, how far it travels, what is stocked and how it is picked - The software layer: serviceable areas and ETAs, demand forecasting and replenishment, picker and rider assignment - The unit economics and the order density they depend on, with the levers that improve them - Trade-offs and risks such as assortment versus speed, rider safety, stockouts and wastage, and local regulation ### Follow-up Questions - On a rainy evening, orders at one store double and riders are scarce. What should the system do, and what should customers see in the app? - Which three metrics would you put on a store manager's daily dashboard, and why those three? - Why might this model thrive in some cities and fail in others?

Overview: A product manager interview question that asks how apps promising delivery in about 15 minutes actually work behind the scenes. It tests whether a candidate can connect the customer-facing promise to the operations, technology and economics that support it, and reason about where the model breaks.

Google logo
Google
Aug 9, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Some apps promise to get an order to the customer's door within about 15 minutes. Explain how an app like this works behind the scenes, from the moment a customer taps to order until the bag arrives.

Clarifying Questions Guidance

  • Are we talking about groceries and household essentials, or also restaurant meals, where cooking time is outside the app's control?
  • Should I cover only the customer-facing flow, or also the warehouses, delivery fleet and economics that keep the promise affordable?
  • Is there a market in mind? The model behaves very differently in a dense city with low labor costs than in a spread-out, high-wage one.

What a Strong Answer Covers Guidance

  • A breakdown of the delivery promise into a time budget for each stage, from checkout to doorstep
  • The physical network behind the promise: where inventory sits, how far it travels, what is stocked and how it is picked
  • The software layer: serviceable areas and ETAs, demand forecasting and replenishment, picker and rider assignment
  • The unit economics and the order density they depend on, with the levers that improve them
  • Trade-offs and risks such as assortment versus speed, rider safety, stockouts and wastage, and local regulation

Follow-up Questions Guidance

  • On a rainy evening, orders at one store double and riders are scarce. What should the system do, and what should customers see in the app?
  • Which three metrics would you put on a store manager's daily dashboard, and why those three?
  • Why might this model thrive in some cities and fail in others?