CI/CD · Ship safely, repeatedly

How do feature flags change the deployment model?

Mediumfeature flagsreleaserollbackUpdated Oct 2026
Quiz this track

Short answer

Feature flags separate deployment from release, so code can ship dark and be enabled later for selected users. They also provide a fast kill switch, but stale flags become technical debt and must be removed.

Without flags, deploying a change and exposing it are the same event. With flags, the artifact can reach production while the behaviour stays off, which lets teams deploy continuously and release on a product schedule.

  • Release flags hide unfinished features and are removed after rollout
  • Ops flags act as kill switches for risky dependencies or behaviour
  • Experiment flags split traffic to measure an outcome and need an owner and end date
  • Permission flags target cohorts such as internal users or a region
  • Every flag needs a default, an owner and a removal plan
js
function renderCheckout(user) {
  if (flags.isEnabled('checkout-v2', user)) {
    return renderCheckoutV2(user);
  }
  return renderCheckoutV1(user);
}
Flag debt is real. A codebase with hundreds of abandoned flags is hard to reason about, so treat stale flags as defects and review them on a schedule.

Follow-ups you should expect

Interviewers use these to check whether the first answer was understanding or memorisation.

  1. 1What types of feature flags have you used?
  2. 2How do you prevent flag debt?
  3. 3What happens if the flag service is unavailable?
  4. 4How do flags interact with canary deployments?

Say it in the interview

Feature flags decouple deploying code from releasing behaviour. I can merge and deploy unfinished work behind a default-off flag, then enable it for internal users, a percentage of traffic or a region. They are also a fast rollback lever when a release goes wrong. The cost is combinatorial complexity and stale flags, so each flag has an owner and a removal date.

Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.

Related questions

Reading is step one

Now say it out loud.

Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live CI/CD mock interview and get scored feedback on depth, clarity and confidence.