What are feature flags, and how do they decouple deployment from release?
What they are really testing: Whether you understand shipping code dark and turning features on independently, enabling gradual rollout, instant kill switch, and trunk-based development, plus the cost (flag debt).
A real interview question
What are feature flags, and how do they decouple deployment from release?
What most people say
drag me
“Feature flags let you turn features on and off in the app.”
It states the mechanism but not the value: decoupling deploy from release, gradual rollout, an instant kill switch, and enabling trunk-based development, nor the cost (flag debt). The why is what the question is after.
The follow-ups they ask next
Why is a feature flag faster than a rollback for disabling a broken feature?
Flipping a flag is a runtime config change, instant, with no build or deploy. A rollback requires redeploying a previous version. The kill switch restores safe behavior in seconds.
What is flag debt and how do you manage it?
Stale flags and the conditional branches around them accumulating in the code, adding complexity and risk. Manage it by treating flags as temporary: track them and remove each once its feature is fully rolled out and stable.
What the interviewer is listening for
- Decouples deploy from release
- Gradual rollout + instant kill switch + enables trunk-based
- Acknowledges flag debt / cleanup
What sinks the answer
- Only "toggle features"
- No decouple/rollout/kill-switch value
- Unaware of flag debt
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.
“A feature flag [toggles a feature at runtime without a deploy], decoupling [deployment (code shipped, dark) from release (feature turned on)]. It enables [gradual rollout to a cohort then ramp, an instant kill switch (faster than rollback), and trunk-based dev with unfinished work behind off flags]. Cost: [flag debt], so remove flags once fully rolled out.”
Keep going with deployment
Foundation
What do CI and CD actually mean, and what is the difference between continuous delivery and continuous deployment?
Foundation
Why should you build an artifact once and promote the same one through environments?
Junior
What stages should a good CI/CD pipeline have?
Junior
A deploy went bad in production. How do you handle rollback, and how do you make rollback easy?
Mid
Compare blue-green and canary deployments. When would you reach for each?
Mid
How does your branching strategy affect continuous delivery? Trunk-based versus long-lived branches.
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