Go or No-Go Decision on Building In-App Search for Paytm

Quick Overview

A product strategy interview question asking whether Paytm should add a search option to its consumer app. It tests whether you can tie a feature decision to real user jobs in a multi-service payments app, weigh alternatives, scope a first version and define success metrics with guardrails.

Go or No-Go Decision on Building In-App Search for Paytm

Company: Paytm

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Paytm is a large digital payments app in India whose consumer app offers many services alongside payments. Assume the app has no search option today. Should Paytm introduce one? Give a clear recommendation and the reasoning behind it. If you would build search, describe what the first version should help users find and how you would judge whether it worked. ```hint List what people would look for Before judging search, list what someone might type into it in this app (a service, a person or shop to pay, an old transaction) and compare each with how that person reaches it today. ``` ### Clarifying Questions - Is search meant to find the app's own services and features, people and merchants to pay, past transactions, or also offers and products from merchants? - Which business goal should the decision serve: more payments, more use of services beyond payments, or a simpler app for people who find it crowded? - Which users concern us most: frequent users who already know their way around, or newer and less confident users, including people who use the app in an Indian language other than English? ### What a Strong Answer Covers - The user jobs search would serve in a payments app with many services, rather than search as a generic feature. - The evidence you would gather before deciding, and the segments that would gain the most. - A clear build or do-not-build recommendation, the alternatives weighed, and what would change the decision. - A scoped first version that handles misspellings, mixed-language queries and the speed of the core payment flow. - Success metrics tied to completed tasks, with guardrails. ### Follow-up Questions - In the first month, most queries turn out to be names of contacts the user wants to pay. What would you change? - How would you handle queries typed in Hindi, in a mix of Hindi and English, or with phonetic spellings? - Leadership wants search results to include promoted merchant offers. How would you protect the user experience?

Overview: A product strategy interview question asking whether Paytm should add a search option to its consumer app. It tests whether you can tie a feature decision to real user jobs in a multi-service payments app, weigh alternatives, scope a first version and define success metrics with guardrails.

Paytm logo
Paytm
Mar 6, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Paytm is a large digital payments app in India whose consumer app offers many services alongside payments. Assume the app has no search option today. Should Paytm introduce one? Give a clear recommendation and the reasoning behind it. If you would build search, describe what the first version should help users find and how you would judge whether it worked.

Clarifying Questions Guidance

  • Is search meant to find the app's own services and features, people and merchants to pay, past transactions, or also offers and products from merchants?
  • Which business goal should the decision serve: more payments, more use of services beyond payments, or a simpler app for people who find it crowded?
  • Which users concern us most: frequent users who already know their way around, or newer and less confident users, including people who use the app in an Indian language other than English?

What a Strong Answer Covers Guidance

  • The user jobs search would serve in a payments app with many services, rather than search as a generic feature.
  • The evidence you would gather before deciding, and the segments that would gain the most.
  • A clear build or do-not-build recommendation, the alternatives weighed, and what would change the decision.
  • A scoped first version that handles misspellings, mixed-language queries and the speed of the core payment flow.
  • Success metrics tied to completed tasks, with guardrails.

Follow-up Questions Guidance

  • In the first month, most queries turn out to be names of contacts the user wants to pay. What would you change?
  • How would you handle queries typed in Hindi, in a mix of Hindi and English, or with phonetic spellings?
  • Leadership wants search results to include promoted merchant offers. How would you protect the user experience?