Architect a fault-tolerant Feature Flag Engine
Last updated: April 20, 2026
Quick Overview
Design a fault-tolerant feature flag system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Doordash
April 20, 2026125
12
3,619 solved
Design a fault-tolerant feature flag system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Doordash asks this during the System Design Round to assess your understanding of the full ML lifecycle. They want to see how you translate a business problem into an ML objective, design the feature pipeline, and plan for model monitoring and retraining.
What the Interviewer Expects
- Design the full ML lifecycle from data collection to model monitoring
- Address cold start, exploration/exploitation, and model freshness
- Discuss multi-objective optimization and ranking systems
- Plan for model debugging, fairness, and bias mitigation
- Design the feature store and training pipeline for scale
- Address model versioning, canary deployments, and rollback strategies
- Discuss the data flywheel and long-term system evolution
Key Topics to Cover
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- How would you ensure fairness and reduce bias in the model?
- What is your model retraining strategy?
- What would you do if model performance degrades over time?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
Functional Requirements
- Dynamic Feature Management: Ability to create, read, update, and delete feature flags in real-time.
- User Targeting: Ability to target users based on attribute...
Capacity Estimation
Assuming DoorDash has 30 million active users, and each user interacts with the feature flag system 5 times a day:
- Total requests per day: 30 million users * 5 requests = 150 million requests/day. ...
Submit Your Answer
