Feature Flag Types and Use Cases

Can you walk me through the different types of feature flags and when you'd use each one?

CI/CDintermediate

// interview question

Can you walk me through the different types of feature flags and when you'd use each one?

Sample answer

There are four main types of feature flags, each serving a different purpose. Release flags control the rollout of new features to users. They're temporary and should be removed once the feature is fully released. Example: rolling out a new search UI to 10% of users first. Ops flags are operational toggles for runtime control. They're semi-permanent and used to manage system behavior without redeploying. Example: a kill switch to disable a non-critical service under heavy load. Experiment flags support A/B testing. Users are consistently placed in the same group so you can measure outcomes. Example: testing whether a one-click checkout increases conversion. Permission flags control access to features based on user attributes like subscription tier, region, or role. They're long-lived and tied to business logic. Example: premium features only available to paying users. The important thing is to treat release flags differently from the others. Release flags are technical debt the moment the rollout is complete. You should have a process to clean them up within days, not months.

Why this matters

This question reveals whether a candidate has practical experience with feature flags beyond basic on/off toggles. Look for awareness of flag lifecycle management, especially cleanup of release flags. Experienced candidates will mention that stale flags are a real operational risk and talk about how they've managed flag hygiene.

Code examples

LaunchDarkly-style flag definitions showing different types

yaml

# Release flag - temporary, remove after full rollout
new-payment-page:
  type: release
  variation: boolean
  targets:
    - percentage: 25
  expiry: 2026-04-30        # Alert if still active after this date

# Ops flag - semi-permanent kill switch
disable-recommendations:
  type: ops
  variation: boolean
  default: false            # Flip to true during incidents

# Experiment flag - A/B test with consistent bucketing
checkout-button-color:
  type: experiment
  variation: ["blue", "green", "orange"]
  bucketing: user-id         # Same user always sees the same variant

# Permission flag - long-lived, tied to business rules
advanced-analytics:
  type: permission
  rules:
    - attribute: plan
      operator: in
      values: ["pro", "enterprise"]

Script to find stale feature flags that should be cleaned up

bash

#!/bin/bash
# Find release flags older than 30 days that are at 100% rollout
# These are candidates for removal

echo "Stale release flags (fully rolled out > 30 days):"
for flag_file in flags/release-*.yaml; do
  created=$(yq '.created' "$flag_file")
  percentage=$(yq '.rollout.percentage' "$flag_file")
  age_days=$(( ($(date +%s) - $(date -d "$created" +%s)) / 86400 ))

  if [[ "$percentage" == "100" && "$age_days" -gt 30 ]]; then
    echo "  WARNING: $(basename $flag_file) - $age_days days old, 100% rolled out"
  fi
done

Common mistakes to avoid

Treating all feature flags the same without distinguishing release flags from long-lived permission flags
Never cleaning up release flags after full rollout, leading to code full of dead branches
Not considering that experiment flags need consistent user bucketing to produce valid results

Likely follow-ups

How would you prevent stale feature flags from piling up in your codebase?
What's the risk of having hundreds of active feature flags at once?
How do you test all the different flag combinations?
Would you store feature flags in your code repo or use a dedicated service?

Answer out loud first, then check yourself against the model answer.

Practice all Mid-Level questions More CI/CD questions

#feature-flags#progressive-delivery#ci-cd#release-management#a-b-testing

More CI/CD interview questions

Also worth your time on this topic

Interview

Progressive Delivery Basics

What is progressive delivery and how does it differ from traditional continuous delivery?

junior

Checklist

How to Implement Progressive Delivery with Feature Flags

A step-by-step checklist for implementing progressive delivery using feature flags, canary releases, and gradual rollouts so you can ship to production without breaking things.

45-90 minutes

Article

How to Implement Progressive Delivery with Feature Flags

Learn how to implement progressive delivery using feature flags, canary releases, and gradual rollouts to ship changes safely in production without risking your entire user base.