Onboarding is incredibly important at GitLab. We don't expect you to hit the ground running from day one.
We highly recommend taking at least two full weeks for onboarding and only in week three starting with team specific onboarding and training. Please feel free to participate in your team's work in your first two weeks, but don't feel like you have to contribute heavily. All onboarding steps are in the onboarding issue template which is owned by the People Experience Team.
Each onboarding issue has a main section that contains tasks relevant to all GitLab team-members and a due date of 30 days. Below the main section are department and role-specific tasks. Some roles and departments have tasks that link to a supplemental issue template or an additional onboarding page. Reach out to your onboarding buddy or other GitLab team members if you need help understanding or completing any of your tasks.
Through onboarding issues, you should gain access to our team member baseline entitlements. On Day 2 of onboarding an Access Request will be generated, if a template has been created for the role. Access requests are owned by the IT team. If you have any access requests related questions, please reach out to #it-help in Slack.
The lists below categorize each onboarding resource by its location.
An issue is created for new team members at least 4 business days prior to their start date. The Manager and a People Experience Associate will be assigned to this issue. Managers, People Experience and IT Ops all have tasks that need to be completed prior to the start date to ensure a smooth and successful onboarding process. For questions or help with any of these tasks feel free to reach out in the issue by mentioning @people-exp or adding a question in the #peopleops Slack channel.
The People Experience Coordinator completes a monthly audit of all open onboarding issues to ensure that the new team member, manager and People Experience team tasks are completed. More importantly, there are certain tasks which need to be completed in line with our company compliance (security, payroll, etc).
If any tasks are still outstanding, the People Experience Coordinator will ping the relevant members on the issue requesting action on the items or checking whether the issue can be closed.
It remains the responsibility of the onboarding team member or the onboarding team members manager to close the issue.
The employment bot will automatically close any onboarding issues still open after 60 days.
To ensure a successful completion of the onboarding issue, it is important that all tasks are checked off, whether the task is applicable to the onboarding team member or not. Checking the box indicates one of the following:
These templates are used by the People Experience team to onboard new team members.
These are added to the "All Team Member" Template
