The first 14 days set the trajectory for everything that follows. Engineers who are well onboarded in the first two weeks are measurably more effective at 30 days and significantly more effective at 90 days than engineers who were left to figure it out themselves.
Before Day 1
Accounts and access provisioned: GitHub, Jira/Linear, Slack, cloud console, staging environmentDevelopment environment documented and tested on a clean machineFirst task identified and written up — something real but bounded, not a tutorialBuddy assigned from the existing team30-60-90 day expectations written down and sharedWeek 1: context and orientation
Day 1: team intro call, codebase walkthrough, architecture overview. Not more than 3 hours of meetings.Day 2: set up local environment, run the app, make a trivial change.Day 3–4: start first real task with buddy available for questions.Day 5: first week retro.Week 2: contributing and calibrating
First pull request reviewed and merged.Participate in sprint planning and retrospective as a full team member.Pair programming session with a senior team member on something non-trivial.The most common onboarding mistakes
Too much documentation before any real work.No buddy. The buddy is the single highest-leverage onboarding investment.First task too large or too vague.No check-in at day 5.Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
Text link
Bold text
Emphasis
Superscript
Subscript
.svg){kind=icon}
%20(1)-2.svg)
