You are a Product Manager at Facebook. Friend requests have suddenly dropped by 10% overnight, and the company wants to understand why and how to respond.

⸻

Initial Clarification & Scoping:

The candidate starts by narrowing down the problem:

• The drop is sudden and happened overnight.

• It’s not seasonal, unexpected, and shows no variance in historical trends.

• The drop is happening in the US and across all platforms (iOS, Android, web).

• It is specific to friend requests, not other features.

⸻

Root Cause Exploration Approach:

The candidate categorizes investigation into four buckets: internal, contextual, user behavior, and external factors.

1. Internal Checks:

• System issues: No known degradation or system outages.

• Product/UI changes: None that deprioritized or altered friend requests.

• Data quality: Trustworthy, no anomalies reported.

2. External Factors:

• User behavior: No sudden change observed.

• Competitive landscape: TikTok is evolving to become more social, which could pull user attention away from Facebook’s friend request flow.

• Regulatory changes: A new European privacy law went into effect overnight, blocking Facebook’s ability to operate in a European country—this indirectly impacts friend connections with/from the US.

• Marketing changes: Facebook has reduced marketing budget, possibly weakening user re-engagement or perception during a critical period.

⸻

Hypothesis:

The candidate synthesizes the situation into three likely contributing factors:

1. Regulatory constraints in Europe limiting cross-border friend requests.

2. TikTok’s shift to social features potentially capturing user attention.

3. Reduced marketing efforts during a sensitive time, leading to reduced visibility and engagement.

⸻

Next Steps as PM:

• Collaborate with privacy/legal teams to fully understand the new law and identify at what point in the user flow it breaks compliance.

• Ideate alternative solutions, such as UI changes or consent-based flows, to regain compliance and re-enable the friend request feature in the affected region.

• Test new designs to evaluate effectiveness.

• Monitor competitor features and user adoption trends to stay proactive.

• Evaluate the need to increase marketing efforts to offset user loss and rebuild trust or awareness.

⸻

Conclusion:

The candidate demonstrates a structured, methodical approach: clarifying the scope, performing a segmented root cause analysis, forming hypotheses from internal and external signals, and proposing practical next steps for mitigation and product iteration.

Flipkart observed a ~15% decline in “cart additions” (users adding items to their cart) over the last three days, primarily on the mobile app.

⸻

Diagnostic Approach by Candidate:

1. Clarification of Metrics:

• Ensured clear definition of “cart additions.”

• Confirmed the issue is specific to the mobile app, not the website.

2. Initial Checks:

• Analytics tools were functioning normally—no logging issues.

• Competition, campaigns, and sales events didn’t indicate any correlation.

• No noticeable decline among specific user segments or locations.

3. App-Specific Investigation:

• Inquired about recent app updates. Flipkart had indeed pushed major updates on both Android and iOS, especially focused on improving the checkout flow.

• Issue was observed only on Android, not iOS.

4. Bug Reports:

• Post-update, there was a spike in bug reports, particularly related to payment and checkout issues.

5. User Journey Deep Dive:

• Hypothesized that the issue could be in the transition from viewing a product to adding it to the cart.

• Explored visibility and functionality of the “Add to Cart” button on the product listing pages.

• Suggested checking event logging to trace the user action flow—whether users were clicking “Add to Cart” and if the event was successfully registering.

6. Key Insight:

• Data showed no cart additions on a specific Android app version, strongly suggesting the bug was introduced in that release.

• Candidate concluded the likely issue lies with the Add to Cart functionality being broken or not triggering the backend event correctly.

⸻

Resolution Direction:

Candidate recommended deep event flow analysis on the Android app version to confirm where the “Add to Cart” interaction is breaking. The Interviewer confirmed this diagnosis as accurate.

⸻

Takeaway:

A structured approach—starting from metric definition, segmentation, external/internal changes, and finally drilling into the app flow—helped accurately identify that a recent Android app update likely broke the cart addition functionality.

⸻

Let me know if you want this turned into a carousel or case study format.

A grocery e-commerce app in India saw a 25% drop in sales starting last week. A candidate is asked to identify the potential reason.

Approach:

The candidate takes a structured problem-solving approach—asking clarifying questions, distinguishing between external and internal factors, and avoiding premature conclusions.

⸻

External Factors (Ruled Out):

• No new competitors

• No major sales/discounts from others

