Strategy question
You have feedback from multiple SMB design partners across paid social, lifecycle, and SEO, but their requests conflict and many are one-off. How would you convert that input into a prioritized roadmap for skill packs, connectors, and core capabilities while separating urgent partner asks from features that can scale across the SMB base?
- 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
Whether you can convert fragmented, conflicting partner feedback into a coherent roadmap by separating what is urgent-and-specific from what generalizes.
How to approach it
- Tag every piece of feedback by workflow (paid social, lifecycle, SEO) and by type: a request for a new skill pack, a connector, or a core capability change.
- Look for overlap across design partners first, since a request appearing across paid social, lifecycle, and SEO partners independently signals a core capability gap, not a one-off.
- Route requests that appear in only one partner's workflow into a bounded, partner-specific solution (a custom skill pack or configuration) rather than a platform change.
- Route requests that recur across partners into the core roadmap, prioritized by how many partners and how central the workflow is to their business.
- Build a lightweight scoring pass: frequency across partners times workflow criticality, to rank the core-roadmap candidates.
- Communicate back to each partner what was generalized, what was scoped as partner-specific, and why, to keep the design-partner relationship productive rather than transactional.
What a strong answer includes
- Uses cross-partner recurrence as the specific signal for what belongs on the core roadmap, directly answering the 'separating urgent from scalable' framing.
- Proposes skill packs and connectors as the outlet for partner-specific asks, so those do not get abandoned, just scoped differently.
- Gives a concrete scoring method (frequency times criticality) instead of a vague prioritization promise.
- Closes the loop with partners on what was and was not generalized, protecting the relationship.
Common mistakes
- Treating every partner request as either fully core-roadmap-worthy or ignored, with no middle path like a skill pack.
- No method for detecting which requests actually recur across partners versus just being loud from one.
- Not closing the loop with partners whose requests were not generalized.
Likely follow-up questions
- How would you handle a request from your most valuable partner that does not generalize?
- What would you do if two overlapping requests conflict in how they should be solved?
- How would you validate the scoring model is producing the right priorities?
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: Discovering and Sizing AI Opportunities
- Chapter 9: Measuring AI Product Economics
- Chapter 14: Interviewing for AI PM Roles