Every strong career story starts messier than it looks from the outside: uncertain options, imperfect experience, and a few decisions made before everything felt ready. Product Case Questions: How to Ace PM Interviews helps you make those decisions with more confidence.
Pro tip: The best PM candidates don't just design features — they think about trade-offs. A candidate who can say "Here's what we'd gain, here's what we'd lose, and here's why the trade-off is worth it" instantly separates themselves from candidates who only pitch the upside.
Types of Product Case Questions
There are four main types of product case questions. Product Design questions ask you to design a product for a specific audience or feature. Product Improvement questions focus on how you would improve an existing product. Product Strategy questions explore whether a company should enter a new market or what the long-term product strategy should be. Estimation and Metrics questions ask you to estimate quantities or determine which metrics to track.
Type 1: Product Design Questions
Prompt example: "Design a grocery delivery app for elderly users in India."
Step 1: Clarify and Understand
Ask questions to narrow the scope, such as whether you are designing a full app or a specific feature, what the core problem is you are solving for elderly users, whether there are any technical or resource constraints, and whether the elderly users are shopping for themselves or with help.
Step 2: Define User Persona and Pain Points
Create a specific user persona. For example, Shanti Devi is a 68-year-old retired school teacher in Pune who lives with her husband. Her children are in the US. She uses a smartphone but finds most apps confusing. She speaks Hindi and Marathi with limited English, her vision is declining, and her fingers are less dexterous. Her pain points include small fonts and buttons that are hard to read and tap, English-only interfaces that are inaccessible, complex navigation with too many options, confusing payment flows, and a fear of making mistakes and losing money.
Step 3: Define Goals and Success Metrics
The user goal is to order groceries in under five minutes without help. The business goal is to increase adoption among the 60-plus age group by 40% in six months. Success metrics include task completion rate for elderly users, time to complete the first order, weekly active users in the 60-plus segment, and customer support calls from elderly users.
Step 4: Design the Solution
The first feature is a Simplified Interface with extra-large fonts of a minimum of 18sp with high contrast, Hindi and regional language support, large tap targets of a minimum of 60dp, voice search and voice navigation in Hindi, and a persistent Help button on every screen. The second feature is Guided Shopping with a curated Common Grocery List based on Indian households, an option to reorder previous orders in one tap, a weekly subscription for staples like rice, dal, oil, and milk, and visual icons alongside text such as a photo of toor dal rather than just text. The third feature is Trust and Safety with COD as the default payment option, a "Call me before substituting any item" toggle, order tracking with simple status messages in Hindi, and family sharing that lets children manage payments from abroad. The fourth feature is Simplified Checkout with a three-step process going from cart to address to confirm, no surge pricing or hidden fees, delivery window selection with a large calendar, and a confirmation call before dispatch.
Step 5: Prioritize and Build Roadmap
Phase 1, the MVP, includes large fonts, Hindi language, COD, a curated list, and voice search. Phase 2 includes family sharing, weekly subscriptions, and regional languages. Phase 3 includes AI-powered reorder predictions and video call support.
Step 6: Validate and Iterate
Conduct usability testing with 20 elderly users, run A/B tests comparing the simplified flow versus the regular flow, and iterate based on task completion rates and user feedback.
Type 2: Product Improvement Questions
Prompt example: "How would you improve WhatsApp for the Indian market?"
Step 1: Understand Current State
WhatsApp has over 500 million users in India. Its primary uses include personal chat, family groups, and business communication. Key competitors include Telegram, Signal, and ShareChat. Monetization comes from WhatsApp Business and payments through UPI.
Step 2: Identify Opportunities
Use a data-driven or hypothesis-driven approach. Payment adoption is low despite UPI integration because most Indians use PhonePe or Google Pay. Business discovery is poor since finding local businesses on WhatsApp is hard. Content sharing is messy with no way to organize shared photos and files in groups. Privacy concerns are significant as many elderly users fall for scams.
Step 3: Pick One Idea and Deep Dive
Consider a Business Discovery and Chat-to-Order feature. This would include a searchable business directory integrated with WhatsApp Business, the ability to view menus and catalogs within WhatsApp without leaving the chat, ordering directly via chat with payment integration, and order tracking within the chat thread. The trade-offs include a seamless experience with no app switching that drives payments usage, weighed against cluttering the chat interface, privacy concerns with sharing location and browsing data, and potential spam increase.
Type 3: Product Strategy Questions
Prompt example: "Should Swiggy enter the quick commerce space with 10-minute delivery?"
Framework: Market + Customer + Company + Competition
1. Market Analysis
Quick commerce in India is a Rs 5,000 crore market in 2024, growing at 40% CAGR and expected to reach Rs 50,000 crore by 2028. Key players include Zepto, Blinkit, and Instamart. The average order value is Rs 300 to 500 compared to Rs 200 to 300 for food delivery.
2. Customer Analysis
The target customers are urban professionals aged 22 to 40 in the top 10 cities. Their need is instant delivery of daily essentials like milk, bread, eggs, snacks, and toiletries. They have a willingness to pay a premium of Rs 10 to 20 over normal prices. Their frequency is three to four times per week for quick commerce versus one to two times for food delivery.
3. Company Analysis
Swiggy's strengths include an existing delivery network of two lakh plus delivery partners, restaurant relationships, a strong tech platform, and brand trust. Its weaknesses include a different supply chain requiring dark stores versus restaurant pickup, margin pressure, and distraction from the core business. Opportunities include cross-selling between food and groceries, higher order frequency, and better delivery partner utilization.
4. Competition Analysis
Zepto is the first-mover with high brand recall among Gen Z and strong unit economics in top cities. Blinkit, owned by Zomato, already operates dark stores with deep pockets from Zomato. Instamart, Swiggy's own effort, already has limited presence but is not dominant.
Recommendation
The go-to-market strategy should focus on five cities where Swiggy has the highest density, convert high-frequency food delivery users to quick commerce, start with 500 essential items per store rather than 5,000, use the existing delivery fleet during non-peak food hours, and target 15-minute delivery as a differentiation from the 10-minute claims. Expected outcomes include revenue per user increasing 40% from food plus grocery, delivery partner utilization improving 25%, and a market share target of 15% in two years.
Type 4: Estimation and Metrics Questions
Estimation Example
"How many orders does Zomato process in Delhi per day?" Start with the population of Delhi at about 2 crore. Assume the tech-savvy population aged 15 to 50 is about 60%, or 1.2 crore. Of those, about 30% use food delivery, giving 36 lakh users. Assume an average of 3 orders per user per month, giving 1.08 crore monthly orders. Divide by 30 for approximately 3.6 lakh daily orders. For a sanity check, Delhi has about 40,000 restaurants on Zomato, so 3.6 lakh divided by 40,000 equals 9 orders per restaurant per day, which is reasonable.
Metrics Framework Example
"How would you measure the success of Instagram Reels in India?" The North Star metric is time spent watching Reels per daily active user. Segmented metrics include adoption measured by the percentage of DAU who view or create Reels and the Reels creation rate; engagement measured by daily Reels views per user, completion rate, and likes, comments, and shares; retention measured by D1, D7, and D30 retention of Reels users and churn rate; monetization measured by ad revenue from Reels, creator earnings, and brand deal volume; and quality measured by content report rate, copyright claims, and unique creators count. Success criteria for India include time spent on Reels exceeding time spent on Feed within six months, Reels creators growing from 5 lakh to 50 lakh in one year, and Reels ad revenue reaching Rs 1,000 crore annually within two years.
Common Frameworks for PM Cases
The AARM Framework covers Acquisition, Activation, Retention, and Monetization. The HEART Framework from Google covers Happiness measured by NPS and surveys, Engagement measured by frequency and intensity of usage, Adoption measured by new user acquisition, Retention measured by returning users, and Task Success measured by whether users can complete core tasks. The RICE Prioritization framework evaluates Reach, Impact, Confidence, and Effort.
Practice Questions to Try
Design a UPI payments experience for international students coming to India. How would you improve the first-time user experience for CRED? Should Zomato launch a cloud kitchen brand and why or why not? How would you measure the success of Ola's electric vehicle fleet? Design a feature to reduce fake reviews on Amazon India. How would you improve the matrimony app experience for Gen Z? Should PhonePe launch a credit card? How many people use Uber in Bangalore during peak hours?
Common Mistakes in Product Case Questions
Not defining the user means jumping to solutions without understanding who you are designing for. Every feature should be justified by a specific user need. Forgetting business impact means a great user experience that does not make money is not a complete answer, so always tie features to business metrics. Ignoring trade-offs is problematic since no decision is all positive, and acknowledging trade-offs shows mature product thinking. Missing technical feasibility means your solution might be brilliant but impossible to build, so consider engineering effort, dependencies, and constraints. Not prioritizing means presenting everything as equally important, so show you can prioritize by impact and effort.
Conclusion
Product case questions test your ability to think like a product manager, being user-centric, data-informed, business-aware, and action-oriented. The key takeaways are to clarify before solving by understanding the user, the problem, and the goal; start with the user since every feature should solve a real user problem; think in trade-offs by showing awareness of what you are giving up; connect to metrics by defining how you will know if you have succeeded; and prioritize ruthlessly since not everything can be built at once.
Want more PM interview prep? Check out our complete product manager interview guide and behavioral interview techniques.
Your Move
- Record three answers using the STAR method: situation, task, action, result.
- Replay each answer and check whether it is specific, concise, and tied to the role you want.
- Rewrite the weakest answer, then practice it once more without reading notes.
