Strategy question
Three enterprise customers request similar capabilities, but each wants different workflow details. How would you decide whether to build a one-off feature, create a reusable platform capability, or advise a process workaround instead, and what criteria would drive the roadmap decision?
- Sierra
- 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
Tests deciding between a one-off feature, a reusable platform capability, or a process workaround for similar-but-different customer requests, using clear roadmap criteria.
How to approach it
- Map the shared underlying need across the three customers versus their specific workflow variations, since a common capability with configurable details often serves all three better than three separate one-offs.
- Check if the difference between requests is truly structural, needing new product capability, or just configuration, workflow ordering or terminology that could be solved without new engineering.
- Consider a process workaround, for example a documented configuration pattern or professional-services setup, when the request is genuinely one customer's edge case with low reuse potential.
- Build a reusable platform capability when the shared need is common enough that solving it generically avoids repeating this same conflict with the next three customers.
- Score each option on engineering cost, revenue or relationship risk if declined, and how often this exact pattern is likely to recur across the customer base going forward.
- Decide and communicate clearly to each customer whether their specific detail is met through the platform capability's configuration options or requires a workaround, setting expectations before building.
What a strong answer includes
- Separates structural differences, needing new capability, from configuration differences, solvable without engineering, before deciding what to build.
- Weighs recurrence likelihood explicitly, recognizing this same conflict will resurface with new customers if the underlying need isn't generalized.
- Proposes a process workaround as a legitimate, deliberate option for a genuine one-off, not just an engineering-avoidance shortcut.
- Commits to clear customer communication about what a shared platform capability will and won't cover for their specific request.
Common mistakes
- Building three separate one-off features instead of checking for a common underlying capability.
- Defaulting to a full platform build even for a genuinely rare, one-customer edge case.
- Deciding the roadmap path without communicating clearly to customers what their request will actually receive.
Likely follow-up questions
- How would you decide if a workaround is a permanent or temporary solution?
- What would change your decision if a fourth customer made the same request next month?
More strategy questions
- Sierra uses outcome-based pricing. How would you design and defend that model?Sierra · Strategy · Hard
- How would you handle a Sierra agent giving a customer wrong information that costs the client money?Sierra · Strategy · Hard
- How should Sierra compete with Decagon and incumbent CX vendors like Zendesk?Sierra · Strategy · Hard
- Traffic is growing, p95 agent latency is degrading, and GTM is asking for faster delivery of customer-specific features. As PM for Infrastructure, how would you decide what to do in the next quarter: performance work, reliability hardening, cost optimization, or platform investments that unblock product teams? Walk through the framework, inputs, and tradeoffs you would use to make and defend that prioritization.Sierra · Strategy · Hard
- You have separate 30-minute meetings with a CIO and an engineering lead at the same prospect. How would you change the demo, proof points, and objections you address for each audience while keeping the core product story consistent?Sierra · Strategy · Medium
- Early design partners want very different things from the SDK: one wants deep customization, one wants the fastest possible integration, and one wants better monitoring and debugging tools. With limited engineering capacity, how would you decide what to build first?Sierra · Strategy · Medium
More questions from Sierra
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