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:
- Foundations
- Plan
- Create
Who we are
Foundations
Foundations:Design System
Foundations:Import and Integrate
Foundations:Personal Productivity
Plan
Plan:Project Management
Name |
Role |
Donald Cook
|
Engineering Manager, Plan:Project Management |
Alexandru Croitor
|
Senior Backend Engineer, Plan:Project Management |
Agnes Slota
|
Backend Engineer |
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 |
Kushal Pandya
|
Senior Frontend 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 |
Vladimir Shushlin
|
Engineering Manager, Plan:Product Planning and Acting Engineering Manager, Plan:Knowledge |
Alisa Frunza
|
Backend Engineer |
Anastasia Khomchenko
|
Frontend Engineer, Plan:Product Planning |
Brett Walker
|
Senior Backend Engineer, Plan:Knowledge |
Eugenia Grieff
|
Senior Backend Engineer, Plan:Product Planning |
Himanshu Kapoor
|
Staff Frontend Engineer, Plan:Knowledge |
Jack Chapman
|
Frontend Engineer, Plan:Product Planning |
Janis Altherr
|
Senior Fullstack Engineer, Plan:Knowledge |
Kassio Borges
|
Staff Backend Engineer
, Plan:Product Planning
|
Matt D'Angelo
|
Backend Engineer, Plan:Product Planning |
Naman Jagdish Gala
|
Senior Backend Engineer, Plan:Knowledge |
Nicolas Dular
|
Staff Backend Engineer, Plan:Product Planning |
Backend Engineer
|
Backend Engineer |
Piotr Skorupa
|
Backend Engineer, Plan:Knowledge |
Rajan Mistry
|
Frontend Engineer, Plan:Product Planning |
Vedant Jain
|
Fullstack Engineer |
Plan:Optimize
Plan:Knowledge
Create
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 |
James Fargher
|
Senior Backend Engineer, Create:Code Creation |
Jan Provaznik
|
Staff Backend Engineer, Create:Code Creation |
Missy Davies
|
Backend Engineer, Create:Code Creation |
Omar Qunsul
|
Senior Backend Engineer, Cells Infrastructure |
Pam Artiaga
|
Senior Backend Engineer, Create:Code Creation |
Shola Quadri
|
Associate Backend Engineer |
Tian Gao
|
Backend Engineer, Create:Code Creation |
Vitali Tatarintev
|
Senior Backend Engineer, Create:Code Creation |
Wanderson Policarpo
|
Senior Backend Engineer |
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 |
Michael Angelo Rivera
|
Fullstack Engineer, Create:Editor Extensions |
Mohammed Osumah
|
Fullstack Engineer |
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
Create:Source Code
Name |
Role |
André Luís
|
Senior Engineering Manager, Create:Source Code, Create:Code Review |
Emma Park
|
Backend Engineer, Create:Source Code Backend |
Fred Reinink
|
Backend Engineer, Create:Source Code Backend |
Gavin Hinfey
|
Backend Engineer, Create:Source Code |
Jerry Seto
|
Senior Backend Engineer, Create:Source Code |
Javiera Tapia
|
Backend Engineer, Create:Source Code |
Jacques Erasmus
|
Senior Frontend Engineer, Create:Source Code |
Joe Woodward
|
Senior Backend Engineer, Create:Source Code |
Kerri Miller
|
Staff Backend Engineer, Create:Source Code Backend |
Chaoyue Zhao
|
Frontend Engineer, Create:Source Code |
Pranav Jain
|
Associate Backend Engineer, Create:Source Code |
Olaoluwa Oluro
|
Senior Backend Engineer, Create:Source Code |
Paulina Sedlak-Jakubowska
|
Senior Frontend Engineer, Create:Source Code |
Vasilii Iakliushin
|
Staff Backend Engineer, Create:Source Code, Systems:Gitaly API |
Stable Counterparts
The following members of other functional teams are our stable counterparts:
Name |
Role |
Andrejs Cunskis
|
Senior Software Engineer in Test, Development Analytics |
Chloe Liu
|
Staff Software Engineer in Test, Development Analytics |
Dan Davison
|
Staff Software Engineer in Test, Development Analytics |
David Dieulivol
|
Senior Backend Engineer, Development Analytics |
Emilio Salvador
|
VP, Dev Relations and Community |
Abhinaba Ghosh
|
Engineering Manager, Test Platform, Development Analytics |
Ievgen Chernikov
|
Senior Software Engineer in Test, Development Analytics |
Jay McCure
|
Senior Software Engineer in Test, Dev:Create |
John Coghlan
|
Director, Developer Advocacy |
Kalyani Yerraguntla
|
Learning & Development Program Manager |
Lauren Cairns
|
Senior Learning & Development Program Manager |
MQ Gillespie
|
Senior Learning & Development Program Manager |
Nivetha Prabakaran
|
Software Engineer in Test, Dev:Manage |
Pranshu Sharma
|
Intermediate Backend Engineer, Development Analytics |
Richard Chong
|
Senior Software Engineer in Test, Developer Experience:Feature Readiness |
Lohit Peesapati
|
Intermediate Backend Engineer, Development Analytics |
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
The Create Stage is a group of teams including Code Creation, Code Review, Editor Extensions, Remote Development, and Source Code.
The Foundations stage deals with cross functional work from the design system, to importers, to the navigation.
Plan teams:
Plan:Project Management Team Plan:Product Planning Team Plan:Optimize Team …