Strategy question

A strategic customer asks for a technically complex feature that would materially improve their workflow but may not generalize across Sierra’s broader customer base. How would you evaluate whether to build it into the platform, support it as a customer-specific solution, defer it, or solve the need through a different product or process change?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Whether you can evaluate a customer-specific request against platform generalizability using a clear, repeatable decision framework.

Assess how much the feature's value depends on this specific customer's workflow versus a broader pattern, by checking if similar requests exist in the backlog from other accounts.
Weigh the deal or relationship value of building it against the platform cost of maintaining a one-off, especially the ongoing burden of supporting custom logic as the core product evolves.
Consider three options explicitly: build it into the platform if it generalizes, support it as a scoped customer-specific solution (configuration or a services layer) if it does not, or defer and solve the underlying need differently, for example through better documentation or a workflow change.
Validate the generalization hypothesis by asking a couple of other strategic accounts if the same capability would be valuable to them, rather than assuming based on one data point.
Make the call using both the validation result and the deal value, choosing the platform path only when both generalization evidence and reach justify the investment.
Communicate the decision and reasoning back to the customer clearly, especially if declining full platform integration, so the relationship stays strong even if the ask is scoped down.

Names three distinct resolution paths, build, scope as customer-specific, or defer, rather than treating this as binary.
Proposes validating generalizability with other accounts before committing, avoiding a roadmap built on one customer's ask.
Weighs ongoing maintenance cost of a one-off as a real, ongoing cost, not just a one-time build cost.
Closes with a clear communication plan back to the customer, preserving the relationship regardless of the outcome.

Deciding based only on the customer's insistence without checking generalizability.
Treating build-or-not as the only two options, missing the scoped customer-specific path.
No plan to communicate the reasoning back to the customer.

How would you validate generalizability without over-promising to the other accounts you ask?
What would you do if the customer refuses a scoped solution and demands full platform integration?
How would you decide the maintenance cost of a customer-specific solution is acceptable?