はてなブックマーク

SAFE Why SAFE? GitLab has accomplished a number of milestones and Transparency has been essential to our success from the beginning. As GitLab has matured, we have evolved to viewing Transparency as both Internal Transparency and External Transparency; accordingly we want to continue to equip team members with the tools to enable responsible transparency in order to protect GitLab and our team mem

Intro to making decisions On this page, we have outlined how we make decisions at GitLab. Making decisions GitLab’s values are the guiding principles for our business. They inform hiring, performance management, and promotion assessments. They also guide other decisions that we make. At times, values may be in conflict. To address this, GitLab has a values hierarchy. At the top of this hierarchy i

Ad-hoc Data Development Ad-hoc delivers a report or dashboard for one-time or limited use and it can also deliver a prototype, first iteration of a data solution that is not mature enough for a long-term, Trusted Data Solution yet. Ad-hoc development is performed when no existing data solution answers the questions being asked. Code developed for ad-hoc analysis for one-time or limited use is not

On this page, we’re addressing a popular question: “How do you interview remotely?” We’re also curating a list of questions that we at GitLab appreciate hearing answers to from others in remote organizations. How do you interview remotely? Whether you’re wanting to learn how to hire remotely, or just wanting to know how to get hired for a remote position, it helps to know how you should prepare fo

Enterprise Data Warehouse Overview The Enterprise Data Warehouse (EDW) is used for reporting and analysis. It is a central repository of current and historical data from GitLab’s Enterprise Applications. We use an ELT method to Extract, Load, and Transform data in the EDW. We use Snowflake as our EDW and use dbt to transform data in the EDW. The Data Catalog contains Analytics Hubs, Data Guides, D

GitLab has at most eight layers in the company structure (Associate/Intermediate/Senior, Manager, Senior Manager, Director, Senior Director and/or VP, Executives, CEO). You can skip layers but you generally never have someone reporting to the same layer (Example of a VP reporting to a VP). Dual Career Path at GitLab A dual career path is a career path that allows upward mobility for team members w

Onboarding is incredibly important at GitLab. We don’t expect you to hit the ground running from day one. We highly recommend taking at least two full weeks for onboarding and only in week three starting with team specific onboarding and training. Please feel free to participate in your team’s work in your first two weeks, but don’t feel like you have to contribute heavily. All onboarding steps ar

Roles vs personas Personas describe the ideal target for GitLab. They help us define our messaging and marketing delivery. They are theoretical people to target. By defining their concerns and where they go for information, we can best spend our marketing dollars and sales efforts by focusing on this ideal target. Roles are distinct job titles. These are the real people you will encounter while se

A list of tools and applications used internally at GitLab and how to access them. This is a listing of the applications we use at GitLab. If you’re looking for the technology used to deliver GitLab.com, please visit the Production Architecture page. Tech stack related processes Update tech stack information Please visit our Tech Stack main page for instructions on how to request updates to the Te

A handbook-first approach to communication is sneakily vital to a well-run business. While it feels skippable — inefficient, even — the outsized benefits of intentionally writing down and organizing process, culture, and solutions are staggering. Conversely, avoiding structured documentation is the best way to instill a low-level sense of chaos and confusion that hampers growth across the board. G

On this page, we’re detailing how informal communication occurs at GitLab, how it complements in-person interactions, and why it matters in an all-remote culture. There are over 20 different ways to foster informal communication below, and we are constantly discovering and adding new methods. What do we mean by informal communication? Informal communication in the workplace is made up of interacti

Flow structure A (process) problem comes up, frequently in an issue or chat. A proposal is made in a merge request to the handbook. Once merged, the change is announced by linking to the diff in the MR or commit. Major ones are posted in the #whats-happening-at-gitlab slack channel. Medium ones are posted in the #handbook channel for visibility, with a one line summary of the change. If there was

A set of conventions and guidelines for writing SQL at GitLab SQL Style Guide This guide establishes our standards for SQL and are enforced by the SQLFluff linter and by code review. The target code changes that this stile guide apply to are those made using dbt. If you are not on the Data Team or you are developing SQL outside of dbt, keep in mind that the linting tools may be more difficult to a

Instructions for how to access the GitLab tech stack and request updates to it Definition and Access Note: Use the Tech Stack Index to browse Tech Stack Apps. The Tech Stack is a list of all the technology that GitLab currently uses to support the business. The Tech Stack lists systems/applications/tools/data used by all departments and details the business purpose/description, the owners, the pro

Security Vision and Mission Our vision is to transparently lead the world to secure outcomes. Our mission is to enable everyone to innovate and succeed on a safe, secure, and trusted DevSecOps platform. This will be achieved through 5 security operating principles: Accelerate business success with a focus on: Prioritize ‘boring’, iterative solutions that minimize risk Find ways to say Yes Understa

The compensation calculator is available to all our team members through this url. For a full list of open positions, please see our jobs page.

The GitLab Enterprise Data Team is responsible for empowering every GitLab team member to contribute to the data program and generate business value from our data assets. Welcome to the Data Team Handbook Our Vision is to Contribute to GitLab’s journey of becoming the leading AllOps platform by responsibly harnessing the power of data. In pursuit of our vision, we will focus on 4 outcomes: Drive c

We’re an all-remote company that allows people to work from almost anywhere in the world. It’s important for us to practice clear communication in ways that help us stay connected and work more efficiently. We’re an all-remote company that allows people to work from almost anywhere in the world. We hire great people regardless of where they live, but with GitLab team members across more than 60 co

OKRs stands for Objective-Key Results and are our quarterly objectives. OKRs are how to achieve the goal of the Key Performance Indicators KPIs. Most recent OKRs Our OKR process and timelines are public and listed on the pages below. FY25-Q1 Active FY25-Q2 Future Previous OKRs OKRs are internal-only in line with guidance from the SAFE framework. What are OKRs? OKRs stand for Objectives and Key Res

Find answers to your questions about GitLab’s compensation framework. Related Compensation Pages Compensation Calculator Formula Compensation Review Cycle Use the Compensation Calculator Team members can access the calculator at any time with their GitLab credentials. Applicants will be given credentials and will be able access the calculator themselves as well, during the application process. Int