Developer Experience
Mission
Our mission is to empower developers to focus on innovation, build, and deliver high-quality products to our customers. We aim to achieve this through:
- State-of-the-art developer tooling.
- Robust and reliable test infrastructure.
- Data-driven analysis for informed decision-making.
- Streamlined release and test governance to ensure consistency, compliance, and quality across the development lifecycle.
- Continuous performance profiling.
Team Structure
Infrastructure Platforms Department structure is documented in our handbook.
OKRs
TODO
Weights
We use Fibonacci Series for weights and limit the highest number to 8. The definitions are as below:
Weight | Description |
---|---|
1 - Trivial | Simple and quick changes such as typo fixes, test tag updates, or trivial documentation additions |
2 - Small | Straight forward changes with no underlying dependencies needed, such as new tests that use existing factories or page objects |
3 - Medium | Well understood changes with a few dependencies. Few surprises can be expected, such as new tests that require new factories or page objects/components |
5 - Large | A task that will require some investigation and research, in addition to the above weights, such as tests that need framework level changes which can impact other parts of the test suite |
8 - X-large | A very large task that will require much investigation and research. Pushing initiative level |
13 or more | Please break the work down further, we do not use weights higher than 8. |
Developer Experience group structure
Team Members
Management team
Name | Role |
---|
Individual contributors
The following people are members of the Development Analytics group:
Name | Role |
---|---|
![]() |
Engineering Manager, Test Platform, Development Analytics |
![]() |
Senior Software Engineer in Test, Development Analytics |
![]() |
Staff Software Engineer in Test, Development Analytics |
![]() |
Senior Backend Engineer, Development Analytics |
![]() |
Senior Software Engineer in Test, Development Analytics |
![]() |
Intermediate Backend Engineer, Development Analytics |
![]() |
Intermediate Backend Engineer, Development Analytics |
The following people are members of the Developer Tooling group:
The following people are members of the Feature Readiness group:
Name | Role |
---|---|
![]() |
Manager, Quality Engineering, Core Platform & SaaS Platform |
![]() |
Senior Software Engineer in Test, SaaS Platforms:US Public Sector Services |
![]() |
Senior Software Engineer in Test, Dedicated:Environment Automation |
![]() |
Software Engineer in Test, SaaS Platforms:US Public Sector Services |
![]() |
Senior Software Engineer in Test, Systems:Gitaly |
![]() |
Software Engineer in Test, Dev:Manage |
![]() |
Senior Software Engineer in Test, Developer Experience:Feature Readiness |
![]() |
Staff Software Engineer in Test, Test and Tools Infrastructure |
![]() |
Senior Software Engineer in Test, Test and Tools Infrastructure |
![]() |
Software Engineer in Test, Core Platform:Systems |
The following people are members of the Performance Enablement group:
Name | Role |
---|---|
![]() |
Manager, Quality Engineering, Core Platform & SaaS Platform |
![]() |
Senior Software Engineer in Test, SaaS Platforms:US Public Sector Services |
![]() |
Senior Software Engineer in Test, Dedicated:Environment Automation |
![]() |
Software Engineer in Test, SaaS Platforms:US Public Sector Services |
![]() |
Senior Software Engineer in Test, Systems:Gitaly |
![]() |
Software Engineer in Test, Dev:Manage |
![]() |
Senior Software Engineer in Test, Developer Experience:Feature Readiness |
![]() |
Staff Software Engineer in Test, Test and Tools Infrastructure |
![]() |
Senior Software Engineer in Test, Test and Tools Infrastructure |
![]() |
Software Engineer in Test, Core Platform:Systems |
The following people are members of the Test Governance group:
Name | Role |
---|---|
![]() |
Engineering Manager, Test Platform, Test Engineering |
Debugging Failing Tests and Test Pipelines
Developer Experience Dashboards
Developer Experience Design Documents
A design document describes a technical vision and a set of principles that will guide various Developer Experience tool implementation, as we move forward. It acts as guardrails to keep team aligned.
They are version controlled documents that are constantly updated with new insights and knowledge, after every iteration, to become even more useful with time.
Contributing
At GitLab, everyone can contribute, including to our design documents. If you would like to contribute to any of these documents, feel free to:
Developer Experience On-call Rotation
Developer Experience Onboarding
Developer Experience Project Management
Developer Tooling team
Development Analytics Group
End-to-end Pipeline Monitoring
Engineering Analytics Team
Feature Readiness
Performance Enablement
Pipeline Triage
Quality Engineering Learning Resources
Risk Mapping
Test Coverage
Test Governance Group
Test Governance Tips and Tricks
Test Platform Roadmap
d818a13d
)