A team says the golden path cannot support their workload and wants to build their own deployment tooling. How do you respond?
Show the full answer Hide the answer
What the interviewer is testing
Whether you treat this as a governance confrontation or as product feedback, and whether you have a defensible position on when leaving the path is legitimate.
The response
Find out what the actual gap is first. In most cases it is one specific capability — a sidecar the platform does not support, a scaling behaviour, a network requirement, a startup dependency. The team has concluded that means building everything, when it means the platform is missing one thing.
If the gap is genuinely narrow, the right outcome is usually to extend the platform, and the team's requirement becomes a prioritised backlog item with a date.
If it is genuinely unusual, leaving the path must remain possible. A platform that permits no exceptions gets routed around covertly, which is worse — you lose visibility as well as consistency.
The terms of leaving
Make the deal explicit rather than adversarial:
| The platform was providing | Off-path, the team now owns |
|---|---|
| Pipeline, scanning, policy checks | Their own, meeting the same standards |
| Telemetry, dashboards, alerting | Their own, emitting the same signals |
| Secrets, identity, network policy | Their own, passing the same compliance checks |
| Patching of base images and runtime | Their own currency and vulnerability response |
| On-call support for the deployment layer | Themselves |
The non-negotiables are the outcomes — policy compliance, telemetry, audit evidence — not the mechanism. That distinction is what makes the position defensible.
What a strong answer adds
Tracking off-path teams as a platform product metric. A rising number means the path is missing capability; a stable small number of genuinely unusual workloads is healthy. Also: revisit the decision periodically, since the platform may acquire the capability and the team may be glad to return once migration is cheap.
Common weak answers
Refusing on the grounds of standards, which produces shadow tooling. Approving with no conditions, which loses compliance coverage.