Requirements Clarification

Introduction

Requirements clarification is the first 5 minutes of every system design interview and every production RFC. Scope ambiguity causes over-engineering and under-engineering alike.

The story

An engineer designed a global video platform assuming live streaming. The product needed VOD only. She spent 20 minutes on WebRTC before the interviewer redirected. Clarifying "live vs on-demand" would have led straight to CDN + object storage.

The business problem

Teams that skip disciplined Requirements Clarification thinking pay in outages, cost overruns, and failed interviews:

• Outages: components chosen without scale math fail at peak.
• Cost: over-engineered microservices for 100-user products.
• Latency: missing cache/CDN/replica on read-heavy paths.
• Interviews: boxes without numbers and trade-offs don't hire.

The problem teams faced

This lesson addresses:

• When and why Requirements Clarification matters in real architectures.
• How to sketch components and data flows under interview time pressure.
• Trade-offs vs alternatives — what senior engineers articulate aloud.
• Production patterns and failure modes you've seen or will see.

Understanding the topic

Core idea: Requirements Clarification in production system design.

• Problem — what force this topic addresses.
• Building blocks — components typically involved.
• Trade-offs — what you gain and what you pay.
• Interview — how this appears in design loops.

Internal architecture

Requirements Clarification — system view:

Interview / RFC opening
   ↓
Who are the users? What core actions?
   ↓
Scale numbers (DAU, QPS, storage)
   ↓
Consistency & latency expectations
   ↓
Out of scope (explicit "no" list)

Visual explanation

Three diagrams: architecture flow, design process, and scaling lens:

Informative example

Example — Requirements Clarification:

Clarifying questions for "Design Instagram":
1. Feed home timeline or stories or DMs? (pick one to deep-dive)
2. Read-heavy? (yes → cache + fan-out)
3. Strong consistency on likes? (usually eventual OK)
4. Global or single region first?

Execution workflow

Real-world use

Used in production at major tech companies and every FAANG system design interview loop. Patterns align with AWS/GCP well-architected frameworks and Google SRE practice.

Production case study

An engineer designed a global video platform assuming live streaming. The product needed VOD only. She spent 20 minutes on WebRTC before the interviewer redirected. Clarifying "live vs on-demand" woul…

• Context: production or interview scenario from this lesson.
• Decision: component and trade-off choices explained.
• Outcome: measurable latency, availability, or cost impact.

Trade-offs

• Pro: structured approach reduces outages and interview failures.
• Con: upfront thinking takes time — faster than wrong rebuild.
• Con: every product has unique constraints — adapt templates.

Decision framework

• Always estimate before drawing microservices.
• Match consistency model to business domain (money vs likes).
• Document rejected alternatives — ADR or interview closing.

Best practices

• State assumptions explicitly (DAU, read:write ratio).
• Draw async vs sync paths with different line styles.
• Close with monitoring and on-call failure modes.

Anti-patterns to avoid

• Jumping to Kafka and microservices without scale justification.
• Single DB box with no read replica or cache on read-heavy design.
• Ignoring idempotency on write APIs with retries.

Common mistakes

• Underestimating peak QPS (forgetting peak factor).
• Hot shard from poor partition key choice.

Debugging tips

• Trace one request ID through diagram — find missing component.
• Ask "what fails first at 10×?" for every design.

Optimization strategies

• Cache + CDN first for read-heavy; shard when single DB saturates.
• Async queue for slow side effects (email, analytics).

Common misconceptions

• More components ≠ better design — simplest meeting NFRs wins.
• Interviews test process — not memorizing Netflix architecture.

Advanced interview questions

Summary

You can explain Requirements Clarification in a 45-minute system design interview with numbers, diagrams, and trade-offs. Teach it back without notes — you own this piece.