• No supply chain disruptions (e.g., driver strikes)

• No pattern across geographies or demographics

⸻

Internal Factors (Investigated Deeply):

• Data Collection Tool: Verified and working fine

• Platform Impact: Issue present only on Android app

• Uninstalls: No spike in app uninstalls

• App Update: Recent update only on Android

• Cart Functionality: “Add to Cart” and cart viewing work fine

• Checkout Bugs: Bugs found during payment stage

• Payment Methods: Digital methods fine

• Cash on Delivery (COD): Bugs reported during COD option usage

⸻

Root Cause Identified:

Bugs in the Cash on Delivery (COD) feature in the Android app update led to failed checkouts, resulting in 25% drop in sales.

⸻

Key Takeaways:

• Avoid jumping to conclusions; always dig deeper

• Structure your thinking: External → Internal

• Validate assumptions at every step

• Small product changes (like bugs in COD) can have massive business impact

• Referencing known case studies (like the “$300M button”) can demonstrate product thinking and real-world knowledge

⸻

#ProductManagement #CaseInterview #Ecommerce #UXDesign #MobileApp #GroceryApp #RootCauseAnalysis #ProblemSolving #ProductThinking #UserExperience #PMInterviews #IndiaEcommerce #ConversionOptimization #CashOnDelivery

Order cancellations on the Personal Care Online Retailer platform have increased by 20%. The platform allows cancellations within a 24-hour window, but this spike is specifically seen after the 24-hour mark—when products are prepared for shipping.

Key Observations & Clarifications:

• The spike in cancellations is sudden and occurred within the past week.

• It is specific to the app (not the website).

• Primarily affects makeup products, not skincare.

• Payment method (e.g., COD or EMI) is not a factor.

• No recent external changes (e.g., competition, pricing shifts, regulations, weather, social sentiment) were identified as causes.

• No experiments or changes in analytics tools have been introduced.

• The measurement method for cancellations has not changed.

Potential Internal Factors Explored:

1. New Feature Releases:

• Some new features were added recently.

• Among them, a virtual try-on tool was launched to help users choose the right product shade. However, it may inadvertently lead to cancellations if users realize post-purchase that they made the wrong selection.

2. Customer Feedback on Cancellation:

• Users mention “product not as expected” as the reason, though this may be a generic response rather than the actual issue.

3. Product Selection Errors:

• Potential confusion around shades or sizes despite the virtual try-on.

4. Sale Timing:

• It’s not linked to upcoming sales—there’s an ongoing sale, which is always pre-announced.

5. Changes in Address Entry:

• No significant recent updates to this process; not seen as a likely cause.

6. Reviews and Perception:

• While the platform is surfacing more positive reviews, customers may still be influenced by negative reviews elsewhere.

• Additionally, the removal of the authenticity badge image (replaced with a text label to improve page load speed) could be reducing trust in product authenticity.

Conclusion:

The likely drivers of the cancellation spike appear to be internal UX and trust-related issues, such as:

• Misuse or misinterpretation of the virtual try-on feature.

• Perceived loss of trust due to removal of visual authenticity cues.

• Discrepancy between what’s promoted (e.g., positive reviews) and what users find externally.

The next step would be to conduct a deep dive into user behavior post-virtual try-on, A/B test the reintroduction of visual authenticity indicators, and gather more qualitative feedback to validate these hypotheses.

⸻

Let me know if you’d like this adapted for a stakeholder deck or interview-ready framework (e.g., root cause analysis format).

Prompt: Build a theme park app for a new Disneyland-style park in Dubai. The key goals are virality, a great user experience, and monetization. You have 4 months to launch the app.

Initial Exploration:

The candidate begins by clarifying the park’s nature, constraints, and goals. With no budget constraints and a four-month timeline, the focus is set on creating an app that enhances user experience, addresses pain points, and encourages sharing.

User Personas:

1. Parents (Ramesh) – On a family vacation, prioritizing ease of experience and creating memories.

2. Teens (Arjun) – Thrill-seeker celebrating his birthday, social media savvy, ideal for generating virality.

3. Vendors (Alisha) – Operates a souvenir shop, interested in user footfall and engagement.

The candidate chooses to focus on tourists (Ramesh & Arjun) initially to optimize for experience and virality.

Pain Points Identified:

• Information overload and difficulty prioritizing rides.

• Long queues and poor time utilization.

