Congratulations on completing the interview process, and starting your first day at GitLab. We are so excited that you are here! This page is designed to help you navigate the onboarding process from reading the handbook, to completing the onboarding issue. Regardless of your role, we all use GitLab, and if you come from a non-technical background, this might be new to you! At times the onboarding issue might feel overwhelming, but if you have any additional questions along the way, please feel free to ask People Ops, your buddy, or anyone else at GitLab in the
#questions channel on Slack.
Throughout your first few weeks at GitLab it is important to focus on the onboarding issue. The onboarding issue is specific to you, for an idea what is in there please see the template. This guide will help you understand what is in the onboarding issue, and why we are asking you to complete the items on the issue.
Prepare for your first Team Call. In the calendar invite is a link to the Team Call agenda. The first time that you join, please make sure that you connect at least 10 minutes before the call in order to download Zoom and make sure that your camera and microphone are working properly. We'd like you to introduce yourself to the team (±1 minute), so please prepare three talking points for yourself. Please make sure to tell us about where you were before GitLab, why you wanted to join our team, and what you like to do in your spare time.
Connect with GitLab's social media sites:
In the onboarding issue, we ask you to complete a variety of tasks. Here are some tips on items like gmail, zoom, calendly, etc. The onboarding issue can be seen at the bottom of this page.
We recommend that you set up your 1Password account early in the onboarding process since you will need it to hold all of the new passwords that you will create. This is an awesome tool, that GitLab uses to store all passwords for each department. You will also have your personal vault where you can store all the passwords that you are creating for GitLab. In keeping with our security best practices. We ask that you do set up this 1Password account with your GitLab email, even though you might have one already.
GitLab asks you to enable 2FA (2-Step Verification, also known as two-factor authentication), because it adds an extra layer of security to your account. You sign in with something you know (your password) and something you have (a code sent to your phone). If you have problem with 2FA just let people ops know! We can disable it for you to then set it up again. If the problem persists, then we can direct you to one of our super admins.
BambooHR is our HRIS (Human Resource Information System) for all team members. We have self-service enabled so that at any time you can access your account to see your employment information and documentation. As part of onboarding, please make sure to update everything that is applicable to you on the Personal tab, your ethnicity (which is located on the Jobs tab), and emergency contact information. We also ask that you provide People Ops with a Photo ID which is used for Employment Verification Purposes. You can send this documentation in any way you feel most comfortable. Some common ways in the past have been emailing People Ops, sending as a direct message to our People Ops Analyst in Slack, or scheduling a call with our People Ops Analyst to view the documentation.
The information from BambooHR is used to feed other systems, so it is important that it is filled out before you start. If you are a GitLab Inc. employee, you will receive login information from TriNet, our payroll and benefits provider, within 24 hours of your start date.
The dev server is only viewable to team members, and is used by the Development team (amongst others). Per the GitLab workflow point 9, everything that can be public should be out in the open. GitLab.com is viewable to anyone with an account. We ask you to set up your GitLab.com account with your GitLab email for additional security.
Calendly is a calendar tool that allows individuals to select open meeting slots in order to speak with others at the company. (Great for also setting up coffee breaks!) All team members add Calendly to their Slack profile as a part of onboarding, so if you ever need or want to speak with another team member, you can schedule the meeting yourself. When you are setting up Calendly, there is no specific GitLab account. With the free version you will only be allowed one meeting time, but if you need to upgrade to a Pro account, you can do so and expense it per spending company money.
You will receive an email to set up your account for Egencia. This travel is for company purposes, and is paid for by the company at the time of booking. For more information on setting up your account please visit our travel page.
We are happy to have you join our company and to include you in our team page. The following are the steps to add yourself to the team page. Please follow the links that will guide you to full guides about every step. If you are not familiar with local git yet, feel free to do this through the web interface, and ask anyone at the company questions along the way.
yourname.pngand then follow the "how to add an image" steps. Picture Notes:
data/, and then
team.yml, click on “edit” on the top right side of your screen.
Firstname 'Nickname' Lastname. Verify that your title is entered correctly. Add the filename of the picture that you uploaded previously. Enter your twitter and gitlab handle. Write a story about yourself. Don't forget to use other team members' information as a reference and to respect the spaces between lines. Please don't use "tab" because it will break the page format.
yourname.pngand then add it to the
source/images/team/directory. Picture Notes:
Firstname 'Nickname' Lastname. Verify that your title is entered correctly. Add the file name of the picture that you uploaded previously. Enter your twitter and GitLab handle. Write a story about yourself. Don't forget to use other team members' information as a reference and to respect the spaces between lines. Please don't use "tab" because it will break the page format.
A core value of GitLab is documentation. Therefore, everything that we do, we have documented on about.gitlab.com. This can make the handbook seem huge! Don't let it scare you. To simplify navigating the handbook here are some suggested steps. Feel free to take a wrong turn at any time to learn more about whatever you are interested in.
If you need any help with Git itself, subscribe to the
#git-help channel on Slack and feel free to ask any question you might have.
Learn how to get started with git. It is important for all team members to understand how to work on the Web UI and locally. The rest of the team is happy to assist in teaching you git.
When you are first starting at GitLab and creating new merge requests, you can assign the MRs to your manager. Going forward, it's best practice to assign the MR to the relevant department; for example, if you are making an edit to the People Ops section of the handbook, please assign it to someone within People Ops.
If you're unsure of who to assign a merge request to or if you have any questions or problems, feel free to reach out to your manager or onboarding buddy. You can also ask in the
#git-help channel in Slack!
When you join GitLab your GitLab.com account will be added to the gitlab-com group as a Developer. Please see this blog post discussing how we assign permissions, as well as a permission levels chart to find out more about what each level can do.
At any time if you have questions, please ask your manager, buddy, People Ops, or anyone else at the company!
Please add to me. Questions that were not answered? Something that is not clear? Please create an issue or a merge request and assign it to People Ops to make this documentation better for the next new team member.
Create a new confidential issue for new hire in organization using the
onboarding template from the dropdown. The topics are ordered by priority in which they need to be tackled, and the main person responsible is called out at the beginning of each task. Please update the list as more steps arise, and then also update the associated item on the offboarding list.
Employees should answer GitLab quiz questions in the first 2 weeks of working in the company. If the answers are not accurate, you may retest once: GitLab Quiz Please schedule a call with your manager.
Please see the NPS section of our handbook.