Code Review & Judgment
Code review is the skill of finding the problems that matter in someone else's code and saying so usefully. It is assessed on severity calibration — catching the data-loss bug matters, and burying it under twelve style comments does not.
Also called: technical review, PR review, code quality
What is code review & judgment?
Code review covers reading unfamiliar code for correctness, spotting real defects and security issues, calibrating severity, and writing feedback that gets acted on rather than resented.
Review quality determines what reaches production and how quickly engineers improve. Severity calibration in particular is a strong senior signal that interviews rarely test.
What do the levels of code review & judgment mean?
Four levels, each defined by observable behaviour rather than by years. This is the definition employers set their bar against, and the one every proof is scored to.
- L1Aware
Spots style inconsistencies and obvious errors.
Evidence: Review comments on clear problems.
- L2Working
Finds correctness bugs and explains why they are bugs.
Evidence: A review catching a real defect with a clear explanation.
- L3Independent
Ranks findings by severity, catches security and data-integrity issues, and writes feedback the author acts on.
Evidence: A review with severity-ranked findings, including a security or data issue.
- L4Leading
Raises review quality across a team and uses review as a teaching instrument rather than a gate.
Evidence: Review standards adopted by a team; measurable defect reduction.
| Level | Label | People proven here |
|---|---|---|
| L1 | Aware | 0 |
| L2 | Working | 0 |
| L3 | Independent | 2 |
| L4 | Leading | 0 |
How is code review & judgment assessed?
Candidates review a pull request containing a genuine correctness bug, a security issue, and several stylistic imperfections. Scoring rewards finding the real defects, ranking them correctly, and writing comments that are specific and actionable.
Which roles require code review & judgment?
| Role | Level required | Status |
|---|---|---|
| Founding Engineer | L2 Working | Nice to have |
How do you prove code review & judgment?
Code Review & Judgment: questions people ask
- What language is the review in?
- You choose from several languages when you start. The bugs are logic and design issues, not language trivia.
- Is tone scored?
- Actionability is scored, tone is not. A blunt comment that tells the author exactly what to change scores above a polite one they cannot act on.
- Why is severity ranking weighted so heavily?
- Because a review that lists a data-loss bug thirteenth, under style nits, will get the data-loss bug shipped. Ranking is the part of review that protects production.