Design Breakout Rooms - System Design | WinJob

Problem framing and constraints

This section covers problem framing and constraints for global breakout rooms in video conferencing products. The interviewer expects explicit constraints, numerical assumptions, and operationally realistic failure handling. I therefore present decisions using three lenses: user experience, systems reliability, and platform cost.

Constraints

Millions of concurrent sessions
Bursty room-moves during live events
Strict permission checks before every rejoin
Malware and policy reconciliationning requirements
Geo-distributed latency expectations

Design Choices

Keep metadata transactional in control-plane services.
Keep raw file transfer on room-state store and CDN path.
Emit deterministic events for downstream indexing and previews.
Apply idempotent APIs for initiate and completion lifecycle.
Add queue-based workers for reconciliationning and preview generation.

Java

javaOne Dark Pro

1 public final class CompleteRoom-moveUseCase {
2   public String execute(String sessionId, String operationId) {
3     if (sessionId == null || operationId == null) {
4       throw new IllegalArgumentException("required");
5     }
6     return sessionId + "::" + operationId;
7   }
8 }

Python

pythonOne Dark Pro

1 from dataclasses import dataclass
2  
3 @dataclass
4 class MoveCompletionInput:
5     session_id: str
6     idempotency_key: str
7  
8 def complete_room-move(inp: MoveCompletionInput) -> str:
9     """Returns deterministic completion token for safe retries."""
10     if not inp.session_id or not inp.idempotency_key:
11         raise ValueError("required")
12     return f"{inp.session_id}::{inp.idempotency_key}"

TypeScript

typescriptOne Dark Pro

1 export interface MoveCompletionInput {
2   sessionId: string;
3   operationId: string;
4 }
5  
6 export function completeRoom-move(input: MoveCompletionInput): string {
7   if (!input.sessionId || !input.operationId) throw new Error('required');
8   return input.sessionId + '::' + input.operationId;
9 }

Operational Validation

Alert when complete-room-move error rate breaches 1%.
Alert when reconciliationner lag exceeds SLA for 10 minutes.
Alert when room assignment token denial spikes by tenant.
Track p50/p95/p99 for initiate, complete, and rejoin auth paths.

Interview Delivery

In phase understanding, I present assumptions first, then architecture, then failure containment, and finally trade-offs with measurable impact.

Why interviewers care

Breakout Rooms interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

The failure that defines the design

The outage to narrate is the participant stuck in limbo between rooms. The host opens breakouts, the participant leaves the main room's media session, and then the join to their assigned breakout fails — so they sit on a black screen with no audio, in no room at all. Multiply that by a flaky network across a 200-person class and you have dozens of people lost on every open. The fix is the spine of the design: treat room assignment, not media, as the source of truth, and model the move as an idempotent, reversible state machine carrying a room-assignment token, so a failed join rolls back to the source room and a reconnect lands the participant exactly where they belong. State assignment-first orchestration up front, because a breakout system is a state-machine problem wearing a video-call costume.

Key Highlights

•Lead with constraints
•Defend trade-offs with numbers
•Cover failures and recovery

1	public final class CompleteRoom-moveUseCase {
2	public String execute(String sessionId, String operationId) {
3	if (sessionId == null \|\| operationId == null) {
4	throw new IllegalArgumentException("required");
5	}
6	return sessionId + "::" + operationId;
7	}
8	}

1	from dataclasses import dataclass
2
3	@dataclass
4	class MoveCompletionInput:
5	session_id: str
6	idempotency_key: str
7
8	def complete_room-move(inp: MoveCompletionInput) -> str:
9	"""Returns deterministic completion token for safe retries."""
10	if not inp.session_id or not inp.idempotency_key:
11	raise ValueError("required")
12	return f"{inp.session_id}::{inp.idempotency_key}"

1	export interface MoveCompletionInput {
2	sessionId: string;
3	operationId: string;
4	}
5
6	export function completeRoom-move(input: MoveCompletionInput): string {
7	if (!input.sessionId \|\| !input.operationId) throw new Error('required');
8	return input.sessionId + '::' + input.operationId;
9	}