Strategy question
Perplexity wants PMs to spot enterprise opportunities for Computer. Choose one enterprise vertical you would prioritize first and identify a single workflow where an agent could create 10x value. Walk through how you would size the pain, validate willingness to trust automation, compare it against other candidate workflows, and decide whether it is worth building now.
- Perplexity
- Strategy
- 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
Enterprise opportunity sizing: can you pick one vertical and one workflow, then walk through validating pain and trust before committing engineering investment.
How to approach it
- Pick one vertical, for example legal research or financial analyst workflows, where document-heavy, time-consuming tasks are common and Perplexity's search and synthesis strengths transfer directly.
- Identify a single workflow within it, for example pulling and synthesizing case law or comparable filings, where an agent could compress hours into minutes.
- Size the pain with time-and-motion data from interviews: how many hours per week professionals spend on this task today, and what it costs the firm.
- Validate willingness to trust automation with a small pilot, checking whether professionals accept the output with light review versus needing to redo the work themselves.
- Compare against other candidate workflows on pain size, trust readiness, and technical feasibility, and decide to build now only if all three clear a bar, not just one.
What a strong answer includes
- Commits to one specific vertical and workflow instead of listing several superficially.
- Uses time-and-motion evidence to size pain quantitatively rather than asserting the workflow is valuable.
- Requires trust validation as a separate gate from pain size, recognizing that a painful task is not automatically ready for automation.
Common mistakes
- Names a vertical without picking a specific workflow inside it.
- Conflates a big pain point with readiness to trust automation, skipping the trust validation step.
Likely follow-up questions
- What would make you deprioritize this vertical even if the pain is large.
- How would you pilot this without a full enterprise sales cycle first.
More strategy questions
- Perplexity made Comet free in 2026. How would you monetize an AI browser without hurting the experience?Perplexity · Strategy · Hard
- How would you handle publisher relationships when Perplexity summarizes their content?Perplexity · Strategy · Hard
- How should Perplexity compete with ChatGPT's built-in web browsing?Perplexity · Strategy · Hard
- How would you grow Comet Enterprise adoption inside large companies?Perplexity · Strategy · Hard
- You believe Perplexity’s core agentic experience could unlock value for an enterprise knowledge-work use case, such as competitive research or internal document synthesis. How would you decide whether that opportunity deserves investment now, and what tradeoffs would you make between enterprise-specific requirements and keeping the everyday core product fast, intuitive, and cohesive?Perplexity · Strategy · Hard
- Users often start a task on mobile and expect to continue it later on web, but today the experience feels fragmented. How would you define the cross-device product direction, decide what state and context must persist, and prioritize the first release across iOS, Android, web, and backend teams?Perplexity · Strategy · Hard
More questions from Perplexity
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop