People Group
Welcome
Welcome to the People Group handbook! You should be able to find answers to most of your questions here.
People Group Vision
The People Group works together to establish a high performance and results driven culture where a diverse and inclusive team can experience a meaningful career.
We support a culture that enables people to do their best work and advance their careers while fully contributing to advancing GitLab’s business results. We hire, promote, and recognize team members who best live our values.
The People Group strategy is to set the foundation for GitLab’s 3 year strategy through a focus on attracting and retaining diverse talent, creating a high performance culture with a focus on efficiency and quality results, driving divisional success through talent programs, and cultivating an equitable and inclusive culture.
We’ve published more information about how this vision translates to strategy and OKRs for GitLab team members in this internal-only presentation.
Connect with us
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:
- The People Group holds several subprojects to organize the people group; please create an issue in the appropriate subproject or
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.- Please note that not all People Group projects can be shared in an issue due to confidentiality. When we cannot be completely transparent, we will share what we can in the issue description, and explain why.
- Employment Issue Tracker: Only Onboarding, Offboarding and Transition Issue Templates are held in this subproject, and they are created by the People Connect Team only. Interview Training Issues, are held in the Training project and created by the Talent Acquisition team. Please see the interviewing page for more info.
- People Connect; Please create a case for the People Connect team with any questions that do not seem appropriate for the issue tracker within HelpLab - choosing the applicable template/category applicable. 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, Expenses or Equity, please direct your question to the respective teams in HelpLab. 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. - If you need to discuss something that is confidential/private (including sensitive matters surrounding your team), you can open a HelpLab Case the Team Member Relations team. Any team member, regardless of location, can use this form to discuss a private sensitive matter.
- If you need help with any technical items, for example, 2FA, please ask in
#it_help
. The channel topic explains how to create an issue. For urgent matters you can mention@it-ops-team
.
The People Group: One Team Mosaic Video
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; Talent Development, Engagement, Talent Management |
Total Rewards | Global Compensation, Benefits, and Equity Strategy |
People Business Partners | Aligned to Engineering, Product, Sales, Marketing, and G&A |
DIB |
Need Help?
In Case of Emergency
If team members need emergency support from GitLab’s People team, please create a case in HelpLab. HelpLab is monitored during most working hours and is the centralized support platform for all people-related queries. 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.
How to Report Violations
As stated in the Code of Business Conduct and Ethics, we have a section related to reporting violations. 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 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.
- Website: https://report.syntrio.com/_StandardCustomURL/LHILandingPage.asp
- USA Telephone:
- English speaking USA and Canada: 833-480-0010
- Spanish speaking USA and Canada: 800-216-1288
- French speaking Canada: 855-725-0002
- Spanish speaking Mexico: 01-800-681-5340
- All other countries telephone: +1-800-603-2869
- E-mail: reports@lighthouse-services.com (must include company name with report)
- Fax: (215) 689-3885 (must include company name with report)
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 teammemberrelations@gitlab.com.
How to reach the right member of the People Group
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 | HelpLab | n/a | |
People Compliance Partner | TBA | HelpLab | TBA | n/a | |
People Connect Team | @gl-people-connect-team | HelpLab | @people-connect-team | n/a | |
Team Member Relations | @atisdale-ext | teammemberrelations@gitlab.com | n/a | n/a | |
Absence Management Team | @lyndemeiers | leaves@gitlab.com | HelpLab | n/a | |
People Group Engineering | @gl-people-engineering | No email group, create issues for People Engineering here | #peopleops-eng | n/a | https://gitlab.com/groups/gitlab-com/people-group/peopleops-eng/-/boards/3941171 |
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 | |
People Analytics | No alias, create issues for People Analytics here | n/a | @peopleanalyticstriage | n/a | People Analytics Issue Board |
People Group Program Calendar for Managers and Team Members
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.
Communication on People Programs that require action
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.
Updating calendars
Each month on the first Monday there’s a calendar reminder to update the calendars on that date. This calendar reminder includes People Business Partners and the DRI in L&D. Also with sharing the calendars in the news letters People Business Partners and L&D will be tagged.
The goal of the calendar is to include information at least two quarters ahead of the current quarter. For questions about the updates to the calendars you can always reach out to People Connect.
Support provided by the Legal, Employment team to the People Group
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.
When support from the People Connect team is required by the Legal, Employment team
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:
- An explanation of what is needed
- Whether there’s a timeline on the request (ensuring people connect are provided with as much lead time as possible)
- Whether all the information needed, has been provided, eg contact names, dual language translations if applicable, links to any relevant documents etc
- A note on whether an FAQ to share with team members is needed or whether people connect have enough information to answer any questions which might arise
- Whether there are any follow up actions for legal or for people connect
- A short explanation or summary (if necessary) or courtesy update for the managers of any affected team members
- Whether confirmation of completion is needed
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.
Support provided by the People Connect team to the People Business Partner team
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.
People Connect Responsibilities & Response Timeline
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.
People Connect 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 24 hours |
Employment Verification | Within 24 hours |
Anniversary Emails | First day of the following month |
HelpLab Queries | Within 24 hours |
Probation Period Notifications | Daily (when applicable) |
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
Employment Solutions Team
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 vary based on a variety of factors. |
Frequently Requested
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.
Addresses
- For the mailing addresses, see our visiting page.
- For the NL office, we use addpost to scan our mail and send it to a physical address upon request.
Reporting potential inaccurate LinkedIn Profiles
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.
- Team members should first check in Slack and/or on the organizational page to determine if the team member is a current GitLab team member.
- If the team member cannot confirm the profile, team members should reach out to the People Connect Team via HelpLab with the LinkedIn profile in question.
- The People Connect Team member will confirm in Workday that they are not/have not been a team member.
- The People Connect Team member will confirm with talent acquisition to confirm if they have ever been interviewed, made an offer or were declined.
- The People Connect Team member will reach out to the Developer Relations team to confirm if they are an active wider community member via the #developer-relations Slack channel, using the
@devrel-team
tag. - If they are a confirmed member of the wider community but not a team member, the Developer Relations team will reach out the profile and ask them to change their profile to match their GitLab involvement.
- If they are not a current member of the wider community and talent acquisition has confirmed they do not have a profile in Greenhouse, talent acquisition will create a Do Not Hire profile.
- The People Connect Team member will report the account to LinkedIn via the Reporting Inaccurate Information on Another Member’s Profile
Using Workday
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.
Using Culture Amp
Administrative access to CultureAmp will be limited based on role and responsibility. There are 3 different levels of access:
- Account Administrator access can manage account setting and team member data, create surveys and has access to all survey results.
- Survey Creator administrator access can create, manage and design surveys, select participants and share results.
- Survey data analyst administrator can export raw data from all surveys enabled for raw data extract.
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 support with a specific CultureAmp Survey, please complete this issue template to alert the People Analytics Team.
Take Time Out to Learn
At GitLab, we believe that career growth is non-linear. In practice, non-linear career growth is an opportunity for team members to increase efficiency with new skills, develop as leaders with new responsibilities, and grow as an expert in their field.
But growth only happens when we make intentional time and space to learn.
As a People Group, we’re embracing this attitude of continuous learning together, with the challenge that, as a team, we can spend a total of 300 hours learning before the end of FY25 Q3! We encourage everyone to participate, spending approx. 2 hours per month learning something new, as a way to prioritize your development and use work time to uplevel and upskill.
At the end of the quarter, we’ll ask folks to self-report hours spent learning, and take a tally of total People Group learning hours.
Here are a few ways you might spend time learning this quarter:
- Create an IGP to track and monitor your growth goals
- Utilize the Growth and Development Fund to engage in a class or conference
- Organize a job shadow or internship for learning to increase exposure and collaboration with different roles and teams.
- Attend an AMA or async Group Conversation, and contribute by asking a question.
- Organize a discussion on your team about a shared topic (i.e. article, book, or podcast on a topic that is relevant to your team’s work)
- Attend a TMRG career growth event
We encourage everyone to have an ongoing conversation about career growth with their manager during weekly 1:1s. If this isn’t already part of your weekly check in, consider adding it to your agenda template now!
Investing in your growth is essential for both your individual success and the success of our entire team. Let’s start learning together!
Other pages related to the People Group
People Business Partners
Total Rewards
People Operations
- Code of Business Conduct and Ethics
- Promotions and Transfers
- Employment Solutions (International Expansion)
- Contracts
- Probation Periods & PIAA
- Onboarding
- Offboarding
- Celebrations
- People Connect
- People Analytics
Talent Acquisition
Learning and Development
Diversity, Inclusion and Belonging
Other People Group Links
- People Policy Directory
- Underperformance
- Visas
- Leadership handbook
- People Group READMEs
- Women in Sales Mentorship Pilot Program
- People Key Performance Indicators
- People Performance Indicators
Anti-Harassment Policy
Competencies
Contracts, Background Screenings, Probation Periods & PIAA
Directly Responsible Individuals (DRI)
Employment Solutions - Overview
Engagement Surveys and Employer Awards
Frequently Requested
Gender and Sexual Orientation Identity Definitions and FAQ
GitLab Internal Acceptable Use Policy
GitLab Offboarding
GitLab Onboarding
GitLab People Connect
Connect with Us
GitLab Team Members can now reach out to us at the touch of a button via HelpLab.
If you are external to GitLab but have a question for our team be sure to email people-connect@gitlab.com.
Introduction
People Connect is GitLab’s centralized team member support model that provides a single point of contact (SPOC) for all people-related questions and requests - taking the guesswork out of finding answers that may not be immediately apparent in the handbook, while creating space for team members to remain productive and focused on what they do best.
GiveLab Volunteer Initiatives
Guidance on Feedback
Incident Response
Learning & Development
Overview
Purpose
Why we exist: GitLab Talent Development (commonly referred to as “Learning & Development”) exists to enhance team member performance, expand capabilities, and further develop skills that make GitLab team members the top talent in the industry. We strive to foster a culture of continous growth so that GitLab remains a great place to work. Positive impact on team member experience leads to a positive impact on results, which leads to a positive impact on GitLab customers.
New Hires, Celebrations and Significant Life Events
Organizational Change Management
Introduction
GitLab is growing fast and we have been ranked as one of the fastest-growing private software companies. Headcount has nearly doubled in the last year and we have plans to continue to grow. As we scale, there will be more and more changes to how we operate as an organization. New technology will be introduced to make us more efficient, new processes will be introduced to improve transparency, functional groups will be redesigned and adjusted to meet our growing headcount and strategic objectives, job families will change, and policies in the handbook will be altered that have a big impact on how we operate.
Paid Time Off at GitLab
Introduction
This policy relates to the types of leaves that GitLab offers and the guidelines associated with each leave type. Training on our PTO policy is included as part of a team member’s onboarding, and is also available here for reference or if a refresher is needed.
Paid Time Off
Time away from work can be extremely helpful for maintaining a healthy work/life balance. GitLab encourages managers and leadership to set the example by taking time off when needed, and ensuring their reports do the same.
People Business Partner Team
People Compliance at GitLab
People Group Calendars
People Group Engineering
People Group Program Management
People Group Project Program
People Group READMEs
People Group Spotlight program
People Group Systems Architecture
People Group Tech Stack Guide
People Operations Team
People Success Performance Indicators
Promotion Document Style Guide
Assembling a case for promotion can be a time-consuming process. The tips and style principles in this guide will help you prepare a document that presents the evidence clearly, requiring fewer review cycles.
The emphasis on quantification over editorialization has a number of benefits for both the reader and the author:
- It’s easier to gradually assemble the document over time, and to understand the level of completion at any point.
- The document reads more confidently and, crucially, more objectively.
- Cases for promotion to the same role are more readily comparable to each other and the job family criteria, with consistent tone.
- The presentation is maximally inclusive, requiring less context on the part of the reader.
Principles for Presenting a Strong Promotion Case
- Minimize the use of adjectives and adverbs.
- Don’t:
- “significantly improved the performance of the most important Plan endpoints.”
- Do:
- “reduced Time to First Byte (TTFB) by an average of 180ms for the 5 most visited Plan endpoints.”
- Why: Adjectives and adverbs are imprecise and make it difficult for the reader to understand the true impact and the person’s exact contribution to it.
- Don’t:
- Ensure quantification is appropriate and meaningful.
- Don’t:
- “increased page views by 2 million over a 3 month period.”
- Do:
- “increased monthly page views by 25% over a 3 month period, from 8 million to 10 million.”
- Why:
- Ensures that statements pass the “so what” test, requiring no further investigation on the part of the reader.
- Don’t:
- Only use numbered links to list examples, not to describe how the person did something. Instead describe the contribution and link parts of the text.
- Don’t
- “brought a critical user feature from the architectural stage right through to General Availability (GA) [1,2,3,4,5].”
- Do
- “created an [architecture blueprint], with a [proof of concept implementation] to validate the proposed solution and aid estimation. As a result, the project was delivered on time in 3 MRs [1,2,3].”
- Why: Avoids the need for the reader to investigate each link individually and figure out for themselves what the person’s contribution actually was, often from a large issue or discussion.
- Don’t
- Focus on ability and impact at the next level.
- Don’t:
- "[name] delivered several projects on time by identifying quality implications during development, performing reviews and reaching out early when blocked." (Intermediate Engineer Competencies)
- Do:
- "[name] delivered several projects on time by proactively resolving vague requirements, collaborating cross-functionally, and mentoring other team-members in a way that enabled them to contribute." (Senior Engineer Competencies)
- Why: Space is limited and detailing contributions at the current level does not materially contribute to the case for promotion.
- Don’t:
- Business Justification should describe how the person’s role will change if promoted, and what that means for the business.
- Don’t:
- “This promotion recognizes [name]’s ability to operate at the next level in their role when required to do so.”
- Do:
- “With this promotion, [name] will assume ongoing responsibility for technical architecture, initially accelerating [project 1] as project lead and bringing forward completion of [project 2] and [project 3] by 3 months to the end of Financial Year 2026.”
- Why: Clearly defining the expected role evolution helps demonstrate the business need for the promotion and how investing in it will contribute to the organization’s goals.
- Don’t:
Additional Tips for Clarity and Impact
- Avoid unnecessary filler words or phrases:
- Arguably
- In order to
- It should be noted that
- Due to the fact that
- Expand acronyms first time they appear (“Technical Account Manager (TAM)”).
- Double-check that links point to the right resource and that it is available to your expected readership.
- Use bullet points instead of prose.
- Avoid sentences over 30 words.
- Stick to the template. If it asks for two examples, give the two best examples.
Promotions and Transfers
Pronoun Guidance and Information
Quarterly Talent Review (QTR)
Relocation
Sales Diversity Inclusion & Belonging Initiatives
Talent Assessment
Talent brand
Talent Development Program
Team Member Relations at GitLab
Using GitLab at GitLab
Intro
Everyone at GitLab uses our GitLab tool in their daily work. This page details items specific to using the GitLab tool at GitLab.
Using GitLab Competency
Skills and behavior of Using GitLab as a Team Member:
- Knows when and how to open, comment, close, and move on issues while utilizing an issue board
- Understands and knows how to open and submit a merge request
- Models how and when to use epics
- Uses GitLab effectively for day-to-day work
Skills and behaviors of Using GitLab as a People Leader:
Visas
Workday Guide
Why Workday?
- Integrated people processes that allow us to view Team Member data in one system (compensation, performance, benefits, absence management, etc.)
- Our data will be more accessible, timely, accurate, and consistent. This will allow us to improve our reporting and analytics capabilities
- Provides us with the ability to make informed organizational decisions and increase operational efficiencies based on that data
- Enhanced and standardized processes and workflows
- Increased visibility and transparency of Team Member data changes and status of those transactions
- 24/7 access from anywhere using the mobile application
- Supports streamlined access and self-service for all team members
Accessing Workday
Workday will be accessible to all GitLab team members through Okta SSO. Go to gitlab.okta.com and click on the ‘Workday SSO’ tile to login. You can search your apps for quick access.
ac0e3d5e
)