Eliciting Requirements in Interviews
What You'll Learn
You'll learn how to uncover the real requirements of a system design problem through strategic questioning — a skill that separates strong candidates from weak ones.
Why Requirements Don't Come Pre-Packaged
Imagine you're asked to "design Instagram." The interviewer won't hand you a specification document. They intentionally keep the prompt vague to see if you'll clarify before diving in. Jumping straight to architecture without asking questions is like building a house without asking the client how many bedrooms they need.
The Art of Asking the Right Questions
Start broad, then narrow down:
1. Clarify the Core Use Case "Are we focusing on photo sharing, stories, direct messaging, or all features?"
2. Probe Functional Requirements "Should users be able to edit photos in-app, or just upload?" "Do we need a feed algorithm or chronological ordering?"
3. Extract Non-Functional Constraints "What's our expected user base — thousands or millions?" "What latency is acceptable for loading a feed?" "How critical is data consistency — can we show slightly stale likes?"
4. Identify What's Out of Scope "Should I design the payment system for ads, or focus on the social features?"
The Interview Dance
Good interviewers want you to ask questions. They're testing whether you can:
- Identify ambiguity
- Prioritize what matters
- Make reasonable assumptions when answers are unclear
If they say "you decide," state your assumption clearly: "I'll assume we need 99.9% availability since users expect the service to always work."
Key Takeaway: Requirements elicitation is your first design decision — clarify the problem space with targeted questions before proposing any solutions, and document your assumptions when details are left to you.