← Google Interview Insights

Google·Product Manager·Onsite - Product Sense / Strategy·Senior

Senior
Apr 2026

Summary

Google PM interview, product design question focused on a notification recommendation system for a news app. Pretty open-ended and they wanted you to go deep on all of it: the product, the tech stack, the decision logic, and how you'd validate it. A lot of ground to cover in one question.

Questions Asked (1)

Q1

You're the PM leading notification recommendations for an existing news app. Walk through how the product works, the underlying tech, how the system decides which notifications to send, and how you'd test it.

System DesignProduct Sense & IdeationA/B Testing & Experimentation
Author's notes

This is basically four questions in one and I didn't realize that until I was already three minutes into just describing the product.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by framing the problem: define the user value and business goals for notification recommendations in a news app. Then walk through the end-to-end system: data signals, ML models, ranking, and delivery. Finally, describe how you would test and iterate using A/B tests and guardrail metrics.

Pro tip: Emphasize the balance between engagement and user trust—over-notifying can lead to uninstalls, so include metrics like notification dismissal rate and opt-out rate as guardrails.

1. Clarify Goals and Scope

Define the objective: increase user engagement (e.g., click-through, daily active users) while maintaining user trust. Clarify constraints like platform (iOS/Android), existing infrastructure, and privacy policies.

2. Describe the Product Experience

Explain how users interact with notifications: they receive personalized news alerts based on interests, reading history, and real-time trends. Notifications can be breaking news, personalized digests, or recommended reads.

3. Outline the Technical Architecture

Detail the data pipeline: user events (clicks, reads, dismissals) feed into a feature store; ML models (e.g., collaborative filtering, content-based) score candidate articles; a ranking system orders them; and a delivery service sends notifications via push infrastructure.

4. Explain Decision Logic

Describe how the system decides which notifications to send: it considers user preferences, real-time context (time of day, location), article freshness, and predicted engagement. It also applies business rules (e.g., max notifications per day) and deduplication.

5. Testing and Iteration Plan

Propose A/B tests to measure impact on key metrics (CTR, retention) and guardrails (opt-out rate, dismissal rate). Include offline evaluation (precision@k) and online experiments with holdout groups. Plan for iterative improvements based on results.

Key Points to Mention

  • User segmentation and personalization based on behavior and preferences
  • Real-time vs. batch processing for timely notifications
  • Machine learning models for ranking and recommendation (e.g., matrix factorization, deep learning)
  • Metrics: click-through rate, engagement, retention, and guardrails like opt-out rate
  • A/B testing framework with control and treatment groups, statistical significance
  • Feedback loops: using user interactions to continuously train and improve models

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