Design a large-scale A/B Testing Platform

Last updated: February 12, 2026

Quick Overview

Design a event-driven a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Goldman Sachs
System Design
Product Manager
Goldman Sachs
February 12, 2026
Product Manager
Onsite
System Design
Medium

246

12

3,752 solved


Design a event-driven a/b testing system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

System design interviews at Goldman Sachs 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
  • Systematically gather requirements and estimate capacity (QPS, storage, bandwidth)
  • Design a scalable architecture with clear component responsibilities
  • Make well-reasoned database and caching decisions with trade-off analysis
  • Address consistency vs availability trade-offs specific to the use case
  • Discuss partitioning strategy, replication, and data modeling
  • Cover failure handling, monitoring, and alerting strategies
Key Topics to Cover
Partitioning and sharding strategies
Message queues and async processing
Consistency models and replication
Security and authentication
High-level architecture and component design
Requirements gathering and capacity estimation
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
  • How would you handle a region-wide outage?
  • What monitoring and alerting would you set up on day one?
  • How would you implement rate limiting to protect the system?
  • How would you migrate from a monolithic to a microservices architecture?
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 large-scale A/B Testing Platform, key functional requirements include...

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