Architect a low-latency A/B Testing Engine
Last updated: March 13, 2026
Quick Overview
Design a low-latency a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Visa
March 13, 202685
7
4,612 solved
Design a low-latency a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Visa 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
- Define clear ML objectives with appropriate loss functions and metrics
- Design a comprehensive feature engineering pipeline
- Discuss model selection with trade-offs (complexity vs interpretability vs latency)
- Plan online and offline evaluation strategies including A/B testing
- Address serving infrastructure: batch vs real-time, latency requirements
- Consider data quality, labeling strategy, and feedback loops
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
- What would you do if model performance degrades over time?
- How would you handle a 10x increase in prediction requests?
- How would you handle the cold start problem?
- How would you debug a model that works well offline but poorly online?
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
- User Segmentation: Ability to segment users based on demographic and behavioral data for targeted A/B tests.
- Experiment Setup: Provide an interface for produc...
Capacity Estimation
Assuming Visa processes approximately 24 million transactions daily, we can estimate the request volume for our A/B testing engine:
- Requests per Second (RPS): 24 million transactions / 86,400 ...
Submit Your Answer
