Gitlab hero border pattern left svg Gitlab hero border pattern right svg

GitLab Onboarding Processes

  1. You are here:
  2. Handbook
  3. People Group
  4. GitLab Onboarding
  5. GitLab Onboarding Processes

Onboarding Processes

Overview

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.

Timing

On Monday and Wednesday 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 and added to the onboarding tracker. This data is pulled from the Greenhouse <> BambooHR sync once the Candidate Experience Specialist team updates the team member to hired.

In the event that a team member has already been synced and a new team members start date changes, it is important that the Candidate Experience Specialist 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 5 days 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 or updates need to be made 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.

Issue Organization

Labels Associated with Onboarding Issues

Alerts & Announcements

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.

Pre-Onboarding

Pre-Onboarding, US

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 LawLogix where the process is completed and documents are saved electronically and securely.

Timing of I-9

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.

If a GitLab team member has not completed Section 1 by end of day on their first day of work (their start date), all access is paused. Their Google Workspace 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 end of day of the team members fourth day of work (3 business days after start date), all access is paused. Their Google Workspace 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.

Note: You can reference what are considered to be “Acceptable Documents” here.

Procedure

  1. There is currently a sync between BambooHR and LawLogix in place where a team member will automatically be added to LawLogix 7 days before their start date.

  2. Section 1 → Employee personal details. New team members fill out this section online personally.
  3. Section 2 → Employee assigns a “Designated Agent” to view, verify and document their government-issued official document(s). The Designated Agent completes this section online personally, but with the new team member and their documents physically in hand next to the Designated Agent.

**If a team member is synced from Greenhouse to BambooHR less than 7 days prior to their start date, we will manually need to run the pops command to sync from BambooHR to LawLogix.

Sending of Employee Instructions

Once the sync has taken place to LawLogix, the People Experience Associate will complete the following steps:

  1. Open Dashboard and locate the team members name.
  2. Click on the team members name.
  3. Then select the I-9 Forms tab
  4. Click on the * next to Electronic I-9
  5. Select who will be the responsible party (People Experience Associate)
  6. Select Review Employee Instructions
  7. Select insert the team members personal email and address and the select Send or Edit Email
  8. Select Send Email

In the event that the automation fails, the People Experience Associate can run the command /pops run uploadtoi9 bambooid in Slack, which will then automatically add the new team member to LawLogix.

The steps below serve as a guide for the People Experience team completing the I-9 process, once the new team member has completed Section 1:

Designated Agent Section

Once the team member has selected a designated agent and inserted the required information in the GitLab I-9 Process - Designated Agent Info google form, the People Experience Associate will log into LawLogix portal and follow the steps below:

  1. Click on the team members name
  2. Select the I-9 Forms tab
  3. Click on the * next to Electronic I-9
  4. Select Review Agent Instructions
  5. Insert the designated agents email address in the To: field (as provided in the Google Form)
  6. Select Send or Edit Email
  7. Select Send Email

The new hire will complete section 1 of the I-9 and upload documents (optional at this step).

Approving the I9

Helpful Guide Slide 94 for Approving I-9

  1. The new hire's name will show up on the dashboard under "I-9 needs approval"
  2. Click on the Date I-9 Created Date (Not the name of the I-9)
    1. Review the I-9
    2. Open the Uploaded Documents - Review the I-9 to check for mistakes, as well as compare to any uploaded supporting documents by clicking the PDF icons. Editing is locked after it has been approved.
    3. If you find any error or issues following the steps here to edit the I-9.
  3. Click Mark Approved on the right side of the page
  4. Select E-Verify Approval
  5. Mark Approve
    • Review the Documents and Review Section 1 and 2 for errors
    • Delete any unnecessary documents uploaded by new hire or designated agent
  6. Approve this I9 - This will now be pushed to E-Verify

E-Verify Photo Matching

