Pull Requests & Code Review
Proposing changes and reviewing each other's work.
Backend Engineer track
Junior
Write correct code, ship small changes safely, ask good questions.
Core: start here
- Code ReviewTeammates reading your change to catch bugs and share knowledge.
- PR DescriptionExplaining what changed, why, and how to test it.
- Pull RequestA proposal to merge a branch, with discussion and review.
- Receiving Code ReviewTaking feedback without defensiveness and resolving it clearly.
- Self-ReviewReading your own diff before asking others to.
- Small Pull RequestsKeeping changes small so they're reviewed faster and better.
5 more junior concepts
- Approve vs Request ChangesThe review states and what each one signals.
- Draft PRA PR opened early for feedback, not yet ready to merge.
- Labels and Issue HygieneLabeling, linking and closing issues so work stays findable.
- NitsMinor, optional review comments, labeled so they don't block.
- Pair ProgrammingTwo people working on the same code at the same time.
Mid-level
Own a feature end to end without hand-holding.
Core: start here
- Giving Code ReviewReviewing others' code helpfully: priorities, tone and turnaround.
6 more mid-level concepts
- AI-Assisted Code ReviewUsing AI reviewers as a first pass, not a replacement for human review.
- CODEOWNERSA file that assigns required reviewers by path.
- CONTRIBUTING GuideA file explaining how to propose changes to a project.
- Merge Commit vs Squash vs Rebase MergeHow a PR lands on main and what history it leaves behind.
- Mob ProgrammingA whole team working on one problem together.
- Review TurnaroundHow quickly reviews happen, and why it matters to team speed.
Senior
Own a system, its failure modes, and its trade-offs.
- Stacked PRsA chain of dependent pull requests, each reviewable on its own.
Staff
Shape how many teams build, across systems.
Nothing here yet.
Principal
Set technical direction for the organization.
Nothing here yet.
Data Analyst track
Junior
Write correct SQL, build trusted dashboards, ask good questions.
- Pull RequestA proposal to merge a branch, with discussion and review.
Mid-level
Own an analysis end to end, from vague question to recommendation.
Nothing here yet.
Senior
Own experimentation and metrics design; call out bad numbers.
Nothing here yet.
Staff
Shape how the organization measures and decides.
Nothing here yet.
Principal
Set measurement strategy across the company.
Nothing here yet.
Data Engineer track
Junior
Build and fix pipelines from clear specs; write correct SQL.
Core: start here
- Code ReviewTeammates reading your change to catch bugs and share knowledge.
- PR DescriptionExplaining what changed, why, and how to test it.
- Pull RequestA proposal to merge a branch, with discussion and review.
- Receiving Code ReviewTaking feedback without defensiveness and resolving it clearly.
- Self-ReviewReading your own diff before asking others to.
- Small Pull RequestsKeeping changes small so they're reviewed faster and better.
5 more junior concepts
- Approve vs Request ChangesThe review states and what each one signals.
- Draft PRA PR opened early for feedback, not yet ready to merge.
- Labels and Issue HygieneLabeling, linking and closing issues so work stays findable.
- NitsMinor, optional review comments, labeled so they don't block.
- Pair ProgrammingTwo people working on the same code at the same time.
Mid-level
Own pipelines and models end to end, including their quality.
- AI-Assisted Code ReviewUsing AI reviewers as a first pass, not a replacement for human review.
- CODEOWNERSA file that assigns required reviewers by path.
- CONTRIBUTING GuideA file explaining how to propose changes to a project.
- Giving Code ReviewReviewing others' code helpfully: priorities, tone and turnaround.
- Merge Commit vs Squash vs Rebase MergeHow a PR lands on main and what history it leaves behind.
- Mob ProgrammingA whole team working on one problem together.
- Review TurnaroundHow quickly reviews happen, and why it matters to team speed.
Senior
Design the platform's storage, processing and modeling choices.
- Stacked PRsA chain of dependent pull requests, each reviewable on its own.
Staff
Shape how the whole organization produces and uses data.
Nothing here yet.
Principal
Set data strategy and architecture across the company.
Nothing here yet.
Frontend Engineer track
Junior
Build UI that works, ship small changes safely, ask good questions.
Core: start here
- Code ReviewTeammates reading your change to catch bugs and share knowledge.
- PR DescriptionExplaining what changed, why, and how to test it.
- Pull RequestA proposal to merge a branch, with discussion and review.
- Receiving Code ReviewTaking feedback without defensiveness and resolving it clearly.
- Self-ReviewReading your own diff before asking others to.
- Small Pull RequestsKeeping changes small so they're reviewed faster and better.
5 more junior concepts
- Approve vs Request ChangesThe review states and what each one signals.
- Draft PRA PR opened early for feedback, not yet ready to merge.
- Labels and Issue HygieneLabeling, linking and closing issues so work stays findable.
- NitsMinor, optional review comments, labeled so they don't block.
- Pair ProgrammingTwo people working on the same code at the same time.
Mid-level
Own a feature end to end without hand-holding.
Core: start here
- Giving Code ReviewReviewing others' code helpfully: priorities, tone and turnaround.
6 more mid-level concepts
- AI-Assisted Code ReviewUsing AI reviewers as a first pass, not a replacement for human review.
- CODEOWNERSA file that assigns required reviewers by path.
- CONTRIBUTING GuideA file explaining how to propose changes to a project.
- Merge Commit vs Squash vs Rebase MergeHow a PR lands on main and what history it leaves behind.
- Mob ProgrammingA whole team working on one problem together.
- Review TurnaroundHow quickly reviews happen, and why it matters to team speed.
Senior
Own an app's architecture, performance, and failure modes.
- Stacked PRsA chain of dependent pull requests, each reviewable on its own.
Staff
Shape how many teams build, across apps.
Nothing here yet.
Principal
Set technical direction for the organization.
Nothing here yet.