Engineering LeadershipMay 18, 2026 8 min read
Your code review culture is your engineering culture. Fix it first, fix everything else.
Pull request behavior is the highest-resolution signal of psychological safety, seniority distribution, and delivery health on an engineering team. Most leaders look at it last.
I've audited engineering orgs from 12 to 1,400 people. The single best leading indicator of team health isn't sprint velocity, isn't engagement scores, isn't even attrition. It's the median time-to-first-review on a pull request, paired with the tone of the comments. Both are public, both are measurable, and both are nearly impossible to fake.
<4 hr
median time-to-first-review on healthy teams
DORA 2024 Accelerate Report
2.4×
higher deploy frequency for teams with reviews under 1 day
DORA 2024
61%
of engineers say review tone is their #1 signal of team safety
Stack Overflow Developer Survey 2025
3.8×
higher attrition on teams where reviews regularly sit >3 days
GitLab internal study, 2024
Healthy
- Reviews start within hours, not days.
- Comments ask questions before asserting answers.
- Senior engineers explain the 'why,' not just flag the 'what.'
- Approvals are distributed across the team, not bottlenecked on two people.
Broken
- PRs sit 3+ days waiting for a single reviewer.
- Comments are nitpicks and tone debates.
- Senior engineers rewrite the code in review instead of teaching.
- Junior engineers stop opening PRs because the review experience hurts.
What to measure this quarter
- Median and P90 time-to-first-review, by team.
- Review participation: % of engineers who reviewed at least one PR per week.
- Comment-to-approval ratio. Above 8:1 is usually a tone problem, not a quality problem.
- % of PRs reviewed by someone two or more levels junior — your real mentorship metric.
Written by
Pawan Joshi
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.