Strategy question
Multiple enterprise customers want different workflow capabilities for their agents, but engineering capacity is limited. How would you decide which requests become reusable platform features, which stay customer-specific, and how that decision shows up on the roadmap?
- 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 prioritization discipline under fixed engineering capacity across multiple competing enterprise requests, and how that shows up concretely on the roadmap.
How to approach it
- Log every request with the requesting account, the underlying capability needed, and estimated build effort, rather than tracking requests as unstructured asks.
- Group requests by underlying capability, not surface wording, since different customers often describe the same need differently.
- Score each capability group on account count, revenue at stake, and reusability across the customer base.
- Set a clear bar: capabilities requested by multiple accounts with high reuse potential go on the roadmap; single-account asks go to configuration or services.
- Publish the roadmap decision with the reasoning visible to account teams, so 'no' decisions are explainable, not silent.
- Revisit the backlog of deferred single-account asks quarterly, since patterns emerge as the customer base grows.
What a strong answer includes
- Groups requests by underlying capability rather than surface wording, catching hidden overlap across accounts.
- Sets an explicit bar, multi-account demand plus reuse potential, for what earns a roadmap slot.
- Makes deferred decisions explainable to account teams instead of a silent no.
Common mistakes
- Tracking requests as a flat list without grouping by underlying capability.
- Making prioritization calls with no visible reasoning for account teams to understand.
Likely follow-up questions
- How would you handle an account threatening to churn over a deprioritized request?
- How often would you re-score the backlog as new requests come in?
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
- 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
More questions from Sierra
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