Understanding how the System Design Interview is scored and how the interviewer manages its complexity is critical for successful completion. In this chapter we will look at assessment criteria for each stage of the interview and a mechanism for adapting complexity.
Evaluation criteria by interview stage
The interviewer evaluates the candidate on several key aspects at each stage System Design Interview. Understanding these criteria will help you place the right emphasis.
Formalization of requirements
The candidate's ability to identify and structure system requirements is assessed.
Good
- Asks clarifying questions
- Identifies functional and non-functional requirements
- Defines the scope and boundaries of the system
Weak
- Goes straight to the solution
- Makes assumptions without elaboration
- Doesn't prioritize
System Boundaries and Public API
An understanding of how the system interacts with the outside world is assessed.
Good
- Clearly defines API endpoints
- Thinks through request/response formats
- Takes into account API versioning
Weak
- Skips API definition
- Inconsistent contracts
- Doesn't think about backward compatibility
Basic data flows
Understanding of write path and read path in the system is assessed.
Good
- Clearly separates write/read paths
- Uses sequence diagrams
- Thinks through async processing
Weak
- Mixes threads into one pile
- Does not take into account asynchrony
- Forgets about error handling
Conceptual and actual data schema
The ability to design a data model to meet the requirements is assessed.
Good
- Starts with a conceptual model
- Justifies the choice of database type
- Thinks through indexes
Weak
- Immediately selects technology without analysis
- Ignores access patterns
- Doesn't think about denormalization
System scaling
Understanding of scaling strategies and their trade-offs is assessed.
Good
- Understands vertical vs horizontal scaling
- Understands sharding strategies
- Takes bottlenecks into account
Weak
- "Just add more servers"
- Does not take into account stateful components
- Ignores data consistency
Readability and clarity of diagrams
The ability to visually communicate architecture is assessed.
Good
- Neat, readable diagrams
- Logical arrangement of elements
- Signatures and explanations
Weak
- Chaotic lines and blocks
- No component signatures
- Unclear connections
Assessment levels (grades)
The interviewer evaluates the candidate on a grade scale, which determines the level independence and depth of understanding of System Design.
Junior
The candidate is able to work only with happy path and requires significant assistance from the interviewer to progress on the task.
Specifications:
- Understands basic system logic
- Needs leading questions
- Does not take into account edge cases independently
- Limited understanding of scaling
Middle
The candidate can work independently on individual modules of the system without constant guidance.
Specifications:
- Designs individual components independently
- Takes into account basic edge cases
- Understands basic scaling patterns
- Can justify technological choice
Senior
The candidate can take end-to-end ownership of system design.
Specifications:
- Leads the entire design process independently
- Anticipates problems and offers solutions
- Deeply understands trade-offs
- Takes into account operational aspects (monitoring, debugging)
Senior+ / Staff
The candidate demonstrates an exemplary design level, beyond standard expectations.
Specifications:
- Offers innovative solutions
- Takes into account long-term evolution of the system
- Thinks about cross-cutting concerns (security, compliance)
- Can explain decisions at the business level
Difficulty Variation Mechanism
It is important to understand that the interview begins with maximum freedom and complexity. The interviewer gradually adapts the level depending on how the candidate performs.
Start
Senior level
Maximum freedom
In case of difficulties
Middle level
More tips
Severe difficulties
Junior level
Specific questions
How to improve your score
- Proactively move forward without waiting for questions
- Raise important topics independently (edge cases, scaling)
- Explain trade-offs without additional questions
- Offer alternative solutions
What lowers the score?
- Waiting for hints from the interviewer
- Failure to justify decisions
- Getting stuck at one stage
- Ignoring the interviewer's prompts
Key Findings
The interview always starts at the Senior level — you are given maximum freedom to show your abilities.
Hints are calibration — Each hint from the interviewer adjusts the assessment of your level.
Proactivity is critical — The more you manage the process yourself, the higher the score.
Trade-offs are more important than "correct" answers — the ability to explain trade-offs is valued over knowledge of specific solutions.