Self-Scoring Rubric for System Design Practice

The biggest gap in most candidates' system design preparation is not technical knowledge -- it is the lack of structured self-assessment. Candidates practice by reading solutions but rarely evaluate how well they would perform under interview conditions. Without a rubric, practice sessions become passive reading exercises rather than active skill-building. This self-scoring rubric provides a consistent framework for evaluating your performance across the five dimensions that interviewers actually assess.

The rubric covers five categories, each scored on a 0-3 scale for a maximum of 15 points. The first category is Requirements Gathering (0-3): a score of 0 means you jumped straight into the design without clarifying the problem; 1 means you asked some questions but missed non-functional requirements (NFRs) like latency, availability, or consistency guarantees; 2 means you systematically identified both functional and non-functional requirements; 3 means you quantified the requirements with specific numbers (QPS, storage, latency targets) that drove your design decisions. The second category is High-Level Design (0-3): a score of 0 means key components were missing or the architecture was fundamentally flawed; 1 means the basic components were present but the connections between them were vague; 2 means the design was reasonable with clear component responsibilities and API contracts; 3 means the architecture was clean, well-justified, and included data flow arrows showing how requests traverse the system.

The third category is Deep Dive (0-3): a score of 0 means you stayed at a surface level and did not explore any component in detail; 1 means you identified bottlenecks but did not propose solutions; 2 means you addressed at least one bottleneck with a concrete solution backed by reasoning; 3 means you addressed two or more bottlenecks with data-driven solutions (cache hit rate estimates, throughput calculations, latency breakdowns). The fourth category is Trade-offs (0-3): a score of 0 means no trade-offs were discussed; 1 means you acknowledged that trade-offs exist but did not compare alternatives; 2 means you compared at least two alternatives with clear pros and cons; 3 means you compared alternatives quantitatively (latency impact, cost implications, complexity assessment) and made a justified decision. The fifth category is Communication (0-3): a score of 0 means you were disorganized or rambling; 1 means you had some structure but lost the thread at times; 2 means you communicated clearly with a logical flow; 3 means you proactively anticipated the interviewer's questions, signposted your thinking, and managed time effectively.

To use the rubric effectively, record yourself performing a timed practice session (35-45 minutes, the typical interview length). After the session, replay the recording and score each category honestly. Track your scores over time in a spreadsheet. Focus your study on the lowest-scoring categories. A total score below 6 indicates that fundamentals need significant work. A score of 6-9 means you are progressing but have clear gaps. A score of 10-12 means you are performing at a solid level and should focus on polishing. A score of 13-15 means you are performing at a strong-hire level.

A self-scoring rubric for system design is like a training log for an athlete. A runner who just runs every day without tracking pace, distance, or heart rate improves slowly because they do not know which aspect of their fitness needs the most work. A runner who logs every workout with specific metrics (5K time, VO2 max, cadence) can identify weaknesses (endurance is strong but speed work is lacking) and target their training accordingly. Similarly, a candidate who practices system design without scoring each session has no way to identify whether their weakness is in requirements gathering, deep dives, or communication -- and no way to measure whether their preparation is actually improving their performance.