Design a MapReduce pipeline that processes large-scale scheduling data (users’ busy intervals) to compute common available time slots of at least duration d for specified groups. Define the map outputs (keys/values), partitioning, and reduce logic; explain how you discretize time, mitigate data skew, and validate results at scale.

Design MapReduce for schedule aggregation evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Onsite rounds at Uber.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Uber during technical interviews.

Design MapReduce for schedule aggregation

MapReduce Design: Common Availability From Busy Intervals

Context

You are given large-scale calendar data: each user has 0 or more busy intervals during the day. For a set of specified groups (each group is a set of user IDs), compute the common available time slots whose duration is at least d minutes. Assume all timestamps are normalized to UTC and intervals are half-open [start, end).

Input datasets:

Busy intervals: records (user_id, start_ts, end_ts)
Group membership: records (group_id, user_id)
Query parameter: minimum duration d (minutes)

Output:

For each (group_id, calendar_day), the list of common free intervals of length ≥ d.

Requirements

Define the Map outputs (keys/values), partitioning, and Reduce logic.
Explain how you discretize time (or avoid discretization) and the trade-offs.
Describe how you mitigate data skew (e.g., very large groups, rush-hour hotspots).
Explain how you validate correctness and performance at scale.

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.
If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
State explicit assumptions before making sizing or architecture decisions.
Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers

A scoped requirements summary with concrete non-goals and success metrics.
API, data model, architecture, consistency, capacity, and operations.
Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions

What breaks first at 10x traffic or data volume?
How would you degrade gracefully during dependency failures?
What metrics and alerts would prove the design is healthy after launch?