• Inefficient navigation across the park.

• Lack of real-time ride details and recommendations.

• Missed moments due to limited photo access.

Proposed Solutions:

1. Smart Itinerary Planner – Personalized plans based on preferences, optimized for time and interest.

2. Real-Time Navigation & Discovery – Interactive map, wait times, and suggestions for nearby attractions and amenities.

3. In-App Ride Photography – Auto-captured ride photos, free samples, monetizable add-ons.

4. AR Experiences – Enhance exploration with AR facts, interactions with characters, and unique selfie spots.

5. Referral & Sharing Mechanism – Reward-based sharing (e.g., free rides, souvenirs) to drive virality.

Prioritization (RICE Framework):

• #2 (Navigation): Table stakes; essential for usability.

• #4 (AR Integration): Differentiating and delighting feature; boosts virality.

• #5 (Referral): Drives organic growth.

• #1 (Itinerary): Deprioritized to V2 based on initial user data.

• #3 (Photos): Valuable but complex; consider privacy and tech feasibility.

Launch Plan: Start with #2, #4, and #5. Collect user data for V2 features like itinerary planning.

Success Metrics:

• App downloads & account creations

• Engagement during trip window (T-3 to T+1 days)

• Number of shared photos on social media

• Net Promoter Score (NPS)

Conclusion: The candidate showcased a structured approach—clarifying goals, identifying personas, mapping user journeys, solving real problems with innovative features, and planning execution in a phased, data-driven manner.

⸻

Let me know if you’d like this adapted into a LinkedIn post or interview-ready format.

Interviewer: Design Google Maps for senior citizens.

Candidate: Considering rising life expectancy, should we focus on everyone over 60 or a narrower segment?

Interviewer: Let’s consider everyone over 60.

Candidate: Should we aim to increase engagement, adoption, or both?

Interviewer: Focus on engagement.

Candidate: Any constraints?

Interviewer: None.

Candidate: Should we focus on the app or web, and for which geography?

Interviewer: Mobile app for India.

Candidate: Great. Let’s aim to improve engagement for seniors using the Google Maps Android app. Most are aware of the app but may struggle with usability due to low tech-savviness. Let’s explore key user personas:

1. Ramesh (60) – Recently retired, launched a wholesale business, tech-aware, travels inter-state.

2. Chitra (65) – Lives in a tier-2 city, wants to move closer to family, uses YouTube and WhatsApp, digitally literate.

3. Vishnu (78) – Lives with family in a tier-3 city, rarely travels independently.

Candidate: I’ll prioritize personas like Chitra—independent seniors with frequent navigation needs. Let’s identify user pain points:

• Never used navigation apps; overwhelmed by screen and instructions.

• UI feels cluttered and hard to operate.

• Voice assistant speaks too fast or with unclear accent.

• Discomfort with traveling alone or during peak hours.

• Family discourages them from going out solo.

Proposed Solutions:

1. Simplified UI: Detect senior users via age or mode selection and show a cleaner, decluttered interface.

2. Voice Assistant Improvements: Let users slow down voice instructions, offer regional language options, and ensure clearer pronunciation.

3. AR/Visual Overlays: Show real-time turn indicators or color-coded markers to aid in navigation, especially in flyovers or busy intersections.

4. Contextual Alerts: Smart notifications based on habits (e.g., walk times, appointments) and time of app usage (e.g., morning = parks).

5. Personalized Exploration: Recommend nearby essential services (e.g., hospitals, parks, safe eateries), tailored to senior needs. Encourage family engagement through shared suggestions.

Prioritization (RICE Framework):

• High Priority:

• #1 (Simplified UI) and #2 (Voice assistant) – High impact, low effort, testable via prototypes.

• Medium Priority:

• #4 (Contextual alerts) – Valuable but needs behavior learning and testing.

• Lower Priority:

• #3 (AR overlays) – Innovative but dependent on hardware/internet and not essential for MVP.

• #5 (Exploration engine) – Start basic, build over time with personalization logic.

Success Metrics:

• Notification click-through rate.

• Weekly active users (WAU) using search/navigation.

• % enabling data sharing.

• Success rate in entering and reaching destinations.

• Participation in recommended activities or groups.

• 30-day retention rate.

Interviewer: Thank you.

Candidate: You’re welcome.

⸻

Would you like this adapted into a LinkedIn post or visual carousel as well?

