Product design question
Perplexity notices that many users start a research task on web, ask several follow-ups, but do not return to that work on another platform later. How would you identify the single highest-leverage friction point in the begin → continue → return journey, and decide whether to invest first in context carryover, navigation, or collaboration?
- Perplexity
- Product design
- 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
Tests identifying the highest-leverage friction point in a cross-platform user journey and choosing where to invest first among several plausible fixes.
How to approach it
- Break the journey into three distinct hypotheses: context carryover (the work exists but is not visible elsewhere), navigation (users cannot find their past work), and collaboration (users would return only if others used it too).
- Check the simplest hypothesis first: whether returning users on another platform even see their prior task listed, since a pure visibility gap is the cheapest to test.
- If visibility exists but return rate is still low, test navigation friction, how many steps it takes to find and reopen past work.
- If navigation is not the bottleneck, test whether return is actually gated on collaboration, users waiting on others rather than struggling to find their own work.
- Instrument each hypothesis with a targeted funnel metric rather than relying on aggregate cross-platform return rate alone.
- Invest first in whichever hypothesis shows the largest measured drop-off, likely context carryover or navigation before collaboration, since those are typically cheaper and faster to fix.
What a strong answer includes
- Tests the cheapest hypothesis, visibility, first before assuming a harder problem like collaboration is the cause.
- Uses targeted funnel instrumentation per hypothesis instead of one aggregate cross-platform return metric that cannot localize the cause.
- Sequences investment by measured drop-off size and fix cost, not by which explanation sounds most compelling.
Common mistakes
- Assuming collaboration is the cause without first ruling out simpler visibility or navigation gaps.
- Using one blended cross-platform metric that cannot localize which journey stage is actually broken.
Likely follow-up questions
- How would you instrument visibility specifically without adding UI clutter?
- What would you do if all three hypotheses show similar drop-off?
More product design questions
- How would you improve Perplexity's Comet browser for daily use?Perplexity · Product design · Medium
- Design an AI shopping assistant inside Comet.Perplexity · Product design · Medium
- Design a 'Deep Research' feature that produces trustworthy, citable reports.Perplexity · Product design · Hard
- How would you design Comet Assistant to safely act on tasks like booking flights and managing email?Perplexity · Product design · Hard
- Design the core interaction model for a Project where a human and multiple agents collaborate on ongoing work. How would you handle delegation, approvals, edit history, permissions, and recovery from bad agent actions so the experience feels powerful but dependable?Perplexity · Product design · Hard
- Users of Perplexity Computer say they do not understand why the agent clicked, searched, or changed course, and they hesitate to let it continue. Design a core interaction model that makes the agent’s intent, current state, and next actions understandable and controllable without turning the product into a complex dashboard.Perplexity · Product design · Hard
More questions from Perplexity
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovering and Sizing AI Opportunities
- Chapter 7: Designing AI UX and Oversight
- Chapter 14: Interviewing for AI PM Roles