Today's skeleton is two frameworks: first use Growth Loop to find a mechanism a product is already half-running — not inventing a sharing feature from scratch, but finding a behavior users already perform that's one step away from reaching new users, then instrumenting its input, action, and output with metrics. Then use Nir Eyal's Hook Model (Trigger, Action, Variable Reward, Investment) to judge whether a feature can get users to come back on their own, instead of relying on push notifications every time. The practice question is a real Slack interview question from PracHub: how to open more product-led-growth pathways for Slack — the walkthrough demonstrates asking first whether 'growth' means new workspaces, more active members in existing workspaces, or free-to-paid conversion, then picking the cross-company channel-sharing mechanism Slack already runs, rather than bolting on a new invite button, while being ready to answer IT's concerns about ungoverned workspace sprawl. The case study is what Calendly investor and board member Blake Bartlett told Sacra in an interview: Calendly's viral loop wasn't designed — it exists because scheduling is a problem both parties hit at the same moment. That same test (does the workflow already involve someone who isn't yet a user) is exactly the logic used today to prioritize which Slack pathway to build first.
Today's skeleton: define growth with a North Star Metric plus a handful of input metrics, then use Eric Ries's three-engine framework (sticky, viral, paid) to figure out which engine the product is actually running on, instead of answering every growth question with 'add a sharing feature.' The practice question is a real diagnostic prompt — checkout funnel conversion dropped 20% in a week — where ruling out bad data and external causes before jumping to a UX hypothesis is itself the thing being graded. The case study is Clay, which went from a generic spreadsheet product with 20 paying customers to narrowing around cold-email agencies, then compounded through a loop where 'an agency delivers client work with Clay → publishes the workflow → looks like an expert → wins more clients → runs more work through Clay' — reaching a $7.1B valuation in September 2026. The most imitable part of this case isn't the LinkedIn posting, it's the design decision to make sharing the product economically self-interested for the people sharing it.
Today's practice is the growth PM answer spine: clarify whether 'growth' means acquisition, retention or revenue, map the funnel with AARRR and check whether the product grows through a loop, segment before diagnosing, rank experiments with ICE, and pair the primary metric with a leading indicator and a guardrail. The practice question is Suno's retention drop-off; the case is Calendly's viral loop — scheduling is a problem both sides hit at the same moment, a condition most B2B products can't borrow.
Growth & Experimentation interviews aren't testing whether you can run an A/B test — they're testing whether you'll question a pretty number before you ship it. Today's question is a real trap asked at Stripe, Notion, and LinkedIn: 'Your A/B test shows a 12% lift in activation rate. Do you ship it?' The framework: pair every primary metric with a guardrail metric. If the activation bar got quietly lowered to produce that lift, this week's number looks great and next month's churn bill comes due. The case is Auth0, where Growth Marketing and Developer Productivity reviewed each other's experiment designs — on the third test (a product tour), the engineering side added a drop-off guardrail nobody had required, which is the only reason the team caught that the tour could inflate activation while scaring off the users they actually wanted.
Growth & Experimentation interviews don't test whether you can run an A/B test — they test whether you can find the lever with the biggest impact on the north star metric before spending experiment budget. Today's question is a real OpenAI Growth PM prompt: 'If you were to design an experiment or feature to help onboard new ChatGPT users, what would you do?' The framework: split users into five states — new, current, reactivated, resurrected, and inactive — estimate how much each transition between states moves daily active users (DAU), and concentrate experiments on whichever transition moves DAU the most. The case is Duolingo's 2018 discovery that improving Current User Retention Rate had roughly five times the DAU impact of the next-best lever. One resulting experiment changed the streak rule from 'hit your daily goal to keep your streak' to 'finish one lesson to keep your streak' — Day 14 retention rose 3.3% relative, overall DAU rose 1%, and the share of learners still on a streak after 20 days rose 10.5%. Over four years, that metric rose 21% and DAU grew 4.5x.
The most common trap in growth interviews is describing a 'viral loop' as one line — 'let users invite friends' — without answering whether the loop feels like spam to the person on the other end, or what metric decides whether it's worth keeping. Today's practice question: a B2B project management SaaS has stalled, and the CEO wants a growth engine that doesn't rely on paid ads, while users already create tasks and export weekly reports to clients. The framework is the Hook Model (Trigger–Action–Variable Reward–Investment) to check whether an existing repeated behavior can naturally become a touchpoint that reaches outsiders, paired with growth-loop thinking to turn a one-shot funnel into a loop that resupplies itself. The case study is Fyxer — a four-person growth engineering team that ran 541 experiments in a year at a 25% win rate, testing which of users' already-repeated actions could become a growth loop, and took ARR from $1M to $35M — while also killing a loop that sounded clever on paper but felt like noise to users.
The most common way growth PM candidates lose points is jumping straight from a retention drop to a tactic — send a reminder, shorten onboarding, add a loyalty mechanic — without first checking whether the retention metric measures the right unit or which failure mode actually caused the drop. Today's practice is a scenario question: a collaboration tool's week-4 workspace retention dropped, and the CEO wants an experiment plan that proves the intervention is worth the engineering resources. The framework is a retention test brief (define a meaningful return event first, write the competing explanation, then pick the intervention) paired with a metric tree that ties the experiment result back to revenue language. The case is Fanatics refusing to count an experiment result that looked like a win on the surface but whose expected behavior chain never actually moved — they reran it and found the effect was flat.
The gap most Growth interview answers miss isn't a lack of ideas — it's forgetting that in a two-sided marketplace, growth only counts if both sides (Guests and Hosts) grow together. Today we use HubSpot's Growth Flywheel (Attract-Engage-Delight) to map the compounding structure of growth, then use Nir Eyal's Hook Model (Trigger-Action-Reward-Investment) to design a habit loop that brings users back without being pushed — practicing a real 2026 Airbnb interview question from Exponent: How would you 3x Airbnb's growth?
The most common trap in Growth PM interviews isn't running out of growth ideas — it's jumping to a solution that 'obviously should work' before diagnosing the actual bottleneck. Today we swap Reforge's linear funnel thinking for Growth Loops, use a six-step diagnostic chain to find the real leak, and look at a real JobLeads experiment that cut 22 steps down to 5 — and changed nothing — to see why experiment velocity beats any single home run.
The dividing line in growth interviews is whether you're talking about linear improvement or compound loops — adding an acquisition channel is marketing; making one user bring in two users is growth. Today we practice the Goal → Metric → Bottleneck → Hypothesis → Experiment → Measurement six-step diagnosis framework, with a question drawn from a real OpenAI Growth PM take-home.
Growth interviews don't test whether you can growth hack — they test whether you have systematic growth thinking. Core skills: growth loop design (the acquisition → activation → retention → referral flywheel), experiment design (the full hypothesis → metric → experiment → analysis process), retention strategy (finding the aha moment, designing habit loops), and using data to decide what's worth continued investment.