Development Analytics Group

Common Links

Mission

Our mission is to enhance developer efficiency by delivering actionable insights, optimizing pipeline performance, and building scalable productivity tools that measurably improve the software development lifecycle.

Vision

We envision a future where GitLab’s development workflows are seamless, insightful, and empowered by data. The Developer Analytics team will:

• Establish GitLab as the industry benchmark for measurable developer productivity
• Improve cycle time to industry-leading standards through tooling and practices
• Create intuitive, powerful analytics dashboards that drive informed development decisions
• Deploy AI-powered systems that optimize pipeline performance and resource utilization

Team members

Name	Role
Abhinaba Ghosh	Engineering Manager, Test Platform, Test and Tools Infrastructure
Andrejs Cunskis	Senior Software Engineer in Test, Test and Tools Infrastructure
Chloe Liu	Staff Software Engineer in Test, Test and Tools Infrastructure
Dan Davison	Staff Software Engineer in Test, Test and Tools Infrastructure
David Dieulivol	Senior Backend Engineer, Development Analytics
Ievgen Chernikov	Senior Software Engineer in Test, Test and Tools Infrastructure, Analytics section
Jennifer Li	Senior Backend Engineer, Engineering Productivity
Mark Lapierre	Senior Software Engineer in Test, Test and Tools Infrastructure

Core Responsibilities

Roadmap

As part of our commitment to aligning with GitLab’s company goals, our team conducts a thorough review of company-level Roadmap and Objectives and Key Results (OKRs) at the beginning of each quarter. This process ensures that our efforts are strategically focused on delivering high-impact results that contribute to the broader organizational objectives. View the Development Analytics Roadmap for detailed insights and upcoming priorities

Dashboards

Pipeline Duration Analytics

• Pipeline Duration Analytics
• Job Execution Analytics
• Pipeline Tier Analysis
• Long-Running Test Analysis

Pipeline Stability Analytics

• Main Branch Incident Analytics
• E2E Test Analytics

AI Latency Analytics

• AI Models and Providers Latncy Analysis
• Duo Comparative Analysis
• Duo E2E Latency Analysis

Note: Access to these dashboards requires appropriate permissions. Contact team leads for access requests.

How we work

• We prioritize asynchronous communication and a handbook-first approach, in line with GitLab’s all-remote, timezone-distributed structure.
• We emphasize the Maker’s Schedule, focusing on productive, uninterrupted work.
• Most critical recurring meetings are scheduled on Tuesdays and Thursdays.
• We dedicate 3-4 hours weekly for focused learning and innovation. This protected time enables the team to explore emerging technologies, conduct proof-of-concepts, and stay current with industry trends. Meeting requests during these blocks require advance notice.
• All meeting agendas can be found in the Team Shared Drive as well as in the meeting invite.

Work related rituals

Work management

Planning

• Each financial year, we develop a clear roadmap for the team to enhance visibility and alignment.
• Our roadmap preparation is an intensive month long exercise (usually in Q4), led by a DRI. During this phase, DRIs take the lead in drafting the roadmap using the roadmap prep-work template for necessary project tracks. This involves gathering inputs from the team, various stakeholders, assessing past performance, and aligning with the strategic goals of the Development Analytics group.
• We utilize and plan OKRs to prioritize the roadmap items.
• Adhering to our team’s work rituals, we conduct reviews to assess progress, address challenges, and recalibrate goals if necessary every two weeks.
• We maintain a Team Board to visualise the current state of the feature work.

Working with us through support requests

We estimate ~20% of weekly time for support tasks, and balancing our roadmap work with emerging support needs. Please note this estimate varies depending upon ongoing priorities.

• For individual questions please reach out to the team via our slack channels: #s_developer_experience and #g_development-analytics.
• Raise support requests as issues in the dx space. Add ~“group::Development Analytics” and ~“development-analytics::support-request” labels.
• Ensure each issue is tagged with one of ~"type::feature", ~"type::bug, ~"type::maintenance following workflow classification guidelines.
• Team members analyze the issue and add a priority. P1 issues will be taken up on an urgent basis the same week based on the availability of the relevant team members. Lower-priority issues are scheduled for review and discussion in our next team meeting.
• The issues should be following the workflow label guidelines.

View page source - Edit this page - please contribute.