← Warner Bros Discovery Interview Insights

Warner Bros Discovery·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Apr 2026

Summary

System design round at Warner Bros Discovery for what felt like a senior backend or platform engineering role. The prompt was dense but pretty focused once you broke it down.

Questions Asked (1)

Q1

Design a targeted advertising delivery system that supports A/B testing, handles high traffic, enables real-time ad selection, and collects metrics for analysis.

System DesignA/B Testing & ExperimentationProduct Analytics & Metrics
Author's notes

There's a lot packed into this prompt and I think I spent too long on the ad selection logic before touching the A/B testing layer, which is probably the more interesting part for a media company.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements: scale (QPS, latency), ad targeting criteria, A/B testing needs, and metrics. Then design a high-level architecture with separate components for ad selection, experiment assignment, and metrics collection, ensuring scalability and real-time performance. Finally, dive into key components like the ad server, experiment service, and data pipeline, discussing trade-offs and optimizations.

Pro tip: Emphasize the importance of consistent user bucketing for A/B tests and low-latency ad selection; mention using a fast in-memory store like Redis for experiment assignments and ad targeting to meet real-time constraints.

1. Clarify Requirements

Ask about scale (e.g., QPS, latency), targeting criteria, A/B testing granularity, and metrics retention. Define functional and non-functional requirements.

2. High-Level Architecture

Outline main components: ad server, experiment service, targeting engine, metrics collector, and data storage. Explain data flow from ad request to ad delivery and metrics logging.

3. Deep Dive into Key Components

Detail ad selection (e.g., using inverted index for targeting), experiment assignment (consistent hashing), and real-time bidding if applicable. Discuss caching and load balancing for high traffic.

4. Metrics and Analytics

Describe how to collect metrics (impressions, clicks, conversions) via async logging, and how to aggregate for analysis (e.g., using Kafka, Spark, and a data warehouse).

5. Scalability and Trade-offs

Discuss scaling strategies (sharding, replication), latency vs. accuracy trade-offs, and failure handling. Mention monitoring and alerting.

Key Points to Mention

  • Consistent user bucketing for A/B tests using hashing (e.g., user ID mod 100) to ensure stable experiment groups.
  • Low-latency ad selection using in-memory data stores (Redis) and precomputed targeting rules.
  • High throughput and scalability via horizontal scaling, load balancing, and asynchronous processing.
  • Real-time metrics collection with a distributed message queue (Kafka) and stream processing (Flink/Spark Streaming).
  • Data partitioning and storage for analytics (e.g., time-series DB or data warehouse like BigQuery).
  • Trade-offs between latency and accuracy in ad targeting and experiment assignment.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.