Q317: System Design Retrospective How to Review Your Own Answer

What Interviewers Want To Evaluate

Interviewers want to know whether you can self-correct and evaluate your own design objectively.

They are checking reflection, gap detection, prioritization, trade-off awareness, communication maturity, and whether you can improve after a mock or real interview.

Short Interview Answer

After a system design answer, I review it against a rubric: clarification, scope, data model, state ownership, API contracts, rendering, UX states, performance, accessibility, security, observability, rollout, and trade-offs. I identify which gaps were knowledge gaps, structure gaps, or communication gaps. Then I rewrite the answer outline, add missing decision points, and practice a targeted drill rather than repeating the same broad prompt.

Detailed Interview Answer

Self-review turns practice into progress.

Without review, mock interviews can become repetition.

The goal is to answer:

What worked?
What was missing?
Where did I lose structure?
Which trade-off was unclear?
What should I practice next?

Review Rubric

Use a consistent rubric:

requirements
scope
entities
state ownership
routes
APIs
rendering
loading and errors
performance
accessibility
security
observability
rollout
trade-offs
communication

Score each area quickly.

The score is less important than the pattern.

Gap Types

Classify gaps:

knowledge gap
structure gap
communication gap
timing gap
depth gap
prioritization gap

Example:

I knew search architecture but introduced ranking too late.

That is a structure or timing issue, not a knowledge issue.

Rewrite the Outline

After review, rewrite the answer.

Do not rewrite the entire transcript.

Rewrite:

opening clarification
P0 scope
architecture diagram in words
three key trade-offs
closing rollout plan

This creates a better reusable pattern.

Detect Over-indexing

Senior candidates often over-index on their comfort zone.

Examples:

React internals
CSS details
API design
performance
platform tooling

Depth is good, but imbalance hurts.

The answer should match the prompt.

Communication Review

Ask:

Did I signpost sections?
Did I pause for interviewer input?
Did I state assumptions?
Did I explain trade-offs simply?
Did I finish with a coherent recommendation?

Communication can be the difference between a strong design and a confusing one.

Interview Framing

Say:

I review mocks with a rubric so I can tell whether I missed content, structure, prioritization, or communication.

Then add:

The next practice session should target the repeated weakness, not just another random prompt.

Common Mistakes

• Saying "I need to study more" after every weak mock.
• Ignoring answer structure.
• Practicing only new prompts.
• Not rewriting the opening.
• Forgetting timing.
• Treating all feedback equally.
• Missing repeated patterns.

Learning Studio Example

After a Learning Studio system design mock, review:

Did I define learner workflow?
Did I separate local and synced progress?
Did I choose rendering per route?
Did I discuss practice console safety?
Did I cover mobile reading?
Did I include rollout and observability?

If two mocks miss observability, review Q296 and drill that section.

Final Mental Model

Self-review is debugging your interview process.

The loop is:

answer
score
classify gap
rewrite outline
drill weakness
repeat