Standard operating procedure
New Software Engineer First-Week Onboarding
Following this procedure guarantees that a new engineer has secure access, contributes their first code, receives mentorship, and has aligned expectations by the end of week one.
Applies to all new full-time software engineers from Day 1 to Day 5. Does not apply to contractors, interns, or non-engineering roles.
Procedure
-
1Provision GitHub, Slack, Jira, and cloud console accessDone when The new engineer receives login credentials and can successfully log into all four systems
-
2Configure and ship hardware (laptop, monitor, peripherals)Done when The engineer confirms receipt of the package and the device boots to the desktop
-
3Assign a buddy based on team rotation and expertiseDone when The buddy is notified via Slack and the assignment is recorded in the onboarding tracker
-
4Conduct the initial buddy introduction meetingDone when The agenda (tools, team intro, first week goals) is reviewed and the new engineer has the buddy's contact info
-
5Guide the engineer to a 'good first issue' in JiraDone when The engineer has claimed a ticket labeled 'good-first-issue' and added it to their local board
-
6Walk through the local development environment setupDone when The engineer runs the application locally without errors
-
7Submit the first pull requestDone when The pull request is created and linked to the Jira ticket
-
8Perform the first code reviewDone when The pull request has at least one approving comment or requested changes
-
9Merge the first pull request to the main branchDone when The PR is merged and the CI pipeline passes
-
10Conduct the Day-5 checkpoint meetingDone when The meeting notes are saved and the new engineer confirms their goals for week two
If something goes wrong
- I
- If