💡 See great PM thinking in action — then do it yourself

PM Product Sense Examples
(2026 Edition)

10 real product sense questions with sample answers. See the structure, the user-first thinking, and the specific metrics that separate strong answers from generic ones.

Practice Similar Questions Daily — Free →

Q1. How would you improve WhatsApp for small business owners in India?

Structure: Clarify → Users → Pain → Solutions → Metrics

**Clarify:** Targeting kiranas and solo entrepreneurs using WhatsApp for order-taking (1M+ merchants). **User:** 32-year-old kirana owner taking 20 orders/day via text. **Pain:** Orders get lost in chat, no inventory sync, payment tracking separate. **Solution:** Structured order cards inside chat — each order becomes a trackable object with items, price, payment status. **Metric:** % of WhatsApp Business users using structured orders, repeat merchant retention 30d.

Q2. Improve Zomato for users who order once a month.

Structure: Segment insight → Why they lapse → Re-engagement → Metric

**Insight:** Monthly users aren't habitual — they order for occasions. **Why they lapse:** High decision cost each time ('what do I want today?'). **Solution:** 'Occasion-based' discovery — 'Weekend brunch' or 'Office lunch' curated menus. Reduces decision cost. **Metric:** Order frequency for monthly users — move from 1 to 2 orders/month. Guardrail: not hurting heavy users.

Q3. Design a product for gig workers to manage their finances.

Structure: User research → Top pain → Product framing → Success

**User:** Delivery rider earning ₹25–40K/month with variable income. **Top pain:** Cash flow — bills come predictably, income doesn't. **Solution:** A 'smooth salary' product that advances next-day earnings based on confirmed orders, automatic savings buffer built in. **Success:** % of gig workers using advance weekly, reduction in payday-loan usage among active users.

Q4. How would you redesign Razorpay's onboarding for a new merchant?

Structure: Current state → Drop-off points → Redesign → Metric

**Current:** 12-step KYC + integration flow, ~40% completion. **Drop-off:** Integration (coding required) is the biggest barrier. **Redesign:** Two-track onboarding — 'Generate payment link' track (no-code, 3 steps, instant) vs 'Full integration' track (for devs). Lets merchants transact before fully integrating. **Metric:** Merchant activation rate (first transaction within 7 days) from 40% to 65%.

Q5. Improve Instagram Reels discovery for users who follow <50 accounts.

Structure: Problem → Why today&apos;s algo fails → Fix → Metric

**Problem:** New/light users see repetitive content because following graph is sparse. **Why it fails:** Algorithm relies heavily on follow-graph signals that don&apos;t exist. **Fix:** For users with &lt;50 follows, weight Reels recommendations toward &apos;explore taste&apos; seed — 5 quick onboarding questions about interests, then explore-heavy feed for first 4 weeks. **Metric:** Time-spent and return-rate for users with &lt;50 follows.

Q6. Design a product to help students from non-IIT/IIM backgrounds crack PM interviews.

Structure: User → Why they struggle → Product → Metric

**User:** Tier-2 engineering student applying to PM roles, no APM program filter. **Why they struggle:** Lack of structured prep, no peer group, no AI feedback. **Product:** Daily 2-minute PM scenarios with AI feedback, streak mechanics for habit, India-company-specific question banks (Razorpay, Flipkart, etc.). **Metric:** % of users who land at least 1 PM interview within 6 months of active use.

Q7. How would you design payment reminders for Paytm that don&apos;t feel spammy?

Structure: User insight → Current failure → Design → Metric

**User insight:** Users ignore standard reminders; they notice specific, useful ones. **Current failure:** Generic &apos;pay your bill&apos; notifications at wrong times. **Design:** Context-aware reminders — &apos;Your DTH bill is due tomorrow. Your balance is ₹X. Tap to pay in 5 seconds.&apos; Include balance context, estimated time, one-tap action. **Metric:** Click-through rate on reminders + NPS of users receiving them (guardrail).

Q8. Redesign the Flipkart search result page for first-time buyers in Tier-3 cities.

Structure: User → Barrier → Simplification → Metric

**User:** First-time online shopper in Jabalpur, low digital literacy, doesn&apos;t trust product photos. **Barrier:** Too many options, no clear pricing, trust issues. **Redesign:** Top 3 options only, bigger photos, one-line trust signals (&apos;5-star seller&apos;, &apos;COD available&apos;, &apos;return in 7 days&apos;), vernacular language toggle. **Metric:** Search-to-purchase conversion for first-time Tier-3 users from X% to Y%.

Q9. How would you help CRED grow usage among its existing premium members?

Structure: Segment → What they don&apos;t use → Why → Product

**Segment:** CRED members paying credit card bills but not using other features. **What they don&apos;t use:** CRED Mint (investing), CRED Pay (merchants), CRED Store. **Why:** Habit formed around bills, no trigger to try adjacent features. **Product:** &apos;Earn extra coins&apos; weekly quest that introduces one adjacent feature per week (week 1: try Mint, week 2: try Pay). **Metric:** Feature breadth — % of members using 2+ CRED features per month, up from X to Y.

Q10. Design a feature for Myntra to reduce return rates in women&apos;s fashion.

Structure: Return reasons → Biggest bucket → Solution → Metric

**Return reasons (research):** 50% size/fit, 20% colour didn&apos;t match, 15% material, 15% &apos;changed mind.&apos; **Biggest bucket:** Size/fit. **Solution:** &apos;Fit predictor&apos; — users enter 2–3 reference items they already own (not measurements), model recommends size based on brand fit patterns. **Metric:** Size-related return rate from X% to Y%, with guardrail: no drop in purchase rate among new users.

FAQ

How should PMs study product sense examples?

Don&apos;t memorise them. Study the structure: how did they clarify? How did they define the user? How did they move from problem to solution? Then try the same question yourself, without looking at the sample, record yourself answering it, and compare. Your structure will be different — that&apos;s fine. What matters is the discipline of moving user → problem → solution → metric, not matching someone else&apos;s words.

Should sample answers be memorised for PM interviews?

No — verbatim memorisation backfires. Interviewers ask follow-ups that break memorised answers. Instead, internalise the thinking structure. The best PMs can structure any product sense question on the fly because they&apos;ve done it 50+ times in practice — not because they&apos;ve memorised 10 templates.

Turn Examples Into Instinct

Daily PM scenarios with AI feedback — practice until the structure is automatic.

Start Free Trial →