Standard operating procedure
New Engineer First-Week Onboarding SOP
Following this procedure guarantees that a new engineer has secure access, clear social integration, a verified first contribution, and a structured feedback loop within five business days.
Applies to all newly hired software engineers from the moment the offer is accepted until the end of the first week. Does not apply to contractors or interns unless explicitly specified in their contract.
Procedure
-
1Create and distribute login credentials for all required systems (GitHub, Jira, Slack, CI/CD, cloud console)Done when The new engineer successfully logs into GitHub and Jira using the provided credentials
-
2Assign a buddy and schedule a 30-minute introductory coffee chatDone when The calendar invite for the buddy introduction is sent and accepted by both parties
-
3Provide the new engineer with a 'Hello World' or low-risk bug fix task and explain the local development setupDone when The new engineer has the codebase cloned locally and the application runs successfully on their machine
-
4Guide the new engineer through creating a pull request and merging their first commitDone when The pull request is merged into the main branch and the CI pipeline passes green
-
5Conduct a 15-minute check-in to review access, setup, and the first commit experienceDone when The meeting takes place and any immediate blockers are documented in the ticketing system
-
6Schedule a 30-minute structured checkpoint meeting for the end of day 5Done when The meeting is scheduled on the calendar with the agenda shared with the new engineer
-
7Review progress against the first-week checklist and address any outstanding blockers or questionsDone when The checklist is marked as complete and any open issues are assigned to owners with due dates
If something goes wrong
- I
- If