Metrics question
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
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
Product design fluency: can you pick a concrete use case and define a first prototype in enough detail to be buildable, with metrics that show real productivity gain, not novelty.
How to approach it
- Pick one use case, for example investing research for a retail investor doing due diligence before a trade.
- State the exact job to be done: pull filings, recent news, and analyst commentary on a ticker into one synthesized view the user can question further.
- Walk step by step: user enters a ticker, Computer assembles sourced findings, user asks follow-up questions, user exports or acts on a summarized thesis.
- Define what the user controls: which sources to include, depth of analysis, and the ability to challenge or correct any claim inline.
- Pick early metrics: time to first useful synthesis, follow-up question rate as an engagement signal, and self-reported time saved versus manual research, collected in a short in-product survey.
What a strong answer includes
- Chooses one concrete use case and stays specific to it rather than describing all three generically.
- Names the exact controls the user has, which shows real product thinking, not just a feature list.
- Uses a mix of behavioral (follow-up rate) and self-reported (time saved) metrics since productivity gains are hard to measure from logs alone early on.
Common mistakes
- Describes all three use cases shallowly instead of committing to one with real depth.
- Metrics measure engagement only, with nothing tied to actual productivity or time saved.
Likely follow-up questions
- How would you validate the self-reported time-saved number is not just novelty bias.
- What would the prototype's failure mode look like, and how would you catch it.
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
- 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
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