Approach & Clarification:

The candidate began by seeking clarification on whether the audio product should integrate with a specific Meta app. The interviewer allowed flexibility, prompting the candidate to choose based on strategic reasoning.

Framework & Thought Process:

The candidate structured the response into four key phases:

1. Why build an audio product?

2. Who is the target audience?

3. What are the key user pain points?

4. What solutions can address these pain points?

1. Justification for an Audio Product:

The candidate highlighted the rapid growth of the audio market, citing a 50% increase in Spotify’s paid subscribers since March 2020. They noted that Meta’s strength in building social communities could be extended into the audio domain to foster deeper connections through shared listening experiences.

2. Target User Segments:

Two segmentation approaches were proposed:

• Demographics: Focus on teens and young adults (12–34), aligning with Meta’s key engagement targets.

• Content Type: Differentiate between music, spoken word (podcasts, audiobooks), and live radio. Special attention was given to the rise of podcast consumption.

The candidate chose to focus on young podcast listeners who actively consume 2+ hours of audio daily.

3. Identified Pain Points:

The candidate mapped pain points across the user journey (Discovery, Consumption, Post-Listening):

• Discovery: Lack of contextual and proactive audio recommendations.

• Consumption: Audio is a solitary, often boring experience leading to disengagement.

• Post-Listening: No easy way to share short, meaningful clips from content.

Top priority pain points were the isolating experience and lack of sharing options, both closely tied to Meta’s mission of building connections.

4. Proposed Solutions:

• Communal Listening: Similar to Meta’s “Watch Together” in Messenger, users can listen to audio in sync with friends/family during calls. This addresses isolation and fosters real-time shared experiences.

• Interactive Audio: Add engagement layers where users make choices affecting content progression (e.g., “choose what happens next”), and periodic questions to maintain attention—ideal for reducing boredom during long-form audio.

• Immersive Audio with Oculus: Leverage VR to enhance podcast/audiobook experiences, allowing users to feel present in the narrative (e.g., historical settings). This supports Meta’s broader metaverse vision.

Conclusion:

The candidate emphasized starting with communal listening as part of the MVP, inspired by OTT success in shared content experiences. This aligns strongly with Meta’s core value of connecting people through meaningful interactions.

Would you like this converted into a LinkedIn carousel or article?

Platform & Integration:

The candidate recommends integrating the product within the Meta ecosystem (e.g., Facebook) to leverage its massive user base.

Product Goal (Assumed):

To support gardening enthusiasts and align with Meta’s mission to build community and promote environmental consciousness.

Target User Segment:

Focused on Passionists — hobbyist gardeners who grow plants at home — rather than commercial users who are already knowledgeable.

Key User Pain Points Identified:

1. Lack of knowledge on suitable plants for specific weather and soil conditions.

2. Uncertainty about space requirements for plants.

3. Inability to visualize future plant growth.

4. Lack of watering knowledge (frequency and quantity).

5. Tendency to forget watering.

6. Difficulty identifying and treating plant diseases.

7. Desire to share their garden progress with friends and community.

Proposed Features (Solutions):

1. Input-based plant recommendations tailored to local weather and soil conditions.

2. Visual previews of plant growth and area coverage.

3. Smart watering recommendations based on climate data.

4. Watering reminders via push notifications.

5. AI/ML-based plant disease detection via photo uploads.

6. Social sharing features within Meta (e.g., image posts with likes/comments/shares).

Prioritization (MVP):

Start with addressing pain points 1–5 and 7 by building features 1–4 and 6. Disease detection (pain point 6, solution 5) is valuable but complex, and can be added later based on time and resources.

Success Metrics:

1. Number of unique users who try the feature.

2. Number of users submitting soil/weather info.

3. Number of shared garden images.

4. Engagement rate on shared posts (likes/comments/shares).

Design a consumer-focused feature within Google Pay to simplify and encourage credit card bill payments, with the long-term goal of increasing platform stickiness and eventual monetization. The scope is limited to India, where such services are prevalent.

User Personas:

1. Rohan (34) – A busy investment banker with multiple credit cards, often unaware of exact dues due to fragmented statements.

2. Preeti (28) – A dietitian and online shopper who uses EMI features but often overspends due to lack of financial visibility.

3. Naresh (50) – A financially responsible father who uses a credit card for big-ticket items and pays bills diligently.

