Developer Tooling team

The Developer Tooling team enables all GitLab contributors to efficiently deliver results for customers by providing stable and performant software development tools, such as the GitLab Development Kit.

Mission

  • Build state-of-the-art developer tools that are efficient and reliable, empowering developers to keep their development environments up-to-date painlessly.
  • Enable contributors to contribute to our tools.
  • Measure what matters: improvements in developer experience, efficiency, and toil reduction, using both quantitative and qualitative metrics.

Vision

The Developer Tooling team’s vision is to create tools that enable GitLab team members and the wider community to contribute to GitLab efficiently, without the friction and manual toil that often come with working on large, complex software projects like GitLab.

Areas of responsibilities

focuses on

Developer Tooling

GitLab Development Kit

GDK remote development workspace

gitlab-org/gitlab tooling

Static Analysis

Auxiliary tooling
Useful tools for GitLab.com.

Pipeline Visualizer

Subparticle

Team structure

Members

Team Members Role
Mohga Gamea Engineering Manager
Doug BarrettDoug Barrett Backend Engineer, Developer Tooling
Nao HashizumeNao Hashizume Backend Engineer, Developer Tooling
Kev KlossKev Kloss Frontend Engineer, Developer Tooling
Peter LeitzenPeter Leitzen Staff Backend Engineer, Developer Tooling

Stable counterpart

Person Role
Greg AlfaroGreg Alfaro GDK Project Stable Counterpart, Application Security

OKRs

Objectives and Key Results (OKRs) help align our sub-department towards what really matters. These happen quarterly and are based on company OKRs. We follow the OKR process defined here.

Here is an overview of our current OKRs.

Communication

Description Link
GitLab Team Handle @gl-dx/developer-tooling
Slack Channel #g_developer_tooling
Team Boards Team Board
Issue Tracker gitlab-org/dx/tooling/team