How to gather and clarify requirements effectively in a system design interview.
Finished this lesson?
Sign in to save your progress across devices.
Tip: use ← and → to move between lessons.
Was this lesson helpful?
Rehearse this with a Staff+ engineer
45-minute mock with a Staff+ engineer who interviews at your target company. Premium members save $20.
The first few minutes of a system design interview are critical. How you gather requirements sets the tone for the entire interview and demonstrates your ability to think systematically about problems.
Many candidates rush to start drawing boxes and arrows immediately. This is a mistake. Without clear requirements, you might:
Spending 5-10 minutes on requirements is time well spent. It's easier to adjust your approach early than to redesign halfway through.
Functional requirements describe what the system should do. These define the core features.
Non-functional requirements describe how the system should behave. These are equally important.
Use this framework to systematically gather requirements:
"Let me start by understanding who uses this system.
Are we designing for end consumers, businesses, or both?"
"What are the 2-3 most important features we need to support?
I want to make sure we focus on the right things."
"What scale are we designing for?
Millions of users? Billions of requests per day?"
"Are there any specific constraints I should know about?
Latency requirements, consistency needs, regional requirements?"
What interviewers expect varies by your target level:
| Requirements Gathering Expectations by Level | |
|---|---|
| Name | Description |
| Mid-Level (L4) | Ask 3-5 clarifying questions covering users, core features, and basic scale. State assumptions clearly. Time: 3-5 minutes. |
| Senior (L5) | Proactively scope the problem. Identify functional vs. non-functional requirements. Discuss trade-offs (consistency vs. availability). Time: 5-7 minutes. |
| Staff+ (L6+) | Frame requirements in business context. Anticipate constraints interviewer hasn't mentioned. Propose phased approach (MVP vs. full system). Time: 5-10 minutes. |
| Engineering Manager | Focus on stakeholder needs and success metrics. Consider team implications and delivery phases. Connect technical requirements to business outcomes. |
Don't spend 20 minutes asking questions. Focus on the most impactful ones.
You can't build everything. Always ask: "If we can only build one feature, which should it be?"
Scale dramatically affects your design. A system for 100 users is very different from one for 100 million.
State your assumptions explicitly. "I'm assuming we need to support 1 billion users. Does that sound right?"
Here's how a good requirements discussion might flow:
You: "Before I start designing, I'd like to understand the requirements better. First, who are the primary users of this system?"
Interviewer: "We're building this for consumers, so regular users who want to share short posts."
You: "Got it. For core features, I'm thinking: posting content, following users, and viewing a feed. Are there other must-haves, or should I focus on these?"
Interviewer: "Those are the main ones. Let's focus on those."
You: "Perfect. For scale, should I design for Twitter-scale, so hundreds of millions of users and billions of posts?"
Interviewer: "Yes, let's design for that scale."
You: "Last question: is the feed timeline more important to be real-time, or is a slight delay acceptable?"
Interviewer: "Slight delay is fine, maybe up to a few seconds."
You: "Great, let me summarize: We're building a social platform for consumers with posting, following, and feed features, at the scale of hundreds of millions of users, with near-real-time but not instant feed updates. I'll start with the high-level architecture."
Notice how this conversation is quick (under 3 minutes) but covers all the essentials. Practice this flow until it becomes natural.
Requirements Gathering Practice
You're asked to "Design a ride-sharing app like Uber." What questions would you ask to clarify requirements?
User & Use Cases:
Core Features:
Scale:
Constraints:
Now that you know how to gather requirements, the next step is to identify your core entities and design the APIs that interact with them. This foundational work sets up everything that follows in your design.
Good summary: "So we're building a ride-sharing platform for consumers in major US cities, focusing on the core flow: requesting a ride, matching with a driver, real-time tracking, and payment. We expect millions of users with hundreds of thousands of concurrent rides at peak, and matching should happen within seconds."