General Memorization

Question 1

What is being tested in a metric definition question? (2)

Answer 1

1. Testing your ability to select the important metrics using a structured process.
2. “The aim isn’t to find a perfect metric, but a good enough metric that encapsulates the business/user goal while being aware of its potential downside.”

Question 2

What approach do you use if you get a question asking you to define metrics for a product?

Answer 2

The GAME framework.
1. Goals - Agree with the interviewer on what the goals are for the product, and what the primary goal is.
2. Actions - List all the actions users can take in the product (don’t go into too much detail), and prioritize them based on the goals you aligned on (especially the primary goal). Explicitly state which actions you’ll focus on.
3. Metrics - For each prioritized action, define 2-3 specific metrics used to track it. This is your recommendation.
4. Evaluate - Evaluate the metrics you recommended by their trade-offs/limitations.

Question 3

What is being tested in a metric change question?

Answer 3

Metric change questions test if you know what to do when a key product metric (e.g. traffic, revenue, engagement, etc.) is going up or down for no apparent reason.

Question 4

What approach do you use if you get a question asking you to diagnose why a metric has changed?

Answer 4

Use my SMRPS method (an adapted DEC method):

1. Specifics - Get specifics of the metric change - Figure out 3 things: 1) what the exact/specific metric is, 2) the time period over which the metric has changed, and 3) are all users impacted, or just a subset? If a subset, what characteristics define the subset? (e.g. device type, location, etc.)

Root causes with MECE: Explore possible root causes of the change:
2. MECE - Create a MECE framework for possible root causes.
3. Root causes brainstorm - Brainstorm potential root causes of the problem within this framework.
4. Pull Data - For each root cause, pull data for the root causes you brainstormed

5. Summarize - Summarize conclusion and how we got there

Question 5

What should I be thinking if I get a metric change question? (2)

Answer 5

1. Use the SMRPS method
2. When walking through my root causes, pay attention if the interviewer asks me to talk through some of my proposed root causes. They’ll often give clues that will point me in the right direction.

Question 6

What is a MECE framework? (3) What are the 3 benefits of it? (3)

Answer 6

**Characteristics: **
1. Mutually exclusive - no overlap between parts
2. Collectively exhaustive - the parts comprise the whole (there’s nothing that isn’t included in the whole that isn’t included in the parts)
3. To ensure being CE, you’d often have an “other” category

Benefits:
1. There is no overlap between the different parts which means** it’s easy for clients to focus and discuss one element at a time.** You’re never mixing apples and oranges.
2. **No risk of missing something. **Clients are often worried that you will “miss something” and being MECE reassures them.
3. You can split the work up without duplication. Finally, taking a MECE approach enables you to make sure that there’s no duplication of work in your consulting project. It means that John can cover the US market, Julie can focus on Europe, Mike on Asia, etc. Your team can organise itself in a clear and transparent way which once again clients appreciate.

Question 7

What’s one good source of how to split it if you want to create a MECE framework?

Answer 7

Maths formulas are great to create MECE frameworks. If your framework is a maths formula, it’ll be MECE by definition. (e.g. profits’ math formula is revenue and costs)

Question 8

What are some common MECE frameworks breakdowns? (5)

Answer 8

1. Math formulas (e.g. profit = revenue and costs)
2. Steps in a process (if they’re CE for the unit you’re working with)
3. Product lines
4. Countries
5. Distribution channels

Question 9

What is a great thing to use if you want to find the root cause of a problem?

Answer 9

MECE

Question 10

What’s an important metric at Meta that I shouldn’t forget about? (not sure if it’s the most important, but it’s important)

Answer 10

Retention

Question 11

What are the interview types you can expect at Meta, and the question types in each interview type?

Answer 11

1. Product sense
a. Product design
b. Product improvement
c. Product strategy (e.g. “should our company add a product for X?”, “How would you monetize some_product?”, “If you were a PM for some_product, what would you build?”)

2. Analytical thinking (formerly execution)
a. Metric definition
b. Metric change (debugging)
c. Prioritization / trade-off (often about product features)

3. Leadership and drive (these are behavioral questions)

Question 12

What is the interviewer testing in a prioritization / trade-off question at Meta? (2)

Answer 12

1. How well candidates can identify customer needs when it comes to picking the most important features and/or building out a product roadmap
2. They want you to single out your highest priorities using a process that includes a thorough investigation of the factors and trade-offs involved.

