A few teams want an internal feature-flag and config service. You could build one on top of your cloud primitives or buy a SaaS. How do you make the build-vs-buy call for a platform capability the whole org will depend on?
What they are really testing: Whether you reason about total cost of ownership, opportunity cost, and lock-in over years, or just compare a license price to a sprint estimate. Platform decisions are bets that other teams will inherit.
A real interview question
A few teams want an internal feature-flag and config service. You could build one on top of your cloud primitives or buy a SaaS. How do you make the build-vs-buy call for a platform capability the whole org will depend on?
What most people say
drag me
“I would scope both options, estimate the engineering effort to build it, compare that to the annual license, and pick whichever is cheaper. Building gives us full control, so if it is close I would build it.”
Optimizes for a one-time cost comparison and a "control" instinct. It ignores the multi-year carrying cost, opportunity cost of the team, and whether this is even worth differentiating on.
The follow-ups they ask next
The vendor doubles its price at renewal. What did you put in place a year ago to keep that from being a crisis?
Listen for the abstraction layer and exit plan they built before they needed it.
Leadership wants to build it for prestige even though buying is clearly right. How do you handle that?
Listen for reframing around opportunity cost and outcomes rather than ego, and willingness to disagree well.
What the interviewer is listening for
- Defaults to buy for undifferentiated capability and reserves build for what is strategic
- Reasons in total cost of ownership and opportunity cost, not sticker price
- Designs for reversibility with an abstraction layer and an exit plan
- Treats long-term ownership as a precondition, not an afterthought
What sinks the answer
- Compares only build effort to license cost
- Builds by default to keep control
- No plan for who owns and patches a built system over years
- Treats the decision as permanent with no review trigger
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“For [capability], I would first ask if it is [differentiating or undifferentiated]. My default is to [build or buy] the latter. I compare [total cost of ownership including ___] rather than just [sticker price], and I make it reversible by [abstraction or exit plan]. I only build if [a team can own it for years], and I record the call as [an ADR with a review date].”
Keep going with strategy & leadership
Principal
You are asked to lead the migration of 200 services to the cloud. What is your strategy and how do you de-risk it?
Principal
You have 30 teams each spinning up cloud infrastructure their own way, with wildly different quality. How do you establish golden paths or paved roads so teams stop reinventing the wheel without grinding delivery to a halt?
Principal
Cloud spend is growing faster than revenue and leadership wants it under control across dozens of teams. How do you set up org-wide cost governance, or FinOps, without turning into the team that says no to everything?
Principal
Design a globally distributed, multi-region active-active system. Walk me through the hard parts.
Principal
The org is moving to many cloud accounts across many teams. How do you design the multi-account landing zone and guardrails so teams move fast safely, instead of locking everything down or letting it become the wild west?
Principal
Design a global rate limiter that protects your APIs across many regions, enforcing per-customer quotas. Walk me through the design and, more importantly, the trade-offs you would make and how you would sequence building it.
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free