Guide

  1. Once an I-9 has been approved and submitted to E-Verify, if Photo-Matching is required a new tab will appear - Manual Processing.
  2. The photo returned by E-Verify will be displayed on the Manual Processing Tab.
  3. Documents previously uploaded are available for review. Click on the appropriate link to compare the document to the image returned by E-Verify. (IE US Passport ID Page).
  4. Compare the photos.
  5. Select the appropriate response.
  6. If the photos match you should receive an Employment Authorized result within 30 seconds.
  7. Save the E-Verify PDF breakdown and upload to BambooHR to the team members Verification folder, along with the documents used to confirm identity.

Team member is no longer joining but I-9 process has started

In the event that a team member notifies us that they will no longer be joining GitLab but the I-9 initial email has been sent, the People Experience team will need to manually terminate the team member from LawLogix.

  1. Click on the date of the I-9 for the team member.
  2. Check that Section 1 has not yet been completed.
  3. Select Employee Details
  4. Click on Terminate Employee
  5. Confirm the warning message that appears.
  6. Refresh the dashboard and the team member should no longer be listed.

Citizenship Confirmation

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.

  1. Administrators can email people-exp@gitlab.com and ask for confirmation that a team member is a US Citizen.
  2. Any People Experience Associate (PEA) can look in the Verification Docs folder in BambooHR for the specific team member, as that is where the documents used to complete the I-9 process are housed.
  3. If the team member has an unexpired US Passport, the PEA may reply: "We can confirm that we have visual proof that this team member possesses an unexpired US Passport, a document only given to US Citizens, therefore they are a US Citizen."
  4. If the team member has an expired US Passport, the PEA may reply: "We can confirm that we have visual proof that this team member possesses an expired US Passport. We will reach out to the team member for visual confirmation of an unexpired US Passport." Then, the PEA will reach out to the team member to gather the scan/image of an unexpired US Passport and then update the email thread.
  5. If the team member has a US Birth Certificate, the PEA may reply: "We can confirm that we have visual proof that this team member possesses a US Birth Certificate, a document only given to US Citizens, therefore they are a US Citizen."
  6. If the team member only has documents other than a US Passport or Birth Certificate, the PEA may reply: "The following team member only provided documents such as a Driver's License and Social Security Card (for example). Since these are available to non-citizens we cannot confirm their US citizenship." Then, the PEA will reach out to the team member to gather a scan/image of either an unexpired US Passport or Birth Certificate and update the email thread.
  7. If the team member has a Permanent Resident Card, the PEA may reply: "I can confirm the team member has an unexpired permanent resident card. Is this acceptable for your system?"
    • Note: This document is not sufficient for SalesForce

Pre-Onboarding, Japan

The PEA team will send two payroll forms for the new team member to complete. This enables our payroll provider to help with the Health Insurance registration.

  1. At least two weeks before the team members start date, the PEA will send both forms listed below to the team member to complete.
  2. To complete the forms the PEA will
    • Employee Regisration Form: Select make a copy and save in team members name. Use the hire date as the effective date
    • Application for change in exemption for dependents: Download and email the form to the team members personal email address to complete.
    • Be sure to use the hire date as the effective date
  3. The PEA will be sure to cc nonuspayroll@gitlab.com in the email sent to the team member so that they can see action has been taken
  4. Once both forms are completed, the PEA will save in BambooHR in the Payroll Folder

Pre-Onboarding, UK

The PEA team will send two payroll forms for the new team member to complete. These forms enable our UK payroll provider (Vistra) to help with their new hire enrollment.

  1. A few days before the new team members start date, the PEA will send both:
    • The new team member the UK email.
      • This email contains: New Starter Checklist link, information about P45, and notification that UK payroll form will be sent from HelloSign
    • Using HelloSign, send the new team member the UK payroll form.
      • To do this go to Template » Use template » GitLab Ltd Uk Payroll Form.
      • On the drop-down menu on the right, choose use template. Fill in as much information as possible from BambooHR and stage in HelloSign for signature using their personal email.
  2. Once the payroll form has been completed and signed by the new team member file the document in BambooHR under Documents/Payroll Forms. If a New Starter Checklist was completed, save it in the same folder. If new team member has a P45, please save it there as well.
  3. When the Payroll form and P45 or New Starter Checklist are complete, send as encrypted attachments to Vistra Payroll along with an encrypted copy of the team member's signed contract. The signed contract is found in the Contracts & Changes folder in the team member's BambooHR profile.
    • This information should not be sent later than Day 1 of a new hire's start date. Do not cc the team as this is sensitive information. Once acknowledged, delete your email.
    • Failure to provide the documents before week one will result in payroll and benefits delays

