How do you handle feature flags?

Answer

A scalable React codebase groups code by feature, gives UI a clear data boundary, and keeps business rules independent from framework details. Tests should focus on visible behaviour and critical integration paths.

For How do you handle feature flags?, start with the rule or behaviour, then anchor it in a small realistic example. Distinguish the default approach from the exceptions and name the observable outcome: correctness, maintainability, accessibility, performance, or security.

Example

function UserPage({ userId, api }) {
  const user = useUser(userId, api)
  return <UserProfile user={user} />
}

Keep data access in a hook or boundary and make the display component easy to reuse and test.

How to structure your answer

1. Define the concept in one or two sentences.
2. Explain when you would use it and when you would choose an alternative.
3. Walk through a small example, including an edge case.
4. Close with how you would test or measure the result.

Common mistakes

• Repeating a definition without connecting it to real code.
• Treating an optimization or abstraction as a default rather than a trade-off.
• Omitting lifecycle, error, cleanup, accessibility, or testing considerations when they apply.

Follow-up prompts

• What failure mode would you expect if this were implemented incorrectly?
• How would you test this behaviour?
• What changes when the feature must scale to a larger application or team?

Interview tip

For this hard-level question, narrate your assumptions before coding. Interviewers can assess reasoning from a clear, bounded example much better than from a list of APIs.