Strategy question
A flagship customer needs a capability Sierra's platform does not support today. Building it as a reusable platform feature would take significant investment and slow other roadmap commitments, while a customer-specific workaround could ship faster but create long-term maintenance cost. How would you decide which path to take, and what criteria would you use to make the call?
- 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 the build-now-versus-workaround decision for a flagship customer capability gap, using reusability and long-term cost as the deciding criteria.
How to approach it
- Quantify the workaround's true cost, not just build time, but ongoing maintenance burden and the risk of it breaking as the platform evolves.
- Estimate the reusable feature's demand beyond this customer by checking whether other accounts have hinted at a similar need.
- Weigh the flagship customer's deal timeline against the platform feature's build timeline honestly, since a workaround may still be needed as a bridge either way.
- If reuse potential is high, build the platform feature but scope a minimal workaround as a bridge to avoid missing the customer's timeline.
- If reuse potential is low, take the workaround but cap its scope tightly and document it as technical debt with an owner.
- Revisit the decision if a second customer requests the same capability, since that should trigger the platform investment.
What a strong answer includes
- Compares true long-term cost, not just build time, between the workaround and the reusable feature.
- Proposes a bridge strategy, workaround now plus platform build in parallel, rather than treating it as strictly either-or.
- Sets a concrete trigger, a second customer request, for revisiting a workaround-now decision.
Common mistakes
- Comparing only build time and ignoring workaround maintenance cost.
- Treating the decision as permanent instead of revisiting it as more data arrives.
Likely follow-up questions
- How would you estimate reuse potential before another customer actually asks for it?
- What would you do if the workaround becomes load-bearing for the customer long term?
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