This page is a guide for People Experience Associates when onboarding new team members. All onboarding tasks and guidelines for new team members, People Experience, and Managers are in the People Experience Onboarding Issue. Each onboarding issue is structured with tasks for all team members (day 1 to day 5 and then week 2 to week 4) and below those task sections are listed department-specific and/or role-specific tasks. In some cases, specific tasks may link to supplemental issues, created by specific teams, with in-depth training. In case this is a re-hire ping the ITOps team in the #it-help slack channel to ensure there are no blockers, before creating an onboarding issue or any accounts to avoid the re-hire from having system related issues on day 1.
On Mondays and Wednesday's the People Experience Associate in the
BHR Onboarding Report rotation will pull a report from BambooHR which compiles a list of all new team members starting in 2 weeks. This data is pulled from the Greenhouse <> BambooHR sync once the CES team updates the team member to
hired. The onboarding team members will then be added to the People Exp/Ops tracker under
Onboarding. In the event that a team member has already been synced and a new team members start date changes, it is important that the CES team notifies the People Experience team by submitting a Slack form in order to re-sync the team member and update the necessary systems (Onboarding issue, PEA tracker, BambooHR, etc).
People Experience Associates will create the onboarding issue, and start completing the onboarding tasks, no later than one week before the new team member joins. People Experience Associates require a minimum of 4 business days (with the new hire timezone as the basis) before the new hire's start date to complete all onboarding tasks. To ensure we create a smooth onboarding experience for new team members, provide enough time for the IT Ops team for laptop orders, and completing the I-9 process (for US-base hires) 4 days is the minimum amount of time needed. Should a contract not be signed prior to 4 working days from the start date, a new start date will be required.
If any changes are made or needed to the onboarding template, kindly notify team members of the People Experience team by ccing them in the MR with the
@gl-people-exp handle. Also notify other teams if a change will impact them.
All new hires will receive invitational access to their GitLab email, GitLab accounts, and any other work-related accounts on Day 1. No access is permitted before Day 1.
Labels Associated with Onboarding Issues
Before Starting at GitLabManager Tasks.
Accounts and AccessDay 1 - Manager Tasks.
At 14:00 UTC every Wednesday, the
PeopleOps Bot slack bot will send an alert in the
#peopleops-alerts channel listing any data missing (if applicable) from the BambooHR profiles of team members joining the following week. The People Experience team will fill in these missing details as soon as possible since completeness and accuracy of BambooHR profiles is necessary for all automation.
At 10:00 UTC every Thursday, the bot will send another alert in the
#team-member-updates channel with a list of all new team members joining the following week. This list includes names, email addresses, joining dates, and job titles of the new hires along with links to a Sisense graph showing the hiring progress over time. If any issues are detected by the bot, the post will first be submitted to the
#peopleops-alerts channel, where the People Experience team will then rectify and rerun the bot (/pops run joiningannouncement) in Slack.
For all GitLab Inc. and GitLab Federal LLC US-based employees, GitLab complies with all USCIS requirements and laws, including the I-9 and E-Verify process. GitLab uses an online I-9 portal called Fragomen where the process is completed and documents are saved electronically and securely. Only US-based People Experience team members who are US Citizens have administrative access to this portal.
There are two sections in the I-9 process (Section 1 and Section 2). GitLab requests that team members complete the I-9 process at least two business days prior to their start date. Please note the
two business days prior to the new hire's start date timeline pertains to GitLab's internal policy, not USCIS legal requirements. GitLab requires the process to be completed earlier than USCIS to ensure there is no delay in adding the new team member to payroll and other important systems.
Note: You can reference what are considered to be “Acceptable Documents” here.
If a GitLab team member has not completed Section 1 by EOD on their first day of work (their start date), all access is paused. Their GSuite account is Suspended, as well as their Okta account, as well as their 1Password account and Slack account if these have been created. Access will be resumed as soon as Section 1 is completed.
If a GitLab team member has completed Section 1 but their Designated Agent has not completed Section 2 by the EOD of the team members fourth day of work (3 business days after start date), all access is paused. Their GSuite account is Suspended, as well as their Okta account, as well as their 1Password account and Slack account. Access will be resumed as soon as Section 2 is completed.
The steps below serve as a guide for the People Experience team completing the I-9 process:
Designate an Agentat the top of the page
Note: Once Section 2 is completed by the designated agent, all access is automatically disabled to both the new hire and designated agent.
corrects the error in the 1-9.
EVerify Employment Verificationsection:
manually submit this I-9 to E-verify
E-Verify Employment Authorization Emailsent to the people-exp inbox and the employee document scans to the
Verification Documentsfolder in the employees BambooHR profile.
For certain systems and applications, it is required for Administrators to confirm that team members are US Citizens to be given access to these systems.
firstname.lastname@example.org ask for confirmation that a team member is a US Citizen.
The People Experience Associate who is responsible for allocating Onboading issues for the team, will open the BambooHR report titled, New Hire.
The People Experience Associate will create the GSuite account first.
email@example.com. To make sure that we create new GitLab.com GSuite emails according to the new team member's preferred first and last name, we first look at the team member's resume & relevant communications to find their preferred name.
firstname.lastname@example.org confirmation from them that is their preferred name.
email@example.com confirmation from them that is their preferred name.
As part of onboarding, People Experience Associates will process new hires in BambooHR. Aside from the steps listed in the onboarding issue, this is a description of how to add the proper information into BambooHR.
Note: All fields are pre-filled by the custom sync that exists between Greenhouse and BambooHR. If not, this is mentioned.
Note: If all of the necessary tabs in the new team member's BambooHR profile do not automatically populate, please go to the
Job tab, scroll down to the
Job Information section, click the pencil icon on the righthand side of the section, and ensure that the
Division fields are correctly populated. Save your changes and refresh the new team member's profile. All necessary tabs should now appear.
Openingstable and scroll to the far left to get the
|Country||Pay Frequency||Pay Schedule|
|United States of America||24||semi-monthly|
total-rewardsteam in the slack channel
#peopleops_totalrewardsand verify the title is in the correct format before adding.
Job Title Speciality: If there is a specialty ((this would be found under On Job- Offer Details), use the drop down to select the appropriate specialty. If the specialty is not listed in the drop down menu, create a new one. The Job Title Specialty field has no restrictions)
(Examples of a Specialty: Growth, Commercial, DoD, EMEA).
_Note: For Development, the
Job Title Specialty field should indicated the
Group level within Development (I.E. Package, Verify, Fulfillment, etc). For reference, there is an overview of all of the stages and their corresponding
Groups on the Product sections, stages, groups, and categories handbook page.
The Employment Status table will be filled out automatically depending on the New Hire's country policies. It is important that the People Experience Associate verifies that the statuses have been added successfully.
Activewith the Hire Date as the Effective Date
Temporary Contractwith effective date marked as the start date (add comment
12-month Temporary Contract (YYYY-MM-DD start date to YYYY-MM-DD end of Temporary Contract))
Temporary Contract Endingwith the date marked as exactly 12 months from their start date (Important: For a 12-month contract with a March 4, 2019 start date, the end date would be March 3, 2020. Any following contract after this 12-month period would have a start date of March 4, 2020)
Probationary Periodwith the date marked as the start date (add comment
1-month Probation Period (YYYY-MM-DD start date to YYYY-MM-DD end of Probation Period))
End of Probationary Periodwith the date marked as exactly one month from their start date
Activewith the date marked as exactly 12 months and one day from their start date (AKA: The day after the Temporary Contract ends)
|Effective Date||Employment Status||Comment|
|2020-06-12||Probationary Period||1-month Probation Period 2020-06-12 to 2020-07-12|
|2020-06-12||Temporary Contract||12-month Temporary Contract 2020-06-12 to 2021-06-11|
|2020-07-12||End of Probationary Period|
|2021-06-11||Temporary Contract Ending|
Probationary Periodwith the start date - Add a comment with the length of the probation period and the start to end date. This is helpful for the reminder emails.
End of Probation Periodwith the number of months after start date.
Activenumber of months + 1 day after start date.
/pops run probationstatus team member name or GitLab email address. 1. If the status is incorrect, the People Experience Associate will need to request assistance from the Senior Manager, People Operations to update the status.
End of Probation Perioddate is accurate, this date will drive an alert for the People Experience team automatically, 5 days before and on the day the probation period expires. Details of the probation period process can be found on the Contracts and International Expansion page. Please use these probation periods in BambooHR for team members in these specific groups.
Review the Referral Process Page for adding referral bonus.
Note: In the case that a referral was not added or was incorrectly added to BambooHR, resulting in the bonus not being paid on time to the referring team member, please proceed with the following steps:
bonus datesection, the date that the referral bonus should have been paid out should be added (I.E. 3 months after the referred team member's start date).
firstname.lastname@example.org notify them of the change.
The sync can't do this yet.
If applicable, add a time off accrual plan for employees located in GitLab LTD (UK), GitLab GmbH (Germany), GitLab B.V. (Belgium), GitLab Inc (China), and GitLab B.V.(Netherlands).
The People Experience Associate will then create an onboarding issue with a ChatOps command in Slack 4-5 business days prior to the new team member's start date.
/pops run onboarding BambooHR_ID_number(not Employee ID #). This number is found in the team member's BambooHR profile URL, after
id=. It is a 5-digit number. An example of the command would be
/pops run onboarding 00000. If BambooHR's API is down, this ChatOps command will fail and will need to be created manually.
@gitlab.comemail ID as the primary email ID in GitLab. They will then manually need to be assigned.
Important: This email can be created and scheduled at any time before the new team member's start date.
email@example.com well as the new team member's gitlab email.
Important: This email can only be sent a maximum of 48 hours prior to the new team member's start date/time. If it is sent more than 48 hours prior the link will no longer be valid. (I.E. If a new team member is starting on Monday, the earliest the People Experience Associate can send this email is on Saturday).
reset passwordon the lefthand side of the page.
send(do not insert the new team member's email address here).
personal email address. Please add the new team member's GitLab email address in the body of the email where it says "Hello [new team member name], [firstname.lastname@example.org].
Each assigned People Experience Associate will send their new team members our Code of Conduct Acknowledgment for review and signature.
Send the "New Hire Swag" email to new hire. It must state that they need to access the GitLab Swag Store, choose goods and use the new hire discount code provided in the email at checkout. New hires must use their GitLab email at checkout.
New Hire Swag code.
We expect every team member to be an advocate for GitLab and we offer every team member the opportunity to have business cards, to make GitLab feel real to people around them despite not having an office.
Every week, the assigned People Experience Associate pulls a report, which will include the new team members email address, as per this process. An invitation will then be sent to the new team member by the Moo representative.
Business cards should be ordered by the team member themselves using the Moo platform. Self-help instructions are here.
confirmto verify each user individually.
All PEAs are responsible for checking to make sure that their team members are eventually confirmed, but we all confirm any team members who are in the Pending stage as we log into 1Password multiple times on Day 1 & 2.
The People Experience Team is responsible for monitoring and facilitating the completion of the onboarding issue.
People Experience Associates will complete the following tasks.
2 Business Days Prior:
On Start Date
After Day 1
After Day 3
After Week 1
If a GitLab team-member is in need of supplies and is unable to purchase the items themselves, People Experience Associates can place the order, per Spending Company Money. Use the Amazon business account for all Amazon links. In order to see what is available to ship in each country, use the Amazon site specific to a new team member's location.
In Section 2 of Form I-9, the designated agent should enter the foreign passport information in the first area and the I-94 information in the second area in the List A column. Enter the information from the Form I-20, which includes the Student and Exchange Visitor Information System (SEVIS) number and expiration date (i.e., the Form I-20 CPT employment authorization end date (Must match section 1 date), not the program end date) in the third area in the List A column.
Unpaid interns are not required to complete an I9.