Metrics question
Perplexity cares about product-led growth and data-driven flywheels. For a new AI productivity feature inside Search or Computer, what user actions would you optimize first to drive activation, retention, and learning effects, and how would you know the feature is creating a real flywheel rather than a one-time novelty spike?
- Perplexity
- Metrics
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Growth thinking for AI products: can you identify the right leading actions to optimize and design a test that distinguishes a real flywheel from a one-time novelty spike.
How to approach it
- Pick the action that is closest to habitual value creation, for example saving or reusing a prior search or workflow, rather than just first use.
- Prioritize actions with compounding value: each use should make the next use better or faster, for example connectors or personalization that improve with more data.
- Optimize activation around getting a user to that compounding action quickly, and retention around whether they return to use it again within a defined window.
- Define a flywheel signal specifically: usage frequency or session depth increasing over successive weeks for the same cohort, not just aggregate growth.
- Distinguish novelty from flywheel by tracking a cohort's week-over-week usage curve; a spike that decays to baseline within a few weeks is novelty, sustained or increasing usage is the flywheel.
What a strong answer includes
- Picks a specific compounding action, not just generic activation, and explains why it compounds.
- Defines the flywheel test concretely as a cohort usage curve over multiple weeks, which is falsifiable, rather than a vague claim of engagement.
- Separates activation and retention as different levers instead of treating growth as one metric.
Common mistakes
- Optimizes for first-use activation only, without checking if usage compounds over time.
- Calls any usage increase a flywheel without a cohort-based test to rule out novelty.
Likely follow-up questions
- What would you do if the cohort curve looks flat rather than decaying or growing.
- How long would you wait before declaring the feature a flywheel or a novelty.
More metrics questions
- What metrics would tell you whether Perplexity is winning against Google Search?Perplexity · Metrics · Hard
- Queries per user dropped 20% after a UI change. How do you investigate?Perplexity · Metrics · Medium
- You have one team and can materially advance only one of these areas in the next 6-12 months: Skills, collaboration, artifact generation, or Projects. How would you choose where to invest, and what leading indicators and longer-term outcome metrics would you use to defend that roadmap to leadership?Perplexity · Metrics · Hard
- Users can create Skills in Computer, but many run a Skill once and never use it again. How would you determine whether the main issue is setup friction, weak discoverability, inconsistent results, narrow applicability, or lack of trust, and what product changes would you test first to improve repeat use and sharing?Perplexity · Metrics · Hard
- Suppose Perplexity launches a new 'resume previous work' feature for research and productivity workflows. What metrics would you use to determine whether it improves retention, and how would you separate durable user value from short-term engagement spikes caused by novelty or accidental usage?Perplexity · Metrics · Hard
- Pick one Perplexity use case, research, investing, or shopping, and design a first prototype in Computer for a domain expert. What exact job-to-be-done would it solve, what would the user see and control step by step, and which early metrics would tell you the prototype is genuinely improving productivity?Perplexity · Metrics · Medium
More questions from Perplexity
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 2: Data fluency: SQL, logs, and reading the truth yourself
- Chapter 14: Get the job: the AI PM interview loop