Pre-Onboarding Issue Creation Tasks

The People Experience Associate will create the Google Mail account first.

Google Mail Account Creation

  1. People Experience Associates create email addresses for new team members using the convention of firstinitiallastname@gitlab.com.
    • Review common naming customs for the team member region. If the team member is from a LATAM country, ensure the email address is aligned with the team members preferred first name and last name(s).
  2. To make sure that we create the GitLab Google Mail account 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.
  3. Before creating the email account, verify that the proposed email is not conflicting with a current account by searching in Google Workspace Admin. If it is, add a letter for their middle name or ask the team member for their choice in preferred letter addition to their email address. After confirming, check the email again within the Google Workspace Admin. Please note that you will not be creating the email address in Google Workspace Admin.
  4. Add the email address to the BambooHR profile under work email. The Okta and BambooHR sync will then create the email address automatically in Google Workspace.

Examples:

BambooHR Profile Data

As part of the Greenhouse<>BambooHR automation, certain fields in BambooHR are pre-filled. The People Experience Associate will check all synced fields have been populated correctly.

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 Department and Division fields are correctly populated. Save your changes and refresh the new team member's profile. All necessary tabs should now appear. Please also create an issue for the People Group Engineer to investigate why the sync did not auto complete the fields.

Hire Date Changes
New team member rejects offer

If a new team member has already been marked as hired in Greenhouse and the sync has taken place, then they reject our offer, the Candidate Experience team will notify both the Senior Director, People Success and the People Experience team in the #people-group-confidential Slack channel.

  1. Once confirmed, The People Experience Associate will verify that the profile has been deleted and then update the People Experience team onboarding tracker to remove the former team member.
  2. If a GitLab email address has already been created, proceed with deleting the email address from Google Workspace Admin. It is important that this step is completed as soon as possible to prevent any issues with the automation

Personal Tab

  1. Name: Verify the team member's full legal name (as much as it is known before seeing legal ID) and preferred name if known has been added correctly as per the custom sync. The sync will import middle name as part of first name, you will need to seperate them if that was the case.
  2. Address: Enter full address, including Street address, City, Region, Zip/Post Code and Country. Only the country is pre-filled by the custom sync. This data can be found in Greenhouse under the 'Details' section.
  3. Locality: (geo area, country). This information should be visible in the offer details. If you have any questions, please reach out to the Total Rewards team.
    • Please note the formatting must be entered exactly as outlined in the location factor file with "area, country" or the integration outside BambooHR will fail. Please only choose a locality from the already created fields in BambooHR. Do not create any new localities.
  4. Region: If not: the three options are Americas, EMEA, or JAPAC.
  5. Work Email Add the GitLab email in the Work Email field. This can not be done by the sync, as the team member is synced before the email is created. Once added, this will sync from BambooHR to Okta and allow the team member to access their Google Mail via Okta.

Jobs Tab

  1. Hire Date:
  2. Role:
    • Leader - if director or above
    • Manager - if has any direct reports
    • Individual Contributor - all others
  3. Cost Center: - it is the same cost center as their manager.
  4. Payroll Type:
    • Employee - paid through Payroll
    • Contractor: IND - Independent Contractor agreement
    • Contractor: C2C - Contractor Company agreement
    • Employee-PEO - Employe employed via a Professional Employer Org
    • Contractor-PEO - Contractor contracted via a Professional Employer Org
  5. Exception to IP Agreement: Not filled in by the sync.
    • Enter Yes if they answered Yes in the PIAA section of their contract. Send an email to VP of Engineering, VP of Product and VP of Legal (Employment) for approval, include the following information:
      • Team Member Name
      • Job Title
      • Information listed by the team member, this information should be specific and not a general web address.
    • File the approved email in the Contracts & Changes folder in the Documents tab in BambooHR. No need to share the doc.
    • Enter No if the team member answered No or None.
  6. Candidate ID: This is the candidate's ID in Greenhouse, and is found by looking at the URL for the candidate. It is an 11-digit number listed between /people/ and the ? symbol.
  7. GHP_ID: This is the GHP ID in Greenhouse. You can find this on the approvals tab for the team member, then scroll to the Openings table and scroll to the far left to get the GHP ID.

If any of the below information has not been correctly synced, rerun the sync. Alternatively, you can use the BambooHR calculator to verify the figures that need to be manually added.

  1. Compensation Table:
    • Compare the data to the signed offer in Greenhouse. Reach out to a Total Rewards Analyst if you need any assistance.
  2. The Pay Frequency and the Pay Schedule should be filled in according to this table:
Country Pay Frequency Pay Schedule
Belgium 13.92 Monthly
Netherlands 12.96 Monthly
United States of America 24 semi-monthly
Canada 26 bi-weekly
Italy 14 Monthly
Philippines 24 semi-monthly
Austria 14 Monthly
Other countries 12 Monthly
  1. On Target Earnings
    • If the team member has variable compensation listed in the signed contract, verify that the information has been added correctly. If yes, continue.
  2. Currency Conversion
    • Effective Date: Hire date for new hires.
    • Exchange Rate Effective Date: is either December 1 or June 1, whichever is more recent. Every December and June, the Total Rewards Analyst will conduct a currency conversion for all team members.
    • The existing Currency Conversion file is used as the SSoT for the currency conversion.
    • Currency Conversation: this should be entered with the factor from yml file, with all 5 decimal places.
    • Local Annual Salary with the appropriate currency code and the converted salary in USD.
  3. Equity:
    • Effective Date: Hire Date
    • Share Vehicle: Stock Options
    • Type:
      • ISO = INC or Federal Entity
      • Internation = All other entities
    • Reason: Hire
    • Shares: # of Shares on offer letter (with comma)
  4. Job information:
    • Effective Date: Hire Date
    • Location: Which entity the new team member is contracted through.
    • Division: Lists the appropriate division the new team member is contracted through.
    • Department: Lists the appropriate department the new team member is contracted through.
    • Job Title: This will list the job title as stipulated on the signed contract.
      • If the title does not exist, ping the total-rewards team in the private Slack channel #peopleops_totalrewards and verify the title is in the correct format before adding.
      • Once confirmed, scroll to the bottom, click "Add New", create and save the new job title.
    • Reports To: Check that the manager listed on the contract is listed correctly in BambooHR.

    • Job Title Speciality: If there is a specialty (this would be found under On Job- Offer Details), this will be inserted in the field. 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 indicate 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.

    • This will list either Part Time or Full Time, check whether this is listed correctly.
  5. Bonus
    • Enter a bonus date, amount and type if applicable.
  6. Employment Status

    • 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.

    • New Team Members with entities that are not mentioned in this file.
      1. Active with the Hire Date as the Effective Date
    • New Team Members in the Netherlands should have 5 entries;
      1. Temporary Contract with 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) )
      2. Temporary Contract Ending with 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)
      3. Probationary Period with 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) )
      4. End of Probationary Period with the date marked as exactly one month from their start date
      5. Active with the date marked as exactly 12 months and one day from their start date (AKA: The day after the Temporary Contract ends)
      6. Example for team member starting June 12, 2020:
Effective Date Employment Status Comment
2021-06-12 Active  
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  
  1. If the team member is a member of the People Group, the People Experience Team is unable to view the probation status. Simply the run the following command in a private Slack message to confirm that the probation period statuses have been added successfully for the team member dependent on their location: /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 Total Rewards Analyst to update the status.
  2. If applicable, Ensure the End of Probation Period date 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, Probation Periods & PIAA handbook page. Please use these probation periods in BambooHR for team members in these specific groups.

Notes Tab

  1. Referrals The sync can't add notes.
    • Add a Note stating "Referred by Jane Doe" if team member was referred. Search in multiple places in their offer details to make sure that you find information if they were referred.

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:

Time Off Tab

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 Canada Corp (Canada), GitLab GK (Japan), GitLab B.V. (Belgium), GitLab Inc (China), and GitLab B.V.(Netherlands).

  1. Click on "Time Off", hover your cursor over the "Employee Accruals" box, and you should see "Accrual Options" appear at the bottom. Click on it and select the appropriate policy from the dropdown. The effective date is their hire date.
  2. Click Save.

Onboarding Issue Creation

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.

  1. Before creating the onboarding issue, ensure that all information entered BambooHR is accurate and complete.
  2. In Slack, go to your profile as if you were going to send a Slack message to yourself. Type the command /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.
  3. You will be pinged in Slack once the onboarding issue is created, which usually takes 30 seconds or so. The ping will include a link to the new onboarding issue.
  4. Check and update if applicable the Name from Legal to Preferred name.
  5. If the new team member is on the executive team, or if the new team member reports to a member of the executive team, please also assign the issue to the appropriate Executive Business Administrator(https://about.gitlab.com/handbook/eba/).
  6. Update if applicable the title with the Specialty as the bot does not add the Specialty so it must be manually added.
  7. If the manager is not automatically assigned and listed in the issue, add them. It could be because the employee's manager uses a name in GitLab that is very different from the one in BambooHR, and they don't use their @gitlab.com email ID as the primary email ID in GitLab. They will then manually need to be assigned.
  8. Copy and paste the link into the People Exp/Ops Task Tracker sheet in the team member's specific column on their line. Please note that this document is only viewable to the People Experience and People Operation Specialist Teams due to personal information.
  9. If you are part of the People Experience team, IT Ops team, new team members's manager or onboarding buddy please note there are additional steps to complete directly in the new hire's onboarding issue in the 'Before Starting at GitLab' section.

People Experience Pre-Start Onboarding Tasks

Request Signature for Code of Conduct 2021 & Acknowledgement of Relocation 2021

Each assigned People Experience Associate will send their new team members our Code of Conduct 2021 and Acknowledgement of Relocation 2021 forms for review and signature.

  1. In BambooHR, go to the Files section.
  2. Be sure you are in the Signature Templates section.
  3. To the right of the Code of Conduct 2021, click on the triangle to the right of the gear icon and click Request Signature.
  4. Choose "Send a signature request to: Only some people"
  5. Type in the name of your assigned team members. Please note that self-service option needs to have been activated in BambooHR in order for us to request a signature.
  6. Message to Signers: Dear new team member, we are so happy you are part of the GitLab team. Please take a moment to sign this document. Thank you!
  7. Click Send Request.
  8. Repeat the above process for Acknowledgement of Relocation 2021.
  9. The People Experience Associate in the respective bi-weekly rotation will check to see whether the team members that started during those weeks have signed the Code of Conduct 2021 and Acknowledgement of Relocation 2021 form.
  10. Click on Code of Conduct 2021.pdf or Acknowledgement of Relocation 2021.pdf and notice the team members who were sent the document and have still not signed.
  11. If a team member was sent the document for signature or reminder over 2 weeks in the past, click the Bell icon on their line at the far right. Clicking on the bell will send them a notification to sign.

People Experience Day 1 Onboarding Tasks

Once you have seen the team member's legal ID (either through work eligibility confirmation or employee upload), please edit the 3 Name fields (First Name(s), Middle Name(s), Last Name(s)) to ensure that the team member's full and complete legal name is shown in BambooHR.

Onboarding Welcome Email

The new team member will automically recieve a "Welcome to Onboarding" email. The People Experience team will be CCd on this process. More information about this email automation can be found here. The team member will follow the instructions in the welcome email to access Okta and their GSuite account (this is no longer a manual process).

New Hire Swag Email

The "New Hire Swag" email is automatically sent to the new hire on their first day with GitLab, with people-exp @gitlab.com cc'ed in the email. The email will state that the team members 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.

The People Experience Associates assigned to the respective team members onboarding is responsible for ensuring that the email is successfully sent on Day 1 and will be checked off in the onboarding issue as part of the tasks list.

Okta Issues

In the event that team members experience any difficulties with gaining access to their Okta account when the IT Ops team is not available, the People Experience team are able to submit a reset password option via the Okta Admin Panel as per the following steps:

Invite to Moo

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.

Create Interview Training Issue

  1. The Interview Training Issue will be created automatically one week after the team members start date. Information about this automation.
  2. This task is only applicable for new team members that are people managers.

Create Becoming a GitLab Manager Issue

  1. The Becoming a Manager Issue will be created automatically one week after the team members start date. Information about this automation.
  2. This task is only applicable for new team members that are people managers.

Compliance and Ownership

The People Experience Team is responsible for monitoring and facilitating the completion of the onboarding issue.

People Experience Associates will complete the following tasks.

Timing

Before Start Date

2 Business Days Prior:

After Start Date

On Start Date

After Day 1

After Day 3

After Week 1

Total Rewards Analyst Onboarding Tasks

  1. Audit the BambooHR Entry. Download a copy of the contract from the Documents Tab. Verify the information (start date, title, stock, etc) matches the entries in BambooHR as outlined in Adding a New Team Member to BambooHR. Add US team members to the appropriate Benefit Group.
  2. If all the information is correct, mark the new hire as complete on the "Payroll Changes Report" in BambooHR.
  3. At the end of each week a Total Rewards Analyst will review all data entered into BambooHR through the Payroll Change Report for audit purposes. Once a month an audit should be conducted from all payroll providers to ensure the salary information matches BambooHR

Onboarding Process for Rehires

In the event that a former team member is rehired with the company, they will still need to go through standard onboarding. There are different factors that need to be considered and actioned prior to the team member joining. For example, the team member will still need to complete all Security and Compliance pieces to ensure that as a company we are remaining compliant (Code of Conduct, Security training, Employment Verification).

Candidate Experience Specialist Team

People Experience Team

Onboarding Process for Interns

Internships are utilized when we are sponsoring a specific program for students to earn credit to their school/university. Although the interns will not be official team members, onboarding is still required for security and compliance reasons. Once an intern is marked as hired in Greenhouse, the automation in place will sync the intern to BambooHR and the People Experience team will be notified via Slack alerts channel.

Creating the Onboarding Issue

We would follow the same onboarding issue creation process when creating the issue for the Interns. The template has been edited to allow for additional tasks to be added for the interns.

I-9 Process

The standard I-9 process will be implemented between BambooHR and LawLogix for paid interns.

BambooHR Profile

The BambooHR Profile will follow all of the same rules as a normal onboarding with these exceptions:

Offboarding Interns

If the intern is not offered full time employment with GitLab, the same offboarding process will need to take place to ensure that access is deactivated and the intern is removed from all systems.

Talent Acquisition or the CES team will notify the People Experience team via Slack when an intern is not offered full time employment with GitLab so that the offboarding can be scheduled at the date of the end of the intership agreement.

Onboarding Process for Interns converting to Hired Team Members

In some instances, the interns that have been onboarded may be hired on a full time basis after successfully completing their internship with GitLab. This lists the steps required from all the different stakeholders:

People Business Partner / Managers

Recruitment

Candidate Experience Specialist

Total Rewards

As the interns already have entries in BambooHR, an update will be needed with the new employment terms.

Payroll

People Experience

Onboarding Core Team Members

Core team members are team member that are not employed by GitLab but are part of the wider GitLab community. These team members can be granted access to certain systems at request from the Community Relations team by creating the respective Core Team Member Onboarding Issue.

The Community Relations teamwill ping the People Experience team in the #peopleops Slack channel for assistance.

There are tasks within the issue that need to be completed by the People Experience Team.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license
View page source — Edit in Web IDE — please contribute. Creative Commons License