The definitive guide to mastering analytical thinking interviews
A step-by-step playbook to help you ace your PM interviews
👋 Welcome to a 🔒 subscriber-only edition 🔒 of my weekly newsletter. Each week I tackle reader questions about building product, driving growth, and accelerating your career. For more: Lenny’s Podcast | How I AI | Lennybot | Lenny’s Reads | Courses | Swag
Annual subscribers now get a free year of Bolt, Perplexity Pro, Notion, Superhuman, Linear, Granola, and more. Subscribe now.
In my ongoing efforts to help you land your dream job, I’m excited to bring you this truly epic guide by Ben Erez. Below you’ll find everything you need to know to nail your analytical thinking interview—a staple of most product interview loops. I’ve never seen a guide this in-depth, specific, and full of so many real-life examples. I hope this helps them see exactly why you’re the perfect fit for the role.
After a decade in product (at Facebook, as the first PM at three different startups, and as a founder), Ben is now a full-time interview coach, helping PMs land their dream roles. He teaches a top-rated course on PM interviewing (use code “LENNYSLIST” to get $100 off), and on July 9th, he’ll be hosting a free 30-minute lightning lesson where he’ll show you how to use AI to practice for your analytical thinking interviews. Ben also co-hosts Supra Insider, a weekly podcast for the product community.
Bonus: You can now listen to this post in convenient podcast form: Spotify / Apple / YouTube.
In part one of this comprehensive guide—The definitive guide to mastering product sense interviews—I explained why product sense and analytical thinking interviews matter and I walked through my framework for acing the former. Now I’ll walk through my framework for acing analytical thinking interviews.
In this post, I’ll cover:
How to structure your answer to demonstrate the exact signals interviewers are looking for
Common pitfalls to avoid and how to navigate challenging scenarios
Practical preparation techniques to build your analytical muscle
Whether you’re actively preparing for upcoming interviews or you simply want to understand how top tech companies evaluate PMs, this guide will equip you with all the tools and frameworks you need to succeed.
We’ll start by exploring exactly what analytical thinking interviews assess and how they’re structured. By understanding the interviewer’s perspective, you’ll be better equipped to provide the signals they’re looking for.
Understand the analytical thinking interview
Analytical thinking (AT) interviews assess a candidate’s ability to understand a product in the context of its broader company and its market, establish metrics to track success, identify team goals, and evaluate tradeoffs in a structured way. Here are some examples of typical AT questions:
“How would you measure success for Spotify?”
“You’re a PM at Meta. Set a goal for Instagram Reels.”
“What should be the North Star metric for DoorDash?”
Although an AT interview normally lasts 45 minutes, you’ll have only about 35 minutes of actual working time after accounting for introductions and wrap-up questions. That might seem like plenty of time, but it flies by, so you’ll want to let your inner “time cop” run the show.
Since the interviewer won’t be looking for a “correct” answer—rather, they’re evaluating your thought process—I recommend approaching the interview with this linear flow to maximize your chances of providing strong signals for the following dimensions in a structured way:
Note: Analytical thinking interviews can sometimes include other question types, such as debugging/root cause analysis questions and estimation questions, but these are becoming less common. I included some thoughts about tackling debugging and estimation questions at the bottom of this post.
Step 1: Assumptions and game plan
The opening minutes of an analytical thinking interview can make or break your performance. I’ve watched countless candidates struggle because they jumped straight into goals without aligning with the interviewer on the structure.
My advice is to approach the interview as a game with clear rules rather than a casual conversation, and spend the first minute making a handful of assumptions at the start of the interview that narrow the scope to a manageable exercise without prematurely limiting the solution space. Then outline your game plan for the interview, showing the interviewer how you want to spend your time together.
When transitioning between key sections of the interview structure (e.g. from product rationale to metrics framework), take a pause to think through your content for that section of the interview. Once you’re ready, check in with the interviewer to walk them through your thinking and confirm they’re following before you proceed to the next section.
To set yourself up for success, state a few potential assumptions to align on the scope of the exercise. Here are some flavors of assumptions that can be helpful:
Let’s now apply our assumptions framework to the first typical AT question I gave above, which we’ll be using as an example throughout this post: How would you measure success for Spotify? (Other potential questions and answers will be available in links at the bottom of each section.)
The assumptions below focus on the core consumer-facing music streaming service globally across all platforms, preventing getting lost in niche features or regional specifics. This grants you the freedom to explore meaningful metrics that capture Spotify’s fundamental purpose without being overwhelmed:
I’ll focus on Spotify’s core music streaming service as the primary product.
I’ll emphasize the consumer-facing experience rather than artist/label tools or enterprise solutions.
I’ll assume we’re focusing on global metrics, not specific to any one region.
I’ll assume we’re talking about all platforms where Spotify is available (mobile, desktop, etc.).
Additional examples:
Question: You’re a PM at Meta. Set a goal for Instagram Reels.
Assumptions here acknowledge Reels’s worldwide reach, concentrating on mobile because that’s where the primary user engagement happens.
We also choose to focus on the current state of the product to ensure alignment with the interviewer that we’re not measuring success at launch.
Question: What should be the North Star metric for DoorDash?
Assumptions here mention customers, restaurants, and dashers up front, signaling that you think about the entire marketplace.
Focusing on the U.S. market prevents overwhelming complexity, and including all platforms/devices keeps the exercise comprehensive.
After stating assumptions, share your game plan for the interview to make sure you’re on the same page as the interviewer about how you’ll spend your time together:
“I want to start by reviewing the product’s landscape and reason for existing, then identify key stakeholders and ecosystem health metrics, define a North Star metric with guardrails, and finally set specific team goals. We can discuss tradeoffs along the way at any point. Does that sound like a good plan for our time together?”
Interviewers love hearing this because it tells them you have a plan to generate the signals they need. To put you in the interviewer’s shoes, this is kind of like sitting down to play a game with someone who knows how to play vs. someone who doesn’t. It’s just better.
Outlining your game plan up front also gives the interviewer a chance to redirect you if they want to spend the time differently, preventing you from going in the wrong direction and wasting everybody’s time.
Step 2: Product rationale
With the interviewer on board with your assumptions and game plan, the next step is articulating the product rationale. This is your opportunity to establish your understanding of the product context and its strategic importance to the business before diving into metrics. Without this contextual grounding, your metrics will feel arbitrary rather than aligned with the product’s purpose and the business needs.
While most good candidates describe what a product does, you’ll set yourself apart by building a compelling strategic foundation touching on three key areas:
Product context: Describe the product, its maturity level, and business model. Explain the core problem it solves for users and why this problem matters to the market and the company. Articulate how the product creates and captures value, being specific about revenue streams.
Market positioning: Review the competitive landscape and highlight the company’s unique advantages relative to its peers. Let your awareness of relevant trends in the market shine.
Company and product alignment: Create a concise, powerful mission statement that captures the product’s core purpose. For products within a larger company, establish a clear throughline from company mission to product mission. Connect the product’s purpose to the parent company’s broader vision and strategic objectives.
Top candidates don’t just describe a product’s features but establish a compelling case for why it matters to users, the business, and the market. This foundation makes all subsequent metrics and recommendations feel naturally aligned with the product’s core purpose.
💡 Tip: Spend about a minute organizing your thoughts before sharing product rationale with the interviewer.
Examples of articulating product rationale
Let’s now apply our metric framework principles to our question: How would you measure success for Spotify?
The rationale below articulates the core problem Spotify solved (music piracy and limited access), establishing why the product exists beyond its features. Second, it positions Spotify within its competitive landscape, highlighting specific differentiators like recommendations and platform support. Most importantly, it concludes with a powerful mission statement that will serve as our North Star for all subsequent metrics and decisions.
Spotify is a music and podcast streaming service offering millions of tracks through a freemium model, generating revenue via premium subscriptions and advertising to free users.
Spotify addressed the critical problem of music piracy by providing legal, affordable access to extensive content when consumers previously faced limited, expensive purchasing options or risky illegal downloads, creating a sustainable model benefiting both listeners and creators.
Currently in late growth/early maturity, Spotify has secured significant market share while expanding globally and diversifying beyond music.
Competing with Apple Music, Amazon Music, and YouTube Music, Spotify distinguishes itself through superior recommendations, social features, broader platform support, and dedicated focus on audio content as its core business rather than an ancillary service to sell hardware or other subscriptions.
Mission statement: “Unlock the potential of human creativity by giving artists the opportunity to live off their art and fans the ability to enjoy and be inspired by it.”
Additional examples:
Question: You’re a PM at Meta. Set a goal for Instagram Reels.
The framework here demonstrates how to craft a product rationale that connects product-level purpose to company-level strategy.
Note how it establishes the market context (shift to short-form video content), competitive positioning against TikTok and YouTube Shorts, and Meta’s unique advantages.
It also explicitly connects Reels to Meta’s broader mission of building human connection, creating a clear throughline from company vision to specific feature.
Question: What should be the North Star metric for DoorDash?
The framework here demonstrates how to address multiple stakeholders in a marketplace.
Notice how it explicitly identifies the problem solved for each ecosystem player: convenience for customers, expanded reach for restaurants, and flexible earnings for drivers.
It also acknowledges the product’s maturity stage and expansion opportunities beyond its core offering.
The mission statement elegantly captures the multi-sided value proposition in a single sentence.
How to practice product rationale
Get reps in with an exercise that develops both written and verbal muscles:
Write down the rationale for 3 of your favorite products (touching on the key elements above), and grab time with a friend to verbally walk them through these in roughly 2 minutes.
Then ask them to read back to you what they remember about why the product exists, who it’s for, how it makes money, and what makes it different from its competitors. If they understood those, you’re on track!
Step 3: Metric framework
Next, you’ll leverage the product rationale to define concrete metrics that track ecosystem health. This section is nuanced and often entails a decent amount of back-and-forth with the interviewer to make sure they follow your thinking. So allocate the largest chunk of time in the interview to your metric framework.
While good candidates can identify relevant metrics, what will set you apart is a cohesive story about healthy growth:
Ecosystem value: Start by listing key players who derive value from the product ecosystem rather than jumping straight to metrics. For each ecosystem player, identify their value proposition for participating (“What’s in it for me?”) and the specific actions they must take to realize this value. Leave out nice-to-have actions.
Metric definition: Track key actions through metrics that a data scientist could implement, including time frames based on real user behavior. Define a North Star metric (NSM) that reflects value creation across ecosystem players and can grow indefinitely as the product succeeds. Make sure you include a time frame (e.g. “weekly”) with the NSM definition.
Critique NSM: Call out the drawbacks of your NSM, identifying 1-2 ways that NSM growth could unintentionally damage ecosystem health. Define guardrail metrics that specifically address the key drawbacks.
If you can’t describe your metric to a data scientist in a way that they could run a query with, it’s not a useful metric. Always define metrics so specifically that someone could implement them tomorrow, and focus on 3-5 primary metrics per ecosystem player rather than trying to capture everything. Metric selection can also become problematic if you use averages or ratios as North Star metrics. Here’s why this backfires: if your NSM increases while your ecosystem actually shrinks, you’re getting a false positive. I’ve watched candidates confidently present metrics that could look great even as their product dies (not exactly what you want to signal to an interviewer).
💡 Tip: Spend about 2 minutes organizing your thoughts before sharing your metric framework with the interviewer.
Examples of metric frameworks
Let’s now apply our metric framework principles to our question: How would you measure success for Spotify?
The framework below organizes metrics by players (listeners, creators, advertisers, Spotify), tracking value creation across the ecosystem. I like tracking daily, weekly, and monthly (“DWM” in short) in the ecosystem metrics section before narrowing in on one time frame for the NSM. The NSM, “total streaming hours per week,” measures the total volume of our unifying action that benefits all ecosystem players in a way that matches real engagement patterns. The guardrail metric prevents becoming a passive platform.
Additional examples:
Question: You’re a PM at Meta. Set a goal for Instagram Reels.
The framework here balances adoption indicators (daily Reels viewers) with engagement depth (watch time).
The North Star metric “total Reels watch time per week” captures the core value: engaging short-form video.
Guardrail metrics prevent optimizing watch time at the expense of content quality or broad user adoption.
Question: What should be the North Star metric for DoorDash?
The framework here measures marketplace success by tracking key indicators for all players: customers placing orders, restaurants fulfilling them, and dashers delivering.
The North Star metric, “total completed deliveries per week,” captures the core transaction creating value across all sides.
Guardrail metrics prevent pitfalls of pursuing delivery volume alone: order satisfaction for quality, retention rates for sustainability, and profit margins to avoid unprofitable growth.
How to practice metrics frameworks
With the products you chose earlier, spend about 10 minutes doing the following exercise with each:
Identify the ecosystem players, map out what value they get and what actions they take, and create specific metrics with time frames that actually make sense.
Then define a North Star metric that can grow indefinitely, and pair it with guardrail metrics that address the biggest ways your NSM could mislead you.
To build your verbal communication muscle, walk a friend or two through your thinking. Ask them if they understand who benefits from the product, how success would be measured, and why you chose your specific North Star metric over alternatives. If they can clearly explain back your measurement logic and see the connection between value and metrics, you’re in good shape!
Step 4: Goal-setting
After you’ve nailed down a solid metrics framework, here comes the critical transition that trips up a lot of candidates: making an “altitude shift” from company/product-level metrics to specific team-level goals. This is where you show the interviewer you can bridge strategy and execution—a skill they’re evaluating.
 | A guest post by
|