Question 13

What are a few things the interviewer is looking for in a Meta product sense interview? (4)

Answer 13

1. User-centricity - You identify who to build for and what their needs are
2. You prioritize based on value and impact
3. Non-obvious: You welcome critique and new constraints and adapt instantly when fresh data arrives
4. You manage real‑world constraints,

Handling critique: The strongest candidates pause, re‑verify the user insight, propose a tweak, and recap the decision path. Staying calm and structured under fire shows you can “lean into push‑back and iterate in real time”

Question 14

What are a few things the interviewer is looking for in a Meta analytical thinking (formerly execution) interview? (4)

Answer 14

1. How you set the right goals for a product and measure against them
2. How you identify, frame, and evaluate trade-offs and priorities
3. How you analyze and debug problems
4. How you set your team up for success

Question 15

What are a few things the interviewer is looking for in a Meta leadership and drive interview? (5)

Answer 15

1. How you earn trust and take ownership
2. How you process and grow from past experiences
3. How you support the people around you
4. How you overcome difficult situations
5. How you get stuff done and prioritize projects

Question 16

What are the question types and sub-types you can expect in a Google PM interview? (5)

Answer 16

Product Insight Questions (34%)
a. Product Design
b. Product Improvement
c. Favorite product

Analytical Questions (21%)
a. Estimation
b. Metrics definition
c. Metrics change

Behavioral Questions (21%)
a. General
b. Googleyness and Leadership - whether you align with Google’s values and can lead and influence effectively.
c. Cross-Functional Collaboration - focuses on how well you can maintain a professional demeanor while engaging in high-pressure situations that require buy-in from a diverse range of stakeholders.

Strategic Insight Questions (14%) - Defining a strategy

Craft and Execution Questions (10%) (though this may have grown in the last couple years)

Question 17

What are interviewers looking for in a Google product insight question? (2)

Answer 17

1. Be able to consider user experiences from the customer’s perspective and use that point of view to design and improve products.
2. They should then convey a clearly defined product vision to stakeholders, and follow through on it.

Question 18

When answering a metric definition question, what’s one thing you shouldn’t forget?

Answer 18

You must be able to identify the downsides of your choices (your chosen metrics), and why they are outweighed by the advantages.

Question 19

When answering a product strategy question, what’s one thing you shouldn’t forget?

Answer 19

You must be able to identify the downsides of your choices (your chosen solution/strategy), and why they are outweighed by the advantages.

Question 20

In a prioritization / tradeoff question, what should your process be?

Answer 20

PUBFRATS

1. Product - Understand the product properly
2. User - define the user
3. Business Objective - define the business objective
4. Framework - decide on a prioritization framework (e.g. RICE) and describe why it fits the situation well
5. Rate each option using the framework
6. Adjust based on non-accounted-for-factors (factors that weren’t accounted for in the prioritization framework)
7. Tradeoffs - State the tradeoffs.
8. Summarize

Question 21

What are the components of the RICE framework? (4) How do you use it? (1)

Answer 21

How to use it:
Assign numerical values to each of R, I, C, E, then calculate it using RIC/E

Components:
Reach : how many customers this product or feature will affect in a given time period
Impact : the degree to which this product or feature will contribute to your goal
Confidence : how sure you are about the values you’ve chosen in this calculation
Effort : the overall time your team will invest in the project

Question 22

How do you assign scores for each letter in RICE?

Answer 22

Reach:
Fnd a metric involving number of people reached in a certain unit time (e.g. quarter or year)

Impact:
3: huge impact
2: high impact
1: medium impact
0.5: low impact
0.25: minimal impact

Confidence:
If you have good analytics, user research, and engineering feedback (respectively) for R, I, and C, you’d have 100% confidence. If you have ⅔, it’s 80%. If you’re just working with educated guesses for all 3, it’s 50% or less.

Effort:
Use a rough estimate of person-months or person-weeks required.
- Consider the total amount of person-months (or person-weeks for smaller projects) this product or feature will take, from planning to implementation and testing, taking into account the work from every branch of your team, including product, design, and engineering.

Question 23

What are interivewers assessing in a product strategy question? (e.g. a strategic insight question at Google) (3)

Answer 23

