Code Review
Also written as PR review
The practice of having other engineers read and comment on code changes before they're merged, to catch bugs and share knowledge.
Think of it like
Like a second editor reading a draft article before it's published — catching mistakes and asking 'did you mean this?' before it reaches readers.
Junior or senior?
Junior sounds like
Treats code review as a gate to get past before merging.
Senior sounds like
Describes it as a two-way teaching tool — with a real example of learning something, or teaching something, through one.
Ask them
“Tell me about a time a code review changed your approach, or you pushed back on one.”
Sounds like real experience
Describes a specific review comment or disagreement — what was flagged, how the conversation went, what actually changed as a result.
Probe further if
Describes code review only as a required step to merge code, without a specific example of a comment that changed their approach or one they pushed back on.