When would you tell a company not to use Kubernetes?
What they are really testing: Whether you can argue against the technology you are hired for. Candidates who cannot name a case where their specialism is wrong tend to over-engineer everything.
A real interview question
When would you tell a company not to use Kubernetes?
What most people say
drag me
“Kubernetes is the industry standard, so almost every company should use it eventually.”
It defers to popularity instead of reasoning about cost and benefit, and it is the mindset that puts a 3-service startup on a self-managed cluster where one engineer ends up permanently maintaining infrastructure instead of building product.
The follow-ups they ask next
What signals tell you a company has grown into needing it?
Enough services that per-service infrastructure is duplicated everywhere, teams blocked waiting on each other for environments, genuine bin-packing or scaling economics, and someone whose actual job is platform.
Managed Kubernetes removes the control plane burden. Does that change your answer?
It helps but only removes part of it. Networking, RBAC, upgrades of workloads, admission control and the debugging skill requirement all remain, and those are most of the real cost.
What the interviewer is listening for
- Argues against their own specialism credibly
- Names concrete simpler alternatives
- Frames containerising as the reversible investment
What sinks the answer
- Cannot name a case against it
- Appeals to industry standard
- Ignores team size and skills
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.
“Kubernetes is [a permanent operational commitment: upgrades, networking, RBAC, and a debugging skill everyone needs]. It pays off with [many services, real elasticity, multiple teams needing self-service]. With [3 services and 6 engineers] the cost dominates, so [a managed container service is better]. [Containerising is the durable, transferable investment.]”
Keep going with strategy
Principal
You join a 200-engineer company where every team built its own deployment tooling. What is your strategy?
Principal
The business wants faster shipping, your on-call team is burning out from incidents. How do you resolve that?
Principal
Your team wants to build an internal developer platform. A vendor sells one. How do you decide?
Principal
Tell me about a time you argued against your own proposal or changed your mind on a significant technical decision.
Principal
One slow dependency takes down your entire system. Why does that happen and how do you prevent it?
Principal
Design multi-region failover for a system that currently runs in one region, targeting 15 minutes recovery.
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