##### Question What would you do if Amazon asked you to: Launch a table-booking app? Launch a flower-delivery service? Develop an advertising platform? For each scenario, discuss: Target customers and their jobs-to-be-done. Core value proposition and how it aligns with Amazon’s mission of customer obsession. Competitive landscape and Amazon assets you would leverage (Prime, Alexa, logistics, ads network, payments). Success metrics—both input (selection, conversion, latency, CSAT) and output (revenue, retention, NPS). MVP feature set, user flows, and technical architecture at a high level. Go-to-market and launch sequencing (geography, marketing, partnerships, pricing). Long-term roadmap: adjacent features, global expansion, and flywheel effects. Key risks, mitigations, and mechanisms for continuous improvement. ##### Hints Think backwards from the customer, use Working Backwards PR-FAQ if helpful. Show trade-offs between speed, cost, and customer experience. Anchor your answer in Amazon Leadership Principles such as Customer Obsession, Think Big, and Dive Deep.

Practice Amazon new-service launch cases for table booking, flower delivery, and advertising platforms. The solution covers target users, JTBD, MVP scope, architecture, metrics, GTM, risks, Working Backwards framing, and long-term flywheels.

How do I approach Product / Decision Making interview questions?

Product / Decision Making questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master product / decision making interviews.

What difficulty level is this interview question?

This is a hard difficulty Product / Decision Making question, commonly asked during Onsite rounds at Amazon.

What role is this question designed for?

This question is commonly asked for Product Manager candidates at Amazon during technical interviews.

Amazon New-Service Launch Cases | Amazon Interview Question

Amazon New-Service Launch Cases

You are asked to outline how Amazon could launch three distinct products: a restaurant table-booking app, a flower-delivery service, and an advertising platform. Use a structured launch framework for each case and explain how the ideas fit Amazon's assets and customer-obsession principles.

Constraints & Assumptions

Treat the three ideas as separate product cases, not one combined service.
Use Amazon assets only where they create customer or partner value.
Include target customers, jobs to be done, value proposition, MVP scope, metrics, GTM, architecture, risks, and roadmap.
Keep v1 launches narrow enough to test liquidity, quality, and economics.

Clarifying Questions to Ask

Should I prioritize one of the three products or give equal treatment to all?
Are these intended for Prime members, sellers, local businesses, advertisers, or broad consumers?
What geography, category, or launch market should be assumed?
Should the answer use Amazon's Working Backwards PR-FAQ format?

Part 1 - Reusable Launch Framework

Define a reusable structure for evaluating each new service.

What This Part Should Cover

Target customers, JTBD, value proposition, Amazon assets, competitive landscape, MVP, architecture, metrics, GTM, roadmap, and risks.
Input metrics and output metrics.
A mechanism for continuous improvement after launch.

Part 2 - Restaurant Table Booking

Design the table-booking product.

What This Part Should Cover

Diner and restaurant needs, real-time availability, booking, deposits or no-show controls, and restaurant portal.
Marketplace liquidity, city-by-city launch, partner integrations, and Prime or Alexa use cases where useful.
Metrics such as active restaurants, availability coverage, search-to-book conversion, seated diners, no-show rate, and retention.

Part 3 - Flower Delivery

Design the flower-delivery product.

What This Part Should Cover

Sender and florist needs, occasion-based shopping, freshness, delivery windows, tracking, substitutions, and proof of delivery.
Logistics model, partner portal, seasonal demand, quality guarantees, and fulfillment risk.
Metrics such as zip coverage, on-time delivery, refund rate, repeat rate, contribution margin, and NPS.

Part 4 - Advertising Platform

Design the advertising platform.

What This Part Should Cover

Advertiser segments, shopper experience, sponsored placements, targeting, bidding, measurement, and brand safety.
Guardrails around ad load, relevance, trust, incrementality, and cannibalization.
Metrics such as active advertisers, CTR, CVR, ROAS, ACoS, ad revenue, shopper satisfaction, and organic impact.

What a Strong Answer Covers