1. With strategic insight interview questions, interviewers assess if you’re comfortable thinking about the wide range of aspects good PMs need to take into account when making product decisions. This includes competition, pricing, marketing, time to market, etc. Thinking through all these aspects requires creativity and a structured approach.
2. Strategy questions also test how capable you are of setting the product vision and articulating a roadmap to deliver it.
3. “One of the key pillars in product strategy questions is articulating the vision. Put an ambitious vision into simple words. Put the user at the center, connecting the mission to customer principles.” -Former Google PM

Question 24

What should your approach be when you get a question of this form?

“If you were the PM/CEO for [product/business], how would you [objective] over the next [timeframe or constraint]?”

Answer 24

1. Clarify ambiguous parts (e.g. scope they want you to focus on).
2. Business objective (set one if you don’t have one): After you’ve described some options for the business objective, the interviewer should help you pick one, but if they don’t, pick one that feels highest priority for the company (and say why you picked it). Try to use tangible metrics when you can because this removes as much ambiguity from what you’re trying to achieve as possible.
3. Framework for brainstorming solutions Create a structure/framework in which you’ll brainstorm solutions (one way is to think “Where can I influence this metric?” then state them). Draw a 2-column table with the structure/framework (1st is the structure, 2nd is the solutions). Brainstorm solutions, within the structure, that influence the metric
4. Prioritize - prioritize the solutions based on sound logic. So be sure to describe the logic you use for prioritizing). Be sure to, at a minimum, describe the reach and impact of your solutions.
5. Tradeoffs - Identify tradeoffs of your solutions.

Question 25

What’s are some things you should be sure to do when prioritizing solutions during a product strategy question? (3)

Answer 25

1. Be sure to, at a minimum, describe the reach and impact of your brainstormed solutions. 1. Try to make your answer data-driven 1. “If possible, try and include a data point that validates your solution to the strategy problem. Something in the real world that you can use as evidence for why your recommended solution could work.” Jason, ex-Amazon PM

Question 26

What does the Meta analytical thinking interview test for? (4)

Answer 26

1. Goals: Being mindful of how the goals (especially quantitative goals) can be gamed or how they can sometimes be counter-indicative of progress. 1. Metrics: What would you use to measure if the product is healthy? Which one would you prioritize? What happens if one is decreasing and the other is increasing? 1. Debugging: Say you notice a specific metric dropping week after week. The interviewer will present a problem statement, and you should ask questions to describe how you’d approach this challenge and determine what’s causing this metric to drop. 1. Navigating a complex trade-off: “A” or “B” option—how do you know what to show to which communities of users?

Question 27

What are some things interviewers are looking for in a craft & execution question at Google? (5)

Answer 27

1. Above all, interviewers are looking for PMs who can make good decisions in real-time, when information is missing or unreliable, and the way forward isn’t always clear. 1. Intentionality when making decisions, taking into account business objectives, urgency, and stakeholders affected. 1. Efficiency in assessing situations and a bias for action. 1. Classic execution skills like problem diagnosis, goal-setting, and choosing metrics. 1. Note that the sample questions above all have analytical, strategic, and product elements. Don’t let that scare you. Instead, use the craft and execution round to show that you’re the whole package – you’ve mastered the craft of product management.

Question 28

What's something I should keep in mind when I get a situational question? (i.e. asking what I would do in a certain situation) (1)

Answer 28

If a question has some interesting, unique immediate context (e.g. “a VC is giving you money”), go hard on gathering clarifying info about the context. This will make the rest of the answer easier. E.g. in this question, ask if the VC is specialized in any way, are there expectations around how the money will be used? Do not ignore the immediate context - your ability to assess a situation is being tested.

Question 29

What should my approach be when I get a situational question (giving me a specific situation and asking what I would do)?

Answer 29

1. Go hard at clarifying the unique context. What’s unique about this scenario, and really ask questions to get more specifics about the situation. E.g. if the question says “a VC is giving you money…”, ask if the VC is specialized in any way, are there expectations around how the money will be used? Don’t feel pressured to move through this stage quickly. 1. Use your other frameworks and skills to handle it

Question 30

What should you be thinking if you get a question like “Engineering comes to you and says they can’t deliver on time. What do you do?”

Answer 30

I'm thinking this is a situational question, and I should gather specifics about the immediate context.

Question 31

