Design a Feature Flag for Expedia

Last updated: August 10, 2025

Quick Overview

Design a real-time feature flag system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Expedia
System Design
Software Engineer
Expedia
August 10, 2025
Software Engineer
Technical Screen
System Design
Hard

117

11

3,198 solved


Design a real-time feature flag system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

System design interviews at Expedia typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.

What the Interviewer Expects
  • Drive the design discussion proactively with minimal interviewer guidance
  • Perform detailed capacity estimation and use it to inform design decisions
  • Design for global scale with multi-region deployment and data consistency
  • Deep dive into 2-3 critical components with implementation-level detail
  • Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
  • Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
  • Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
High-level architecture and component design
Caching strategies (local, distributed, CDN)
Message queues and async processing
Partitioning and sharding strategies
Database selection and data modeling
Security and authentication
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • What would the deployment pipeline look like for this system?
  • How would you optimize costs as the system scales?
  • How would you handle a 10x increase in traffic overnight?
  • How would you handle schema migrations with zero downtime?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements Clarification

Before diving into the architecture, clarify the scope with the interviewer. For Feature Flag for Expedia, key functional requirements include: what a...

Capacity Estimation

Estimate the scale to drive design decisions. Assume 100M DAU with an average of 10 actions per user per day = 1B requests/day ~ 12K QPS average, ~36K...


Submit Your Answer
Markdown supported

Related Questions