Welcome to the People Group handbook! You should be able to find answers to most of your questions here. You can also check out pages related to People Group in the section below. If you can not find what you are looking for please do the following:
general if you're not sure. Please use confidential issues for topics that should only be visible to GitLab team-members. Similarly, if your question can be shared please use a public issue. Tag @gl-people-connect-team or @gl-hiring so the appropriate team members can follow up.
#people-connect Slack chat channel for questions that do not seem appropriate for the issue tracker - if your question contains personal data or sensitive information we encourage you to direct message the People Connect Bot which can be found in the Apps Dropdown within Slack. For access requests regarding Google or Slack groups, please create an issue here: https://gitlab.com/gitlab-com/team-member-epics/access-requests. For questions that relate to Payroll and contractor invoices please direct your question to the #payroll, #expense-reporting-inquiries and #finance channel for Carta. Regarding questions for our recruiting team, including questions relating to access, or anything to do with Greenhouse, referrals, interviewing, or interview training please use the #talent-acquisition channel.#it_help. The channel topic explains how to create an issue. For urgent matters you can mention @it-ops-team.In general, the People Group is here to support GitLab's mission by bringing top talent into GitLab, and then enabling team members to make meaningful contributions in alignment with our values. Please don't hesitate to reach out with questions or ask for support!
The People Group works together as one team, made up of five departments: People Operations, Talent and Engagement, Total Rewards, People Business Partners, and Diversity, Inclusion, and Belonging (DIB).
| Department | Teams |
|---|---|
| People Operations | People Connect, Employment Solutions, People Compliance, People Tools & Technology, People Analytics, Team Member Relations |
| Talent and Engagement | Talent Acquisition; Candidate Experience, Talent Acquisition Operations and Insights, Sourcing, Talent Brand Engagement; Learning & Development, Engagement |
| Total Rewards | Global Compensation, Benefits, and Equity Strategy |
| People Business Partners | Aligned to Engineering, Product, Sales, Marketing, and G&A |
| DIB |
If team members need emergency support from GitLab's People team, please post in the #people-connect Slack channel marked URGENT. The #people-connect channel is monitored during most working hours and is the centralized support platform for all people-related queries. Please do not include any sensitive or private information in your message in the #people-connect channel. Team members must direct message the People Connect Bot to relay any personal data or potentially sensitive information. The People Connect bot which can be found by searching the 'apps' section of Slack. Read more about our People Connect methods of engagement.
In critical cases, the VP, People Operations, Technology & Analytics is contactable 24/7 via their mobile numbers that appear in their Slack profile.
We trust team members to always use their best judgement when facing any emergency. Team members are encouraged to dial their country's emergency services number for any critical and/or medical emergency. In the case that other team members are aware of a team member's emergency (during a Zoom call for example) and wish to call that country's emergency services on the original team member's behalf, we do not recommend this as only certain People Ops team members have access to team member addresses and we would take on the role of communicating with emergency services, should this extremely rare situation arise.
In the event a team member is in an unsafe situation due to a natural disaster, please see the Disaster Recovery Plan page.
As stated in the Code of Business Conduct and Ethics, we have a section related to reporting concerns about violations of the Code of Business Conduct and Ethics. GitLab has engaged Navex to provide EthicsPoint, a comprehensive and confidential reporting tool, an anonymous ethics hotline for all team members. The purpose of the service is to insure that any team member wishing to submit a report anonymously about conduct addressed in the Code of Business Conduct and Ethics can do so without the fear of retaliation.
In addition to EthicsPoint, GitLab has engaged Lighthouse Services to provide an anonymous reporting hotline for all team members to submit reports if they have concerns regarding team member relations. Reports may cover but are not limited to the following topics: wrongful discharge or disciplinary action, sexual harassment, discrimination, conduct violations, alcohol and substance abuse, threats, improper conduct, violation of company policy.
Please note that the information provided by you may be the basis for an internal and/or external investigation into the issue you are reporting and your anonymity will be protected by Lighthouse to the extent possible by law. However, your identity may become known during the course of the investigation because of the information you have provided. Reports are submitted by Lighthouse to a company designee for investigation according to our company policies.
Lighthouse has a toll free number and other methods of reporting are available 24 hours a day, 7 days a week for use by team members.
In addition to EthicsPoint and Lighthouse, please review the Team Member Relations page. GitLab also offers a Harassment Complaint Form that any team member may use to document any instance of any type of workplace harassment. Simply copy the form, fill it out with your information and send it to our Team Member Relations Specialist at [email protected].
This table lists the aliases to use, when you are looking to reach a specific group in the People Group. It will also ensure you get the right attention, from the right team member, faster.
| Subgroup | GitLab handle | Slack Group handle/channel | Greenhouse | Issue tracker | |
|---|---|---|---|---|---|
| People Business Partners | @gl-peoplepartners, Please add the pbp-attention label to any issue or MR that requires PBP review, collaboration, or feedback |
peoplepartners@ gitlab.com | @peoplepartners | n/a | |
| Total Rewards | @gl-total-rewards | total-rewards@ gitlab.com | #people-connect | n/a | |
| People Compliance Partner | TBA | TBA | TBA | n/a | |
| People Connect Team | @gl-people-connect-team | people-connect@ gitlab.com | @people-connect-team | n/a | |
| Team Member Relations | @atisdale-ext | [email protected] | n/a | n/a | |
| Absence Management Team | @lyndemeiers | [email protected] | #people-connect | n/a | |
| People Group Engineering | No alias, create issues for People Engineering here | n/a | #people-ops-eng | n/a | |
| Diversity, Inclusion and Belonging | No alias yet, @mention the | ||||
| Diversity, Inclusion and Belonging Partner | diversityinclusion@ gitlab.com | n/a | n/a | Diversity, Inclusion and Belonging issue tracker | |
| Learning and Development | @gitlab-com/people-group/learning-development |
learning@ gitlab.com | #learninganddevelopment | n/a | L&D Issue Board |
| Talent Acquisition | @gl-talent-acquisition | recruiting@ gitlab.com | @talent-acquisition-team | n/a | |
| Employer Branding | No alias yet, @mention the Senior Talent Brand Manager | employmentbranding@ gitlab.com | n/a | n/a | |
| Candidate Experience Specialist | @gitlab-com/gl-ces | ces@ gitlab.com | @ces | @ces* | |
| Talent Acquisition Operations and Insights | @gl-talent acquisitionops | talentacquisitionops@ gitlab.com | @talent-acquisition-ops | @talent-acquisitionops | |
| Sourcing | @gl-sourcingteam | n/a | @sourcingteam | n/a |
On this page you can find our People Manager Calendar and All Team Member Calendar. The goal of these pages is to ensure that team members and People Managers can plan ahead and have an overview of upcoming programs and timelines.
Each quarter a Slack reminder will go out in #people-manager-and-above channel to review the next quarter calendar events. Each month shows Task, which outlines the people manager responsibility associated with the specific program, and (if applicable) highlights the Key Date. We will also leverage our Manager Newsletter and the Company Newsletter for broadcasting our programs widely.
Please reach out to your aligned People Business Partner (PBP) to engage in the following areas:
| Contact | Division - Department |
|---|---|
| Anjali Kaufmann | G&A: People Group, Finance, LACA, CoS (Interim) |
| Denise Parsonage | Marketing: Awareness, Brand Activation, Campaigns, CMO Executive, Communications, Developer Relations, Content Marketing, Digital Design, Digital Marketing, Field Marketing, Marketing Ops, Partner Marketing, Sales Development, and Search Marketing |
| Carolyn Bednarz | Sales: Enterprise Sales |
| Carlie Russell | Sales: Customer Success, Channel and Alliances. |
| Lauren Tepper | Sales: Commercial Sales, Field Operations |
| Giuliana Lucchesi | Engineering: Development and Incubation Engineering; Product: Product Management and UX; CISO: Security |
| Kristina Bullock | Engineering: CTO, Customer Support, Quality/Infrastructure |
If you would like People Business Partners' input, collaboration, or feedback on an issue or MR, please add the pbp-attention label, which will flag the issue for triaging on our People Business Partner issue board. See the People Business Partner Issue Board section below for more information on our triaging and lableing process.
The People Business Partners (PBPs) have an issue board to track collaboration on issues across GitLab.com to keep us efficient and collaborative with other teams.
We utilize labels for triaging amongst the PBPs, and to indicate to other teams the level of priority for the PBPs and the status (doing, done, etc.)
pbp-attention label is added by team member/group seeking input, collaboration, or feedback on an issue or MR. This will flag the issue for triaging on our People Business Partner issue board. Note: While MRs will not appear on our board, we ask that the pbp-attention label is added regardless for analytics purposes.pbp::low 1 PBP DRI with 1 additional reviewerpbp::medium 1 PBP DRI with 2 additional PBP reviewerspbp::high 1 PBP DRI with 3 additional PBP reviewers (at least one should be at the Director level)pbp-DIB (Diversity, Inclusion, & Belonging)pbp-LD (Learning & Development)pbp-TR (Total Rewards)pbp-legalpbp-peopleopspbp-talent-acquisitionpbp-otherpbp-done label when PBP action is complete.You may reference the GitLab.com labels for an overview of all labels included in the PBP issue board triaging and labeling process.
The Legal-Employment team, collaborates with and provides support to the People team in many functional areas.
Email approval from the Senior Director of Legal, Employment is required prior to engagement with external counsel to allow for accurate tracking of costs.
Invoices will be sent to Senior Director of Legal, Employment, for approval.
The legal, employment team may require support from the people connect team, for communicating a country specific legal requirement to team members, to consult with team members in an entity country if necessary or to arrange legally required contract amendments, to name just a few examples. As these matters may relate to individual team members or groups of team members, they are appropriately managed in a confidential manner.
If the legal, employment team makes a request for support or assistance from the people connect team, the request should be formulated using a template (linked here, though accessible internally only to legal, employment and the people connect teams). The request should include all the required detail and explanation to enable people connect to support, including:
To make a request, a copy of the template should be saved, filled out as above, dated and passed to Alissa Meeks/the People Connect Manager so the request can be assessed and assigned to a member of the people connect team for completion. Once assigned, the member of the people connect team who will be assisting with the request should touch base with the member of the legal, employment team who has made the request, to confirm that the request is being worked on and so it's easy to collaborate on finishing out the task.
All tasks will be assigned via slack in the #pbp-peopleops slack channel. This is a private channel. The People Connect Team, will self-assign a task, within 24 hours and comment in slack on the request to confirm.
Please note that the source of truth for role responsibilites is the job family for the People Connect Team. The table below is meant to provide a quick overview of some of the core responsibilities for the team.
| Responsibility | Response Timeline |
|---|---|
| Onboarding | 2 weeks prior to start date |
| Offboarding | Immediate action for involuntary & 24 hours for voluntary |
| Career Mobility | Within 24 hours |
| Letters of Employment | Within 12 - 24 hours |
| Employment Verification | Within 12 - 24 hours |
| Anniversary Emails | Last day of the month |
| Slack and Email Queries | Within 12 - 24 hours |
| Probation Period Notifications | Daily (when applicable) |
| Evaluate onboarding surveys | As responses are submitted |
| Determining quarterly winners of the onboarding buddy program | Last week of each quarter |
| People Connect Shadow Program | As requested by other team members |
| Contract Renewals | 30 days or more prior to team member's renewal date |
| Exit Interviews | During voluntary offboarding team member's last week |
| Administration of the signing of our Code of Business Conduct and Ethics | Annually in Feb/March |
| US Unemployment Claim Management | As Needed and Audited Quarterly |
Other listed processes for the People Connect Team can be found here
| Responsibility | Response Timeline |
|---|---|
| Relocations | As requested, usually completed 30 days or more prior to team member's relocation date |
| Country Conversions | As soon as approval is given by CFO. Conversion turnaround time can take from 4-12 weeks depending on a variety of factors. |
Please review the frequently requested section of the People Handbook before reaching out to the team. The page includes information on accessing a team directory, requesting a letter of employment, mortgage forms, the companies reference request policy, ordering business cards, and changing your name in GitLab systems.
GitLab does not actively search for LinkedIn profiles that have inaccurate information about being a GitLab Team member. However, there are instances where a profile is identified and there is question on whether the person is truly a GitLab team member. Here is the process for flagging a potentially inaccurate profile and the actions that the People Connect Team will do to confirm and potentially report a profile.
@community-team tag.We use Workday to maintain team member information. All team members (all contract types) are in Workday. Workday is managed and maintained by the People Tools and Technology team.
See our Workday Guide to learn more about how to use Workday.
Administrative access to CultureAmp will be limited based on role and responsibility. There are 3 different levels of access:
To request access please open an access request with the type of account access requested and the business need. You can assign the access request to Anesia Chan @anechan and Laura Janssen `@Laura-Janssen (as backup) for review and approval. The default admin access will be the Survey Creator administration rights unless other access is specified. Please note that Survey Data Analyst admin rights will not be granted to team members outside of the People group with out permission from the Chief People Officer.
If you need assistance reviewing your CultureAmp Survey, please complete this issue template to alert the People Connect Team.