Launch plan for a slower, non-urgent delivery tier in Swiggy Instamart

Quick Overview

A product launch question about adding an opt-in, slower no rush delivery option to Swiggy Instamart's quick-commerce grocery service. It tests reasoning about last-mile delivery economics and order batching, target customers, checkout and dark-store design, a store-level pilot experiment, and success metrics with guardrails.

Launch plan for a slower, non-urgent delivery tier in Swiggy Instamart

Company: Swiggy

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager on Instamart, Swiggy's quick-commerce service that delivers groceries and household essentials within minutes from small neighborhood warehouses (dark stores). The team wants to add a "no rush" delivery option, which a customer would pick when the order does not need to arrive right away. Explain how you would take this from idea to launch: why it is worth building, which customers and orders it is meant for, how it should work for customers and for store and delivery operations, how you would roll it out, and how you would decide whether the launch succeeded. ```hint Follow what waiting unlocks Ask what a dark store and its riders could do differently if some orders were allowed to wait, and what a customer would need in return for giving up speed. Both answers shape the goal and the design. ``` ### Clarifying Questions - What does "no rush" promise: a wider window later the same day, a delivery slot the customer chooses, or next-day delivery? - Which goal matters most: lowering delivery cost per order, absorbing peak-hour demand, or winning larger planned grocery baskets that customers currently buy elsewhere? - Does the customer get something for waiting, such as a lower or waived delivery fee, a discount or credits, and how should that work for members of Swiggy's paid membership who may already get free delivery? - Is the first launch limited to certain cities or stores, and are any categories, such as frozen or chilled items, excluded? ### What a Strong Answer Covers - A reason for the option grounded in quick-commerce delivery economics, and one explicit launch goal. - The customers and order types for which waiting is acceptable, and the ones for which it is not. - The customer flow (the choice at checkout, the promised window, the incentive, tracking) and the dark-store and dispatch changes that make the promise reliable. - A staged rollout with an experiment design that handles store-level batching effects, plus clear go/no-go criteria. - A success metric with guardrails for cannibalized fast orders, on-time delivery within the window, product freshness and rider earnings. ### Follow-up Questions - After the pilot, most no-rush orders come from customers who used to pay for standard delivery, and their order frequency has not changed. Was the launch a success? - How would you size the incentive for waiting, and what evidence would make you change it? - Customers who chose no rush complain that frozen items arrive partly thawed. What do you change?

Overview: A product launch question about adding an opt-in, slower no rush delivery option to Swiggy Instamart's quick-commerce grocery service. It tests reasoning about last-mile delivery economics and order batching, target customers, checkout and dark-store design, a store-level pilot experiment, and success metrics with guardrails.

Swiggy logo
Swiggy
Nov 8, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager on Instamart, Swiggy's quick-commerce service that delivers groceries and household essentials within minutes from small neighborhood warehouses (dark stores). The team wants to add a "no rush" delivery option, which a customer would pick when the order does not need to arrive right away. Explain how you would take this from idea to launch: why it is worth building, which customers and orders it is meant for, how it should work for customers and for store and delivery operations, how you would roll it out, and how you would decide whether the launch succeeded.

Clarifying Questions Guidance

  • What does "no rush" promise: a wider window later the same day, a delivery slot the customer chooses, or next-day delivery?
  • Which goal matters most: lowering delivery cost per order, absorbing peak-hour demand, or winning larger planned grocery baskets that customers currently buy elsewhere?
  • Does the customer get something for waiting, such as a lower or waived delivery fee, a discount or credits, and how should that work for members of Swiggy's paid membership who may already get free delivery?
  • Is the first launch limited to certain cities or stores, and are any categories, such as frozen or chilled items, excluded?

What a Strong Answer Covers Guidance

  • A reason for the option grounded in quick-commerce delivery economics, and one explicit launch goal.
  • The customers and order types for which waiting is acceptable, and the ones for which it is not.
  • The customer flow (the choice at checkout, the promised window, the incentive, tracking) and the dark-store and dispatch changes that make the promise reliable.
  • A staged rollout with an experiment design that handles store-level batching effects, plus clear go/no-go criteria.
  • A success metric with guardrails for cannibalized fast orders, on-time delivery within the window, product freshness and rider earnings.

Follow-up Questions Guidance

  • After the pilot, most no-rush orders come from customers who used to pay for standard delivery, and their order frequency has not changed. Was the launch a success?
  • How would you size the incentive for waiting, and what evidence would make you change it?
  • Customers who chose no rush complain that frozen items arrive partly thawed. What do you change?