Strategy question
Several enterprise customers are simultaneously requesting custom agent features, but engineering capacity is limited. How would you decide what goes onto Sierra’s roadmap, what gets solved through configuration or services, and what should remain customer-specific so the platform becomes more reusable over time?
- 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 roadmap triage across multiple simultaneous enterprise requests under limited engineering capacity, and building durable reusability over time.
How to approach it
- Log every request by underlying capability rather than surface phrasing, since similar needs are often described differently by different customers.
- Score each capability cluster on account count, revenue at stake, and reusability across the broader customer base.
- Reserve roadmap slots for capability clusters with multi-account demand and high reuse; route single-account asks to configuration or professional services instead.
- Build genuinely reusable capabilities as configurable platform features rather than one-off code paths, even under time pressure.
- Communicate the triage decision transparently to each account team, including why some requests were routed to services rather than roadmap.
- Review the routed-to-services backlog periodically, since accumulating similar service requests is itself a signal to promote a capability to the roadmap.
What a strong answer includes
- Clusters requests by underlying capability, surfacing hidden overlap that raw request counting would miss.
- Routes single-account asks to services deliberately, using that channel as a controlled way to increase reusability over time.
- Reviews the services backlog periodically as an intentional feedback loop into future roadmap decisions.
Common mistakes
- Prioritizing by which account is loudest rather than by demand clustering and reuse potential.
- Treating professional services as a dumping ground with no feedback loop back to product.
Likely follow-up questions
- How would you handle a high-revenue account whose request scores low on reuse?
- How often would you revisit the roadmap given how fast 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