Metrics question
Perplexity also wants this PM to expand usage among existing SMB operators. Design a growth plan for increasing adoption of relevant Computer capabilities across onboarding, lifecycle messaging, and in-product recommendations. What user segments, funnel metrics, and experiments would you prioritize first, and why?
- 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
Whether you can design a full-funnel growth plan for an existing customer base and choose experiments with a clear, prioritized rationale.
How to approach it
- Segment SMB operators by current usage depth, for example single-capability users versus multi-capability users, since the growth levers differ for each.
- Define funnel stages: onboarding (first capability activated), lifecycle (return usage and expansion to a second capability), and in-product discovery (surfacing relevant capabilities at the right moment in a workflow).
- Prioritize onboarding improvements first if data shows many users activate one capability and never discover others, since that is usually the highest-leverage, lowest-cost fix.
- Design lifecycle messaging around specific triggers, for example a user running paid social campaigns gets a targeted nudge about a relevant SEO or CRO capability, not generic re-engagement email.
- Prioritize funnel metrics: activation rate on a second capability, weekly active usage across capabilities, and time-to-second-capability-adoption.
- Sequence experiments by expected impact and cost, starting with in-product discovery nudges (cheap, fast to test) before larger onboarding redesigns (slower, higher cost).
What a strong answer includes
- Segments by current usage depth rather than treating all SMB operators as one growth funnel.
- Names a specific, triggered lifecycle message example rather than generic re-engagement messaging.
- Prioritizes experiments by a cost-versus-impact sequence, starting cheap and fast before big redesigns.
- Picks time-to-second-capability-adoption as a genuinely useful funnel metric specific to a multi-capability product.
Common mistakes
- Treating growth as one funnel instead of segmenting by current usage depth.
- Proposing generic lifecycle messaging without a specific behavioral trigger.
- No sequencing logic for which experiments to run first.
Likely follow-up questions
- How would you validate which capability to recommend next for a given user?
- What would you do if onboarding improvements do not move the second-capability activation rate?
- How would you balance growth experiments against the design-partner program's bespoke requests?
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: Measuring AI Product Economics
- Chapter 2: Using SQL and Logs
- Chapter 14: Interviewing for AI PM Roles