What should you be thinking if you get a question like “Your biggest customer requested . They went straight to engineering to see if it could be implemented. How do you handle it?”

Answer 31

Fill this in

Question 32

What's a good rule of thumb when you're prioritizing or going over tradeoffs in a product manager interview?

Answer 32

A good rule of thumb: mention at least one technical, one business, and one UX constraint without prompting—shows you think holistically.

Question 33

At a high-level, what do meta interviewer's want you to do in a product sense interview? (3)

Answer 33

1. understanding the product’s purpose and context 2. deeply understanding the user and their problems 3. proposing a high-level solution

Question 34

What are HEART metrics used for? What is each component (with an example for each)?

Answer 34

**Used for:** Outlines the different components of good UX, and how to measure them. * **Happiness:** Measures user attitudes or satisfaction. Example: Net Promoter Score (NPS), user satisfaction surveys, or app store ratings. * **Engagement:** Reflects the level of user involvement. Example: Daily Active Users (DAU), session length, or frequency of feature usage. * **Adoption:** Tracks new user acquisition or feature uptake. Example: Number of new users per week or percentage of users trying a new feature. * **Retention:** Measures how many users return over time. Example: 30-day retention rate or churn rate. * **Task Success:** Assesses how effectively users complete key tasks. Example: Task completion rate, error rate, or time on task.

Question 35

What is AARRR and when would this be useful in a product manager interview? When is it not useful?

Answer 35

**Acquisition** – How users find you (e.g., channels like SEO, ads, social media). **Activation** – The user’s first positive experience (e.g., signing up, completing onboarding). **Retention** – Users returning over time (e.g., app opens, repeat purchases). **Referral** – Users sharing the product (e.g., invites, word-of-mouth). **Revenue** – Monetization (e.g., subscriptions, in-app purchases). **When it's useful in a PM interview:** * When you're asked how you’d measure product success * structuring answers to case questions around product improvement or growth. (e.g. identifying growth bottlenecks) **Companies & products it's useful for:** * useful for early-stage startups, SaaS products, and consumer-facing apps where tracking user behavior and conversion at each funnel stage is critical **Companies & products it's not useful for: ** it's less useful for enterprise products with long sales cycles, non-digital products, or internal tools where the funnel doesn't apply neatly. In those cases, success may hinge more on account-level metrics, stakeholder satisfaction, or workflow efficiency rather than user-driven funnels.

Question 36

What is the form of a Google craft & execution question?

Answer 36

It gives you a specific situation and asks how you would handle it. Then they would give follow-ups changing the context and seeing how you would react.

Question 37

What is your approach to solving a “how would you improve this product?” questions:

Answer 37

-**Users:** Identify the users -**Pain points:** Identify their pain points -**Business goals: ** Identify the business goals -**Solutions: ** Try to think of some solutions for the pain points and business goals -**Validation:** How would you test the solution using limited resources? What metrics? Etc.

Question 38

In a metric change question, if I get stuck trying to break down the problem into different angles to diagnose where the cause of the metric change might be, what are the 3 most important ways to remember? (3)

Answer 38

**User Segmentation** – Slice the metric by user type (e.g. new vs. returning, device, country, traffic source) to see which group experienced the drop. **Funnel Analysis** – Break the user journey into steps (e.g. login → search → click → purchase) to locate where the conversion rate suddenly decreased. **Change Timeline Review** – Check for recent product launches, A/B tests, infra updates, or external events that coincide with the drop.

Question 39

What's your process for product design questions?

Answer 39

1. **Why this product? / High-level company objective** -Explicitly state my assumptions based on the immediate context -What is x? -Company mission/strength -Trends -Competitors 2. **** 2. **Who: Ecosystem/stakeholders** 3. **Pick a user then subsegment (3 or 4) and prioritize** -Based on Underserved/TAM 4. **List pain points (3 or 4) and prioritize one** -Based on severity/frequency 5. **Solutions/vision** -3 or 4 solutions and prioritize one -Pitch your vision -Based on impact/effort 6. **Metrics** 7. **Discuss risks/tradeoffs**

Question 40

Today’s bar for product sense interviews is that candidates anchor everything—problem selection, opportunity sizing, even the down‑stream design choices—in a crisp articulation of goal: What core business objective does the proposed product advance? What are the common objectives?

Answer 40

Fill with ChatGPT