Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
10 results for “Feature Flags”
Feature Flag
A runtime switch that decouples deploying code from releasing behaviour, so unfinished or risky work can ship dark.
Feature Parity Trap
The expectation that a replacement system must match every behaviour of the old one before it can be adopted, which is what makes rewrites never finish.
Booking.com's Experimentation Platform
Booking.com runs over a thousand concurrent experiments and treats the ability to test any change safely as a platform capability rather than a product feature.
Build vs Buy
The choice between developing a capability in-house and acquiring it, decided on differentiation and total cost rather than on feature lists.
Error Budget
The amount of unreliability an SLO permits, treated as a resource that feature velocity spends.
Knight Capital lost roughly $460M in 45 minutes in 2012 after a deployment reached seven of eight servers. Which architectural failures made that possible, and which one would you fix first?
The case, as publicly reported Per the SEC's 2013 order, Knight Capital deployed new order routing code to eight production servers ahead of a NYSE programme la
An LLM feature that worked last week now gives worse answers. Nothing was deployed. How do you find out what changed, and what should have been in place?
What the interviewer is testing Whether you treat an AI feature as a system with configuration and dependencies, or as a black box that mysteriously drifts. Wha
Feature Flags
Decoupling deploy from release, with an expiry date.
Error Budgets
Unreliability as a resource that feature velocity spends.
ML Platform
Feature stores, training pipelines, registries and deployment.