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.
The Dev sub-department is taking care of the first part of the DevSecOps Lifecycle with the following stages and the specific groups:
| Person | Role |
|---|
| Person | Role |
|---|
| Person | Role |
|---|---|
| Martin Wortschack | Engineering Manager, Manage:Import |
| Carla Drago | Senior Backend Engineer, Manage:Import |
| George Koltsov | Senior Backend Engineer, Manage:Import |
| Illya Klymov | Senior Frontend Engineer, Manage:Import |
| Rodrigo Tomonari | Senior Backend Engineer, Manage:Import |
| Person | Role |
|---|
| Person | Role |
|---|
| Person | Role |
|---|---|
| Donald Cook | Engineering Manager, Plan:Project Management |
| Alexandru Croitor | Senior Backend Engineer, Plan:Project Management |
| Brett Walker | Senior Backend Engineer, Plan:Project Management |
| Coung Ngo | Senior Frontend Engineer, Plan:Project Management |
| Deepika Guliani | Frontend Engineer, Plan:Project Management |
| Eulyeon K. | Backend Engineer, Plan:Project Management |
| Heinrich Lee Yu | Staff Backend Engineer, Plan:Project Management |
| Mario Celi | Backend Engineer, Plan:Project Management |
| Natalia Tepluhina | Staff Frontend Engineer, Plan:Project Management |
| Simon Knox | Senior Frontend Engineer, Plan:Project Management |
| Person | Role |
|---|
| Person | Role |
|---|---|
| Sean Carroll | Backend Engineering Manager, Create:Source Code |
| Gavin Hinfey | Backend Engineer |
| Igor Drozdov | Senior Backend Engineer, Create:Source Code |
| Jerry Seto | Senior Backend Engineer |
| Joe Woodward | Senior Backend Engineer, Create:Source Code |
| Robert May | Senior Backend Engineer, Create:Source Code |
| Vasilii Iakliushin | Senior Backend Engineer, Create:Source Code |
| Person | Role |
|---|---|
| Matt Nohr | Backend Engineering Manager, Create:Code Review |
| Sincheol (David) Kim | Senior Backend Engineer, Create:Code Review |
| Gary Holtz | Backend Engineer, Create:Code Review |
| Kerri Miller | Staff Backend Engineer, Create:Code Review |
| Marc Shaw | Senior Backend Engineer, Create:Code Review |
| Patrick Bajao | Senior Backend Engineer, Create:Code Review |
| Person | Role |
|---|---|
| David O'Regan | Engineering Manager, Create:Editor |
| Chad Woolley | Senior Backend Engineer, Create:Editor |
| Denys Mishunov | Staff Frontend Engineer, Create:Editor |
| Enrique Alcántara | Senior Frontend Engineer, Create:Editor |
| Guillermo De los Santos García | Senior Backend Engineer, Create:Editor |
| Himanshu Kapoor | Senior Frontend Engineer, Create:Editor |
| Kassio Borges | Senior Backend Engineer, Create:Editor |
| Paul Slaughter | Staff Frontend Engineer, Create:Editor |
| Tomas Vik | Senior Fullstack Engineer, Create:Editor |
| Vishal Tak | Senior Backend Engineer, Create:Editor |
| Person | Role |
|---|---|
| André Luís | Frontend Engineering Manager, Create:Source Code, Create:Code Review, Delivery & Scalability |
| Jacques Erasmus | Senior Frontend Engineer, Create:Source Code |
| Nataliia Radina | Frontend Engineer, Create:Source Code |
| Person | Role |
|---|---|
| André Luís | Frontend Engineering Manager, Create:Source Code, Create:Code Review, Delivery & Scalability |
| Phil Hughes | Staff Frontend Engineer, Create:Code Review |
| Stanislav Lashmanov | Senior Frontend Engineer, Create:Code Review |
| Thomas Randolph | Senior Frontend Engineer, Create:Code Review |
| Person | Role |
|---|---|
| Tim Zallmann | Senior Director of Engineering, Dev |
| Person | Role |
|---|
| Person | Role |
|---|
The following members of other functional teams are our stable counterparts:
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.
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.
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.
(Sisense↗) We also track our backlog of issues, including past due security and infradev issues, and total open SUS-impacting issues and bugs.
(Sisense↗) MR Type labels help us report what we're working on to industry analysts in a way that's consistent across the engineering department. The dashboard below shows the trend of MR Types over time and a list of merged MRs.
