Strategy question
A neobank wants a bespoke servicing workflow feature, while Sierra engineering argues for a generalized API and orchestration capability that could serve multiple financial-services customers. How would you decide what to build now versus later, and how would you explain that decision to both the customer and the team?
- 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 decision between a bespoke customer feature and a generalized platform capability, and explaining it to both the customer and the team.
How to approach it
- Assess the neobank's request for genuine specificity: is this workflow truly unique to their servicing model, or a specific instance of a broader financial-services pattern.
- Weigh engineering's generalized-API argument on reuse potential across other financial-services customers, not just theoretical elegance.
- Estimate timeline cost for both paths honestly, since a generalized API likely takes longer and the neobank has a real deadline.
- If the underlying need is genuinely common across financial-services customers, build the generalized capability but scope a fast, minimal version of it to hit the neobank's timeline.
- If the need is truly neobank-specific, build the bespoke feature but document why generalization was rejected, to avoid relitigating the decision later.
- Explain the same decision differently: to the neobank, focus on their timeline being met; to engineering, focus on the reuse case or the documented reason it was not pursued.
What a strong answer includes
- Tests genuine specificity of the request before assuming either 'build bespoke' or 'engineering is right' by default.
- Proposes a minimal-but-generalized version as a way to meet both the timeline and reuse goals when the need is genuinely common.
- Adapts the explanation for each audience, timeline for the customer, reuse logic for engineering, without changing the underlying decision.
Common mistakes
- Defaulting to engineering's generalized preference without checking urgency and true reuse potential.
- Building fully bespoke without documenting why generalization was rejected, inviting the same debate later.
Likely follow-up questions
- How would you handle it if the neobank later insists on features assuming a generalized API you did not build?
- What would you do if scoping a minimal generalized version still missed the deadline?
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