Primary focus is on Rohan and Preeti, representing the younger, urban demographic who are frequent digital users but lack financial management tools.

User Pain Points:

• Difficulty tracking multiple due dates.

• Fragmented billing details (emails, statements).

• Lack of clear categorization or spend insights.

• Unawareness of hidden charges, interests, or fees.

• Insufficient motivation for timely, full payments.

• Accidental overspending due to lack of budgeting tools.

Proposed Solutions:

1. Card Registration: Easy card linking via scan feature; integrate with major banks and credit card networks.

2. Due Date Reminders: Notifications and banners within Google Pay (e.g., 3 days before due date), calendar integration.

3. Monthly Overview: Show total dues at month-start to aid planning.

4. Reward System: Post-payment rewards (Google services credits, etc.) to encourage usage.

5. High-Value Payments: Allow payments over ₹1 lakh.

6. Spending Insights: Visualize top transactions, spending categories, credit score insights, and spending alerts.

7. Full Payment Nudges: Show interest saved by full payments; disclose fees transparently.

8. Budgeting Tool: Let users set monthly limits, get spending alerts, and visualize progress via a “saving tree.”

Implementation Priorities (RICE Framework-based):

• Must-have (MVP): Features #1, #2, and #7 for core functionality.

• Differentiators: #3, #4, and #6 to offer personalization and insights.

• Version 2: Advanced budgeting (#5) and deeper data-driven insights.

Conclusion:

The strategy is to create a seamless, intuitive experience that reduces user friction and builds financial awareness. In parallel, technical integration with banks and card networks is crucial. The feature roadmap balances quick wins and long-term differentiation while keeping users engaged and informed.

⸻

Let me know if you’d like a version tailored for a resume, case study deck, or interview notes.

Understanding the Product:

The candidate starts by defining Google Docs as a cloud-based word processor within Google Workspace that allows users to write, edit, and collaborate on documents. They confirm their understanding with the interviewer before proceeding.

⸻

Approach & Framework:

The candidate outlines a structured problem-solving approach:

1. Define user segments.

2. Establish a business goal.

3. Focus on a high-potential user journey.

4. Identify pain points.

5. Propose solutions with trade-offs.

6. Conclude with a recommendation.

⸻

User Segments:

• Consumers: Students, teachers, freelancers, kids, elderly, etc.

• Businesses: Small, medium, and large enterprises.

The candidate decides to focus on Small and Medium Businesses (SMBs), recognizing Google’s strategic push in the enterprise market and strong penetration in the SMB space via other tools like Google My Business.

⸻

Business Goal:

Increase enterprise market share, specifically within the SMB segment.

Key Metrics:

• Number of paying customers

• Market share (%)

⸻

Pain Points (SMBs):

• Need seamless document collaboration and review.

• Require approvals/signatures for process completion.

• Must store and access approved documents reliably.

• Require strong security and protection from cyber threats.

• Face challenges sending documents to external entities (physically or digitally).

Pain Points (Clients of SMBs):

• Verifying identity is cumbersome.

• Struggle with unfamiliar and complex systems.

• Have low trust in digital tools.

• Frequently re-enter the same information for different forms.

⸻

Opportunity Area:

The candidate identifies a high-impact, underserved use case—document-intensive procedures involving third parties (e.g., real estate, immigration, loan applications). These use cases are complex, fragmented, and lack tailored support from competitors like Microsoft or Dropbox.

⸻

Proposed Solutions:

1. Electronic ID using Google Accounts:

Certifies user identity for document processing and approvals.

2. Integration with third-party systems (e.g., immigration, financial services):

Allows seamless submission of Docs-based forms directly into official platforms.

3. Centralized Document Vault:

Helps users store and reuse procedural documents securely across different applications.

⸻

Recommendation:

Prioritize the Cyber ID solution—an identity certification layer built into Google Accounts and integrated into Docs. This would:

• Enable official document collaboration and approvals.

• Target SMBs handling legal/official processes.

• Differentiate Google Docs in a competitive market.

• Leverage Google’s expertise in security and identity.

Business Impact:

Offered via the Google Workspace Business Plan, this feature would drive SMB adoption and boost enterprise market share.

⸻

Conclusion:

The candidate delivers a strategic and structured recommendation to enhance Google Docs, aligned with Google’s broader goals, focusing on solving critical user pain points to gain competitive advantage in the SMB market.