← Meesho Interview Insights

Meesho·Product Manager·Onsite - Product Sense / Strategy·Intermediate

Intermediate
Jun 2026

Summary

Interviewed for a PM role at Meesho and got hit with a classic product evaluation question framed around Facebook's early days. Pretty standard onsite product sense round, nothing too wild, but the question had more depth than it looked at first glance.

Questions Asked (1)

Q1

You're an early PM at Facebook. How would you evaluate whether to launch the News Feed?

Product Analytics & MetricsProduct StrategyA/B Testing & Experimentation
Author's notes

I went straight to metrics and kind of skipped the 'why does this even exist' part, which I think hurt me.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the goal of News Feed: to increase user engagement and retention by providing a personalized, algorithmic stream of content. Then, outline a framework that evaluates user value, business impact, and risks, using metrics and experiments to validate assumptions. Conclude with a recommendation based on data and strategic alignment.

Pro tip: Acknowledge the tension between algorithmic ranking and user control, and propose a phased rollout with guardrail metrics to mitigate potential backlash. Show that you understand Facebook's mission to connect people and the need to balance short-term engagement with long-term trust.

1. Define Success Metrics

Identify key metrics such as DAU/MAU, time spent, retention, and content interactions. Also consider counter-metrics like user satisfaction and well-being.

2. Assess User Value Proposition

Evaluate how News Feed solves user problems: discovery of relevant content, social connection, and personalized experience. Compare to existing alternatives like profiles and notifications.

3. Evaluate Business Impact

Estimate effects on ad revenue, content distribution, and ecosystem health. Consider how algorithmic ranking might change publisher and advertiser behavior.

4. Identify Risks and Mitigations

List potential risks: filter bubbles, privacy concerns, user backlash, and technical scalability. Propose mitigations like transparency controls and gradual rollout.

5. Design and Run Experiments

Plan A/B tests to measure impact on key metrics. Use holdout groups and long-term studies to detect unintended consequences.

Key Points to Mention

  • North Star metric: Daily Active Users (DAU) and time spent per user
  • A/B testing framework with control and treatment groups
  • Guardrail metrics: user-reported satisfaction, unfollows, hide rates
  • Network effects and content ecosystem impact
  • Algorithmic ranking vs. chronological feed trade-offs
  • Privacy and data usage considerations

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.