Dev Sub-department
Vision
Enable engineers across the world by having top notch planning and issue tools for managing their work, awesome tools to organize their code and evolve their codebase through the best code review and online editing experience. Support organizations to have an easy entrance level to use GitLab by having great import capabilities, a great documentation experience and administration tools.
We thrive for ownership of the things that we built by having a clear view on its performance and stability in production. We constantly challenge ourselves to build a better, faster and more robust application.
Mission
The Dev sub-department is taking care of the first part of the DevSecOps Lifecycle with the following stages and the specific groups:
Who we are
Foundations
Foundations:Design System
Name | Role |
---|---|
![]() |
Engineering Manager, Foundations:Design System, Foundations:Personal Productivity |
![]() |
Frontend Engineer, Foundations:Design System |
![]() |
Staff Frontend Engineer, Foundations:Design System |
![]() |
Senior Frontend Engineer, Foundations:Design System |
![]() |
Senior Frontend Engineer, Foundations:Design System |
Foundations:Import and Integrate
Name | Role |
---|---|
![]() |
Engineering Manager, Manage:Import and Integrate |
![]() |
Senior Backend Engineer, Manage:Import and Integrate |
![]() |
Senior Backend Engineer, Manage:Import and Integrate |
![]() |
Backend Engineer |
![]() |
Senior Backend Engineer, Manage:Import and Integrate |
![]() |
Senior Frontend Engineer, Manage:Import and Integrate |
![]() |
Backend Engineer, Manage:Import and Integrate |
![]() |
Staff Backend Engineer, Manage:Import and Integrate |
![]() |
Frontend Engineer, Manage:Import and Integrate |
![]() |
Backend Engineer, Manage:Import and Integrate |
![]() |
Staff Backend Engineer, Manage:Import and Integrate |
![]() |
Senior Backend Engineer, Manage:Import and Integrate |
Foundations:Personal Productivity
Name | Role |
---|---|
![]() |
Engineering Manager, Foundations:Design System, Foundations:Personal Productivity |
![]() |
Staff Frontend Engineer, Foundations:Personal Productivity |
![]() |
Senior Frontend Engineer, Foundations:Personal Productivity |
![]() |
Senior Fullstack Engineer, Foundations:Personal Productivity |
Plan
Plan:Project Management
Name | Role |
---|---|
![]() |
Engineering Manager, Plan:Project Management |
![]() |
Senior Backend Engineer, Plan:Project Management |
![]() |
Backend Engineer |
![]() |
Senior Frontend Engineer, Plan:Project Management |
![]() |
Senior Frontend Engineer, Plan:Project Management |
![]() |
Frontend Engineer, Plan:Project Management |
![]() |
Staff Backend Engineer, Plan:Project Management |
![]() |
Senior Backend Engineer, Plan:Project Management |
![]() |
Senior Fullstack Engineer, Plan:Project Management |
![]() |
Staff Frontend Engineer, Plan:Project Management |
![]() |
Backend Engineer |
Plan:Product Planning
Name | Role |
---|---|
![]() |
Fullstack Engineering Manager, Plan:Product Planning |
![]() |
Frontend Engineer, Plan:Product Planning |
![]() |
Senior Backend Engineer, Plan:Product Planning |
![]() |
Senior Frontend Engineer, Plan:Product Planning |
![]() |
Frontend Engineer, Plan:Product Planning |
![]() |
Staff Backend Engineer , Plan:Product Planning |
![]() |
Backend Engineer, Plan:Product Planning |
![]() |
Staff Backend Engineer, Plan:Product Planning |
![]() |
Backend Engineer |
![]() |
Frontend Engineer, Plan:Product Planning |
Plan:Optimize
Name | Role |
---|---|
![]() |
Fullstack Engineering Manager, Plan:Optimize |
![]() |
Backend Engineer, Plan:Optimize |
![]() |
Senior Frontend Engineer, Plan:Optimize |
![]() |
Senior Frontend Engineer, Plan:Optimize |
![]() |
Senior Backend Engineer, Plan:Optimize |
![]() |
Staff Backend Engineer, Plan:Optimize |
![]() |
Frontend Engineer, Plan:Optimize |
Plan:Knowledge
Name | Role |
---|---|
![]() |
Senior Manager, Engineering, Plan |
![]() |
Engineering Manager, Plan:Knowledge |
Create
Create:Code Review
Name | Role |
---|---|
![]() |
Senior Engineering Manager, Create:Source Code, Create:Code Review |
![]() |
Engineering Manager, Create:Code Review |
![]() |
Staff Fullstack Engineer, Create:Code Review |
![]() |
Senior Frontend Engineer, Create:Code Review |
![]() |
Senior Frontend Engineer, Create:Code Review |
Create:Code Creation
Name | Role |
---|---|
![]() |
Backend Engineering Manager, Create:Code Creation |
![]() |
Senior Backend Engineer, Create:Code Creation |
![]() |
Backend Engineer, Create:Code Creation |
![]() |
Staff Backend Engineer, Create:Code Creation |
![]() |
Senior Backend Engineer, Create:Code Creation |
![]() |
Backend Engineer, Create:Code Creation |
![]() |
Senior Backend Engineer, Create:Code Creation |
![]() |
Associate Backend Engineer |
![]() |
Backend Engineer, Create:Code Creation |
![]() |
Senior Backend Engineer, Create:Code Creation |
Create:Editor Extensions
Name | Role |
---|---|
![]() |
Engineering Manager |
![]() |
Senior Frontend Engineer, Create:Editor Extensions |
![]() |
Senior Backend Engineer, Create:Code Creation |
![]() |
Backend Engineer, Create:Editor Extensions |
![]() |
Associate Backend Engineer, Create:Editor Extensions |
![]() |
Senior Frontend Engineer, Create:Editor Extensions |
![]() |
Staff Fullstack Engineer, Create:Editor Extensions |
![]() |
Backend Engineer |
![]() |
Staff Backend Engineer, Create:Editor Extensions |
![]() |
Fullstack Engineer |
![]() |
Backend Engineer |
![]() |
Senior Backend Engineer |
![]() |
Fullstack Engineer, Create:Editor Extensions |
![]() |
Senior Frontend Engineer, Create:Editor Extensions |
![]() |
Staff Fullstack Engineer, Create:Editor Extensions |
![]() |
Senior Frontend Engineer, Create:Editor Extensions |
Create:Remote Development
Name | Role |
---|---|
![]() |
Engineering Manager |
![]() |
Backend Engineer |
![]() |
Staff Backend Engineer, Create:Remote Development |
![]() |
Fullstack Engineer, Create:Remote Development |
![]() |
Backend Engineer |
![]() |
Staff Frontend Engineer, Create:Remote Development |
![]() |
Associate Frontend Engineer |
![]() |
Staff Fullstack Engineer, Create:Remote Development |
![]() |
Backend Engineer, Create:Remote Development |
![]() |
Staff Backend Engineer, Create:Remote Development |
![]() |
Backend Engineer, Create:Remote Development |
Create:Source Code
Name | Role |
---|---|
![]() |
Senior Engineering Manager, Create:Source Code, Create:Code Review |
![]() |
Engineering Manager, Create:Source Code Backend |
![]() |
Senior Frontend Engineer, Create:Source Code |
![]() |
Frontend Engineer, Create:Source Code |
![]() |
Senior Frontend Engineer, Create:Source Code |
Stable Counterparts
The following members of other functional teams are our stable counterparts:
How we work
Error Budgets
Error budgets are one of the Dev sub-department/section’s performance indicators. They’re vital in determining how reliable services within Dev are over any given timeframe. The budget is spent any time user-facing services experience a percentage of errors or latency breaching their defined thresholds. We track our error budgets using Grafana dashboards.
Engineering Managers in Dev focus on the 7-day timeframe of their error budget. An example dashboard can be found here.
Reporting your groups error budget, reliability, and security status
Every week, engineering leaders meet to discuss topics including the error budgets across the entire Engineering Division.
Dev engineering leaders use this Google document to track our error budget status week-over-week, which are then reported on in these meetings by senior leadership.
Engineering Managers are advised to report up to their managers, or self-report the status of their group on Monday’s using the above document to ensure we have an accurate weekly snapshot of the sub-department’s error budget status, outstanding reliability issue status, and past due security issues.
Automating a weekly check-in on your error budget
One way that groups can keep error budgets in mind is by automating a weekly reminder in Slack to check on their error budget.
A Slack workflow can be created that allows any member of the team to provide a quick update on the current error budget status.
Common Links
- Issue Tracker
- Slack Channels
- #sd_dev_engineering
- #s_manage
- #s_plan
- #s_create
Foundations Stage
Plan Stage
Plan teams:
The responsibilities of this collective team are described by the Plan stage. Among other things, this means working on GitLab’s functionality around issues, boards, milestones, to-do list, issue lists and filtering, roadmaps, time tracking, requirements management, notifications, value stream analytics (VSA), wiki, and pages.
- I have a question. Who do I ask?
In GitLab issues, questions should start by @ mentioning the Product Manager for the corresponding Plan stage group. GitLab team-members can also use #s_plan.
fd7f35e9
)