Processes


Development Talent Assessment Process

Talent Assessment Process

Company-wide guidelines on the Talent Assessment can be found here. The company timeline for the process remains SSOT, the guidelines below are meant to:

  • Provide additional check points and due dates built into the company-wide timeline for Development specifically (as one of the larger departments at GitLab)
  • Guidance on department-specific calibration section structure (attendees, leveling, etc.)
  • Outline our strategy in terms of who we will be calibrating in the Development Department

Who Are We Calibrating?

Formal calibration will take place at the Senior Manager, Director, and VP levels. The thought process around who qualifies as an “outlier” for Performance and Growth Potential is outlined here.

Follow the Sun Coverage - Development Department
How the development department uses follow the sun coverage and pairing
General Information of Development Escalation Process

About This Page

This page outlines the background, goals, success criteria, and implementation detail of infrastructure escalation process and Q&A.

Background

Historically there have been challenges in consistently maintaining our service level for GitLab.com customers. See the impacts in this GitLab.com performance degradation summary document.

This issue is not unique to GitLab when business grows fast and the user base and workload on the hosted SaaS increases exponentially. As a result, the business growth requires corresponding changes in how we work so that customers continue experiencing best service by GitLab, which maintains and boosts our business growth momentum.

Hiring Contractors - Development Department
How the development department hires engineers as contractors
Rollout Plan Process for Development

About This Page

This page outlines the requirements, success criteria, and how-to’s of a rollout plan within the Development department.

What is a rollout plan and why do you need one?

A rollout plan is a description of how to get your change successfully applied to production and working as expected.

The process of creating a rollout plan is often more valuable than the plan itself because you will invest time in thinking about what needs to be done to achieve success. This may uncover implementation or observability problems that can be addressed before going live - when it is often easier to make these changes.