Service-specific reasoning, not one generic launch answer.
Practical MVPs and phased rollout plans.
Metrics and guardrails that protect customer trust.
Clear discussion of risks, mitigations, and flywheel effects.

Follow-up Questions

Which of the three products would you launch first?
What is the riskiest marketplace cold-start problem?
How would you prevent flower-delivery quality failures during holidays?
How would you prove ad sales are incremental?
What Amazon asset would you intentionally avoid using?

Amazon New-Service Launch Cases

Constraints & Assumptions

Treat the three ideas as separate product cases, not one combined service.
Use Amazon assets only where they create customer or partner value.
Include target customers, jobs to be done, value proposition, MVP scope, metrics, GTM, architecture, risks, and roadmap.
Keep v1 launches narrow enough to test liquidity, quality, and economics.

Clarifying Questions to Ask

Should I prioritize one of the three products or give equal treatment to all?
Are these intended for Prime members, sellers, local businesses, advertisers, or broad consumers?
What geography, category, or launch market should be assumed?
Should the answer use Amazon's Working Backwards PR-FAQ format?

Part 1 - Reusable Launch Framework

Define a reusable structure for evaluating each new service.

What This Part Should Cover

Target customers, JTBD, value proposition, Amazon assets, competitive landscape, MVP, architecture, metrics, GTM, roadmap, and risks.
Input metrics and output metrics.
A mechanism for continuous improvement after launch.

Part 2 - Restaurant Table Booking

Design the table-booking product.

What This Part Should Cover

Diner and restaurant needs, real-time availability, booking, deposits or no-show controls, and restaurant portal.
Marketplace liquidity, city-by-city launch, partner integrations, and Prime or Alexa use cases where useful.
Metrics such as active restaurants, availability coverage, search-to-book conversion, seated diners, no-show rate, and retention.

Part 3 - Flower Delivery

Design the flower-delivery product.

What This Part Should Cover

Sender and florist needs, occasion-based shopping, freshness, delivery windows, tracking, substitutions, and proof of delivery.
Logistics model, partner portal, seasonal demand, quality guarantees, and fulfillment risk.
Metrics such as zip coverage, on-time delivery, refund rate, repeat rate, contribution margin, and NPS.

Part 4 - Advertising Platform

Design the advertising platform.

What This Part Should Cover

Advertiser segments, shopper experience, sponsored placements, targeting, bidding, measurement, and brand safety.
Guardrails around ad load, relevance, trust, incrementality, and cannibalization.
Metrics such as active advertisers, CTR, CVR, ROAS, ACoS, ad revenue, shopper satisfaction, and organic impact.

What a Strong Answer Covers

Service-specific reasoning, not one generic launch answer.
Practical MVPs and phased rollout plans.
Metrics and guardrails that protect customer trust.
Clear discussion of risks, mitigations, and flywheel effects.

Follow-up Questions

Which of the three products would you launch first?
What is the riskiest marketplace cold-start problem?
How would you prevent flower-delivery quality failures during holidays?
How would you prove ad sales are incremental?
What Amazon asset would you intentionally avoid using?

Amazon New-Service Launch Cases

Quick Overview

Amazon New-Service Launch Cases

Amazon New-Service Launch Cases

Constraints & Assumptions

Clarifying Questions to Ask

Part 1 - Reusable Launch Framework

What This Part Should Cover

Part 2 - Restaurant Table Booking

What This Part Should Cover

Part 3 - Flower Delivery

What This Part Should Cover

Part 4 - Advertising Platform

What This Part Should Cover

What a Strong Answer Covers

Follow-up Questions

Write your answer

Amazon New-Service Launch Cases

Quick Overview

Amazon New-Service Launch Cases

Amazon New-Service Launch Cases

Constraints & Assumptions

Clarifying Questions to Ask

Part 1 - Reusable Launch Framework

What This Part Should Cover

Part 2 - Restaurant Table Booking

What This Part Should Cover

Part 3 - Flower Delivery

What This Part Should Cover

Part 4 - Advertising Platform

What This Part Should Cover

What a Strong Answer Covers

Follow-up Questions

Write your answer