Design a large-scale A/B Testing Platform

Last updated: May 24, 2026

Quick Overview

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

LinkedIn
System Design
Software Engineer
LinkedIn
May 24, 2026
Software Engineer
Onsite
System Design
Hard

326

12

1,613 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 LinkedIn 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
Message queues and async processing
Load balancing and horizontal scaling
High-level architecture and component design
Consistency models and replication
Failure handling and fault tolerance
Caching strategies (local, distributed, CDN)
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 monitoring and alerting would you set up on day one?
  • What would the deployment pipeline look like for this system?
  • How would you migrate from a monolithic to a microservices architecture?
  • How would you handle a region-wide outage?
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