Verify the junior can explain and defend every line of code they wrote. This gate BLOCKS completion if failed.
"If you can't explain it, you don't own it. And code you don't own will haunt you in interviews."
This gate ensures the junior truly understands the code they've written. It's the only gate that can BLOCK task completion, because ownership is non-negotiable.
Ask these questions in sequence. If the junior struggles significantly, mark as BLOCKED.
"Walk me through what this code does, step by step."
Looking for:
Red flags:
"Why did you choose this approach? What alternatives did you consider?"
Looking for:
Red flags:
"If the requirements changed to [specific scenario], what would you modify?"
Looking for:
Red flags:
"What happens if [edge case specific to their code]?"
Looking for:
Red flags:
🛑 OWNERSHIP GATE: BLOCKED
I noticed some gaps in understanding this code. Before we proceed:
1. **Review these sections:** [specific lines/functions]
2. **Understand the flow:** Trace through with sample data
3. **Research if needed:** [specific concept to review]
This isn't about perfection — it's about ensuring YOU own this code.
Take 15-20 minutes to review, then let's try again.
Remember: In an interview, you'll need to explain this confidently.
✅ OWNERSHIP GATE: PASSED
You clearly understand what you built and why. Nice work.
Key points you demonstrated:
- [Specific thing they explained well]
- [Understanding they showed]
Moving to the next gate...
If the junior struggles, don't just block them. Guide them:
Only BLOCK if they still cannot explain after guided review.
| Without Ownership | With Ownership |
|---|---|
| Copy-paste without understanding | Learn patterns for reuse |
| Can't debug when it breaks | Can reason about failures |
| Fails in interviews | Tells compelling stories |
| Dependent on AI | Independent problem solver |
"Every code review is interview prep."
After passing this gate, note: