Welcome to the People Operations handbook! You should be able to find answers to most of your questions here. You can also check out pages related to People Operations in the next section below. If you can't find what you're looking for please do the following:
generalif you're not sure. Please use confidential issues for topics that should only be visible to GitLabbers. Similarly, if your question can be shared please use a public issue. Tag
@gl-hiringso the appropriate team member can follow up.
#peopleopschat channel for questions that don't seem appropriate for the issue tracker. For access request regarding Google and Slack groups, kindly create an issue here: https://gitlab.com/gitlab-com/access-requests. For questions that relate to ADP, Payroll, Invoicing or Carta, kindly direct your questions to the
#financechannel. With questions for our recruiting team, including questions relating to access or anything to do with Greenhouse, referrals, interviewing and interview training please use the
#recruitingchannel. For more urgent general People Operations questions, please use the mention
@peoplegeneralto get our attention faster.
In general, the People Operations team and processes are here as a service to the rest of the team; helping make your life easier so that you can focus on your work and contributions to GitLab. On that note, please don't hesitate to reach out with questions! In the case of a conflict between the company and a team member, People Operations works "on behalf of" the company.
GitLab uses Slack profiles as an internal team directory, where team members can add their personal contact details, such as email, phone numbers, or addresses. This is your one-stop directory for phone numbers and addresses (in case you want to send your team mate an awesome card!). Feel free to add your information to your Slack profile (this is completely opt-in!) by clicking on "GitLab" at the top left corner of Slack, "Profile & Account", then "Add Profile" (for the first time making changes) or "Edit Profile" (if your account is already set up) to make any changes!
+[country code]in front of your phone number.
Once per month, GitLabbers with Anniversaries will be notified that they can redeem their Anniversary Gift in the Swag Store. Celebrate by sending the team member an email (template below) and post on the
#celebrations channel on Slack so all team members can help them celebrate.
Anniversary Swag Template: "Happy GitLab Anniversary! Please use this code [insert code] to redeem your anniversary swag! You will need to login or create an account in the swag store to receive your special gift! The username will be your GitLab email. Please let People Ops know if you have any questions."
The code for the swag store anniversary campaign is located in the People Ops vault in 1Password.
Monitor the swag store open orders to place orders that team members have entered for their anniversary swag.
The company encourages all GitLabbers to take a day of vacation on their birthday by utilizing our paid time off policy.
If you need a letter from GitLab verifying your employment/contractor status, please send the request to People Ops citing what information is needed. We will provide most recent title, dates of employment, and salary information. We will also verify, but not provide National Identification Numbers. People Ops will send you the letter once it is completed. In addition, if the request comes from a third party, People Ops will always verify that the information is appropriate to share.
GitLabbers are not authorized by the company to speak on its behalf to complete reference requests for GitLabbers no longer working for GitLab. If a team member would like to give a personal reference based on their experience with the former team member, it must be preceded by a statement that the reference is not speaking on behalf of the company. To reinforce this fact, personal references should never be on company letterhead and telephone references should never be on company time. You do not need permission from GitLab to give a personal reference. Remember to always be truthful in reference check and try not to give a majority negative reference; instead refuse to provide one. Negative references can result in legal action in some jurisdictions.
If an ex team member acted in a malicious way against GitLab we'll do a company wide announcement on the company call not to provide a reference.
Business cards can be ordered through Moo. Please let People Operations know if you have not received access to your account on Moo by the end of your first week with GitLab. Place the order using your own payment and add it to your expense report. If you need any assistance, let People Ops know.
Once you are logged in, you will follow these steps to create your cards:
NPS stands for "Net Promoter Score". GitLab has two forms of NPS surveys: eNPS for all employees (where "e" stands for "Employee"), and an onboarding NPS. These surveys gauge employee satisfaction and how likely employees are to recommend GitLab to others as a place to work.
People Ops will send out an eNPS survey twice yearly to all employees.
The onboarding NPS survey is a 60-day survey for new hires. To help People Ops understand your experience and improve the onboarding process, please complete the onboarding survey after you have been working for GitLab for at least 2 months. People Ops will send reminders to team members to complete the survey.
People Operations will send flowers for a birth, death, or significant event of a team member. This policy applies to an immediate relationship to the GitLab team member. Management can send a request to People Operations in order to ensure that a gift is sent in the amount of 75-125 USD.
We use BambooHR to keep all team member information in one place. All team members (all contract types) are in BambooHR. We don't have one contact person but can call BambooHR if we want any changes made in the platform. The contact info lives in the Secretarial Vault in 1Password.
Some changes or additions we make to BambooHR require action from our team members. Before calling the whole team to action, prepare a communication to the team that is approved by the Chief Culture Officer.
Team Members have employee access to their profile in BambooHR and should update any data that is out-dated or incorrect. If there is a field that cannot be updated, please reach out to the People Ops Analyst with the change.
Our company and office phone lines are handled via RingCentral. The login credentials are in the Secretarial vault on 1Password. To add a number to the call handling & forwarding rules:
For roles directly relating to Research and Development in the Netherlands, GitLab may be eligible for the WBSO (R&D Tax Credit).
As of 2019 GitLab must submit three applications each year and the deadlines for those are as follows:
There is a translated English version of the application template located in the WBSO folder on the Google Drive. The applications should be completed by a Product Manager, responsible for features or a service within GitLab, who can detail the technical issues that a particular feature will solve. Assistance on completing the application can also be sought from the WBSO consultant (based in the Netherlands). The contact details for the consultant can be found in a secure note in the People Ops 1Password vault called WBSO Consultant. People Operations will assist with co-ordinating this process. It is currently owned by Finance.
Each year a spreadsheet with the project details and hours logged against the work done on the project(s) will need to be created. This is for the entire year. The current hour tracker is located in the WBSO folder, on the Google Drive, and shared only with the developers that need to log their hours (located in the Netherlands), People Operations, Finance and the WBSO consultant. Once the projects have been completed for the year, the WBSO consultant will submit the hours and project details to claim the R&D grant from the RVO. The WBSO consultant will contact People Operations should they have any queries.
When your employment contract is for a fixed period of time (e.g. 12 months) you'll need a "werkgeversverklaring". This document describes your salary and states that your employer expects to continue to employ you after the contract expires (assuming the performance of the employee doesn't degrade). This document has to be filled in by hand, preferably using blue ink, and must be signed and stamped. If there is no stamp (as is the case for GitLab) an extra letter (also signed) must be supplied that states the employer has no stamp. While the language of these documents doesn't matter, the use of Dutch is preferred.
Employees also have to provide a copy of a payslip that clearly states not only their monthly salary but also their annual salary. These numbers must match the numbers on the "werkgeversverklaring" down to the decimals. Mortgage providers may also require you to provide information about your financial status, usually in the form of a report/screenshot of your total financial status (including any savings you have). The requirements for this seem to vary a bit between mortgage providers.