Strategy question
Should Amazon Pay be kept as a standalone app separate from Amazon shopping app? If yes, why? If no, why?
- Razorpay
- Strategy
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests platform-architecture strategy reasoning: can you weigh discoverability and focus of a standalone app against the convenience and cross-sell power of embedding within the main app.
How to approach it
- Clarify the trade-off: a standalone Amazon Pay app offers focused access for payment use cases but loses the built-in distribution of Amazon's shopping app.
- Consider arguments for standalone: a dedicated app can move faster on payment features and appeal to non-shoppers who just want a payment tool.
- Consider arguments against standalone: most usage likely originates within Amazon's own ecosystem, and a separate app adds friction against entrenched competitors like Google Pay or PhonePe.
- Make a recommendation: keep it embedded for most use cases, checkout and linked bill pay, and consider a lightweight standalone app only for an offline QR-payment use case.
- Address the competitive reality: standalone UPI apps already dominate offline payments with strong network effects, so a late entry faces a steep uphill battle.
- Define success as Amazon Pay transaction volume and attach rate to Amazon purchases, best served by staying embedded.
What a strong answer includes
- Weighs both sides explicitly, focus of standalone versus distribution advantage of embedding, rather than an unsupported one-line answer.
- Identifies the real competitive dynamic in offline payments, entrenched apps with network effects, as the deciding factor against a standalone push.
- Makes a clear recommendation, stay embedded but consider a narrow experiment, rather than listing pros and cons with no conclusion.
- Picks metrics tied to the actual question, attach rate versus offline payment volume, depending on the path chosen.
Common mistakes
- Giving pros and cons with no actual recommendation, missing the core ask of the question.
- Ignoring the competitive reality of the payments market the question is implicitly grounded in (strong existing standalone payment apps).
- Not considering that most Amazon Pay value likely comes from checkout convenience, which requires being embedded, not standalone.
Likely follow-up questions
- What would change your recommendation if Amazon Pay's offline/QR usage grew significantly?
- How would you test demand for a standalone app before committing to build it?
- How would you measure cannibalization if a standalone app pulled usage away from the embedded experience?
More strategy questions
- You are a PM at Uber and you have to evaluate whether to add "Cash" as a method of payment. How would you decide?Razorpay · Strategy · Hard
- Google Keep is a free product to save, share notes etc. How would you make it a subscription product & monetize it?Google · Strategy · Hard
- How would you launch (roll out) Amazon Go?Amazon · Strategy · Hard
- With an unlimited network bandwidth what would you build?Google · Strategy · Hard
- Strategize and implement omni-channel initiatives to improve customer LTV for Walmart.Shopify · Strategy · Hard
- How would you decide between showing more ads on the Facebook Newsfeed vs showing a "People you may know" recommendation widget?Meta · Strategy · Hard
More questions from Razorpay
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop