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 |
---|---|
Sam Beckham | Engineering Manager, Foundations:Design System, Foundations:Personal Productivity |
James Rushford | Frontend Engineer, Foundations:Design System |
Staff Frontend Engineer | Staff Frontend Engineer, Foundations:Design System |
Scott de Jonge | Senior Frontend Engineer, Foundations:Design System |
Vanessa Otto | Senior Frontend Engineer, Foundations:Design System |
Foundations:Import and Integrate
Name | Role |
---|---|
Martin Wortschack | Engineering Manager, Manage:Import and Integrate |
Carla Drago | Senior Backend Engineer, Manage:Import and Integrate |
Senior Backend Engineer | Senior Backend Engineer, Manage:Import and Integrate |
James Nutt | Senior Backend Engineer, Manage:Import and Integrate |
Justin Ho | Senior Frontend Engineer, Manage:Import and Integrate |
Keeyan Nejad | Backend Engineer, Manage:Import and Integrate |
Luke Duncalfe | Staff Backend Engineer, Manage:Import and Integrate |
Oiza Baiye | Frontend Engineer, Manage:Import and Integrate |
Rodrigo Tomonari | Senior Backend Engineer, Manage:Import and Integrate |
Sam Word | Senior Backend Engineer, Manage:Import and Integrate |
Foundations:Personal Productivity
Name | Role |
---|---|
Sam Beckham | Engineering Manager, Foundations:Design System, Foundations:Personal Productivity |
Lukas Eipert | Staff Frontend Engineer, Foundations:Personal Productivity |
Paul Gascou-Vaillancourt | Senior Frontend Engineer, Foundations:Personal Productivity |
Thomas Hutterer | Senior Fullstack Engineer, Foundations:Personal Productivity |
Plan
Plan:Project Management
Name | Role |
---|---|
Donald Cook | Engineering Manager, Plan:Project Management |
Alexandru Croitor | Senior Backend Engineer, Plan:Project Management |
Senior Frontend Engineer | Senior Frontend Engineer, Plan:Project Management |
Deepika Guliani | Senior Frontend Engineer, Plan:Project Management |
Fernanda Toledo | Frontend Engineer, Plan:Project Management |
Heinrich Lee Yu | Staff Backend Engineer, Plan:Project Management |
Mario Celi | Senior Backend Engineer, Plan:Project Management |
Marc Saleiko | Senior Fullstack Engineer, Plan:Project Management |
Simon Knox | Staff Frontend Engineer, Plan:Project Management |
Stefanos Xanthopoulos | Backend Engineer |
Plan:Product Planning
Name | Role |
---|---|
Kushal Pandya | Fullstack Engineering Manager, Plan:Product Planning |
Anastasia Khomchenko | Frontend Engineer, Plan:Product Planning |
Abhilash Kotte | Senior Fullstack Engineer, Plan:Product Planning |
Eugenia Grieff | Senior Backend Engineer, Plan:Product Planning |
Florie Guibert | Senior Frontend Engineer, Plan:Product Planning |
Jack Chapman | Frontend Engineer, Plan:Product Planning |
Kassio Borges | Staff Backend Engineer , Plan:Product Planning |
Nicolas Dular | Staff Backend Engineer, Plan:Product Planning |
Backend Engineer | Backend Engineer |
Rajan Mistry | Frontend Engineer, Plan:Product Planning |
Plan:Optimize
Name | Role |
---|---|
Brandon Labuschagne | Fullstack Engineering Manager, Plan:Optimize |
Alex Pennells | Senior Frontend Engineer, Plan:Optimize |
Ezekiel Kigbo | Senior Frontend Engineer, Plan:Optimize |
Felipe Artur | Senior Backend Engineer, Plan:Optimize |
Pavel Shutsin | Staff Backend Engineer, Plan:Optimize |
Rudy Crespo | Frontend Engineer, Plan:Optimize |
Plan:Knowledge
Name | Role |
---|---|
John Hope | Senior Manager, Engineering, Plan |
Vladimir Shushlin | Engineering Manager, Plan:Knowledge |
Create
Create:Code Review
Name | Role |
---|---|
André Luís | Senior Engineering Manager, Create:Source Code, Create:Code Review |
François Rosé | Engineering Manager, Create:Code Review |
Phil Hughes | Staff Fullstack Engineer, Create:Code Review |
Stanislav Lashmanov | Senior Frontend Engineer, Create:Code Review |
Thomas Randolph | Senior Frontend Engineer, Create:Code Review |
Create:Code Creation
Name | Role |
---|---|
Matt Nohr | Backend Engineering Manager, Create:Code Creation |
Allen Cook | Senior Backend Engineer, Create:Code Creation |
Backend Engineer | Backend Engineer, Create:Code Creation |
Jan Provaznik | Staff Backend Engineer, Create:Code Creation |
Leaminn Ma | Senior Backend Engineer, Create:Code Creation |
Mikołaj Wawrzyniak | Staff Backend Engineer, Create:Code Creation |
Missy Davies | Backend Engineer, Create:Code Creation |
Pam Artiaga | Senior Backend Engineer, Create:Code Creation |
Shola Quadri | Associate Backend Engineer |
Sri Rangan | Staff Fullstack Engineer, Create:Code Creation |
Tian Gao | Backend Engineer, Create:Code Creation |
Vitali Tatarintev | Senior Backend Engineer, Create:Code Creation |
Create:Editor Extensions
Name | Role |
---|---|
Kisha Mavryck Richardson | Engineering Manager |
Andrei Zubov | Senior Frontend Engineer, Create:Editor Extensions |
Anna Springfield | Senior Backend Engineer, Create:Code Creation |
Bohdan Parkhomchuk | Backend Engineer, Create:Editor Extensions |
Dylan Bernardi | Associate Backend Engineer, Create:Editor Extensions |
Elwyn Benson | Senior Frontend Engineer, Create:Editor Extensions |
Erran Carey | Staff Fullstack Engineer, Create:Editor Extensions |
Jean-Gabriel Doyon | Backend Engineer |
John Slaughter | Staff Backend Engineer, Create:Editor Extensions |
Juhee Lee | Fullstack Engineer |
Karl Jamoralin | Backend Engineer |
Laura Ionel | Senior Backend Engineer |
Marvin Gay | Backend Engineer, Create:Editor Extensions |
Michael Angelo Rivera | Fullstack Engineer, Create:Editor Extensions |
Olena HK. | Senior Frontend Engineer, Create:Editor Extensions |
Tomas Vik | Staff Fullstack Engineer, Create:Editor Extensions |
Tristan Read | Senior Frontend Engineer, Create:Editor Extensions |
Create:Remote Development
Name | Role |
---|---|
Adebayo Adesanya | Engineering Manager |
Chad Woolley | Staff Backend Engineer, Create:Remote Development |
Cindy Halim | Fullstack Engineer, Create:Remote Development |
Daniyal Arshad | Backend Engineer |
Enrique Alcántara | Staff Frontend Engineer, Create:Remote Development |
Joseph Fletcher | Associate Frontend Engineer |
Paul Slaughter | Staff Fullstack Engineer, Create:Remote Development |
Safwan Ahmed | Backend Engineer, Create:Remote Development |
Vishal Tak | Staff Backend Engineer, Create:Remote Development |
Zhaochen Li | Backend Engineer, Create:Remote Development |
Create:Source Code
Name | Role |
---|---|
André Luís | Senior Engineering Manager, Create:Source Code, Create:Code Review |
Devi Poosarla | Engineering Manager, Create:Source Code Backend |
Jacques Erasmus | Senior Frontend Engineer, Create:Source Code |
Chaoyue Zhao | Frontend Engineer, Create:Source Code |
Paulina Sedlak-Jakubowska | 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.
81d291b5
)