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:

  1. Foundations
  2. Plan
  3. Create

Who we are

Foundations

Foundations:Design System

Name Role
Sam BeckhamSam Beckham Engineering Manager, Foundations:Design System, Foundations:Personal Productivity
James RushfordJames Rushford Frontend Engineer, Foundations:Design System
Staff Frontend EngineerStaff Frontend Engineer Staff Frontend Engineer, Foundations:Design System
Scott de JongeScott de Jonge Senior Frontend Engineer, Foundations:Design System
Vanessa OttoVanessa Otto Senior Frontend Engineer, Foundations:Design System

Foundations:Import and Integrate

Name Role
Martin WortschackMartin Wortschack Engineering Manager, Manage:Import and Integrate
Carla DragoCarla Drago Senior Backend Engineer, Manage:Import and Integrate
Senior Backend EngineerSenior Backend Engineer Senior Backend Engineer, Manage:Import and Integrate
James NuttJames Nutt Senior Backend Engineer, Manage:Import and Integrate
Justin HoJustin Ho Senior Frontend Engineer, Manage:Import and Integrate
Keeyan NejadKeeyan Nejad Backend Engineer, Manage:Import and Integrate
Luke DuncalfeLuke Duncalfe Staff Backend Engineer, Manage:Import and Integrate
Oiza BaiyeOiza Baiye Frontend Engineer, Manage:Import and Integrate
Rodrigo TomonariRodrigo Tomonari Senior Backend Engineer, Manage:Import and Integrate
Sam WordSam Word Senior Backend Engineer, Manage:Import and Integrate

Foundations:Personal Productivity

Name Role
Sam BeckhamSam Beckham Engineering Manager, Foundations:Design System, Foundations:Personal Productivity
Lukas EipertLukas Eipert Staff Frontend Engineer, Foundations:Personal Productivity
Paul Gascou-VaillancourtPaul Gascou-Vaillancourt Senior Frontend Engineer, Foundations:Personal Productivity
Thomas HuttererThomas Hutterer Senior Fullstack Engineer, Foundations:Personal Productivity

Plan

Plan:Project Management

Name Role
Donald CookDonald Cook Engineering Manager, Plan:Project Management
Alexandru CroitorAlexandru Croitor Senior Backend Engineer, Plan:Project Management
Senior Frontend EngineerSenior Frontend Engineer Senior Frontend Engineer, Plan:Project Management
Deepika GulianiDeepika Guliani Senior Frontend Engineer, Plan:Project Management
Fernanda ToledoFernanda Toledo Frontend Engineer, Plan:Project Management
Heinrich Lee YuHeinrich Lee Yu Staff Backend Engineer, Plan:Project Management
Mario CeliMario Celi Senior Backend Engineer, Plan:Project Management
Marc SaleikoMarc Saleiko Senior Fullstack Engineer, Plan:Project Management
Simon KnoxSimon Knox Staff Frontend Engineer, Plan:Project Management
Stefanos XanthopoulosStefanos Xanthopoulos Backend Engineer

Plan:Product Planning

Name Role
Kushal PandyaKushal Pandya Fullstack Engineering Manager, Plan:Product Planning
Anastasia KhomchenkoAnastasia Khomchenko Frontend Engineer, Plan:Product Planning
Abhilash  KotteAbhilash Kotte Senior Fullstack Engineer, Plan:Product Planning
Eugenia GrieffEugenia Grieff Senior Backend Engineer, Plan:Product Planning
Florie GuibertFlorie Guibert Senior Frontend Engineer, Plan:Product Planning
Jack ChapmanJack Chapman Frontend Engineer, Plan:Product Planning
Kassio BorgesKassio Borges Staff Backend Engineer , Plan:Product Planning
Nicolas DularNicolas Dular Staff Backend Engineer, Plan:Product Planning
Backend EngineerBackend Engineer Backend Engineer
Rajan MistryRajan Mistry Frontend Engineer, Plan:Product Planning

Plan:Optimize

Name Role
Brandon LabuschagneBrandon Labuschagne Fullstack Engineering Manager, Plan:Optimize
Alex PennellsAlex Pennells Senior Frontend Engineer, Plan:Optimize
Ezekiel KigboEzekiel Kigbo Senior Frontend Engineer, Plan:Optimize
Felipe ArturFelipe Artur Senior Backend Engineer, Plan:Optimize
Pavel ShutsinPavel Shutsin Staff Backend Engineer, Plan:Optimize
Rudy CrespoRudy Crespo Frontend Engineer, Plan:Optimize

Plan:Knowledge

Name Role
John HopeJohn Hope Senior Manager, Engineering, Plan
Vladimir ShushlinVladimir Shushlin Engineering Manager, Plan:Knowledge

Create

Create:Code Review

Name Role
André LuísAndré Luís Senior Engineering Manager, Create:Source Code, Create:Code Review
François RoséFrançois Rosé Engineering Manager, Create:Code Review
Phil HughesPhil Hughes Staff Fullstack Engineer, Create:Code Review
Stanislav LashmanovStanislav Lashmanov Senior Frontend Engineer, Create:Code Review
Thomas RandolphThomas Randolph Senior Frontend Engineer, Create:Code Review

Create:Code Creation

Name Role
Matt NohrMatt Nohr Backend Engineering Manager, Create:Code Creation
Allen CookAllen Cook Senior Backend Engineer, Create:Code Creation
Backend EngineerBackend Engineer Backend Engineer, Create:Code Creation
Jan ProvaznikJan Provaznik Staff Backend Engineer, Create:Code Creation
Leaminn MaLeaminn Ma Senior Backend Engineer, Create:Code Creation
Mikołaj WawrzyniakMikołaj Wawrzyniak Staff Backend Engineer, Create:Code Creation
Missy DaviesMissy Davies Backend Engineer, Create:Code Creation
Pam ArtiagaPam Artiaga Senior Backend Engineer, Create:Code Creation
Shola QuadriShola Quadri Associate Backend Engineer
Sri RanganSri Rangan Staff Fullstack Engineer, Create:Code Creation
Tian GaoTian Gao Backend Engineer, Create:Code Creation
Vitali TatarintevVitali Tatarintev Senior Backend Engineer, Create:Code Creation

Create:Editor Extensions

Name Role
Kisha Mavryck RichardsonKisha Mavryck Richardson Engineering Manager
Andrei ZubovAndrei Zubov Senior Frontend Engineer, Create:Editor Extensions
Anna SpringfieldAnna Springfield Senior Backend Engineer, Create:Code Creation
Bohdan ParkhomchukBohdan Parkhomchuk Backend Engineer, Create:Editor Extensions
Dylan BernardiDylan Bernardi Associate Backend Engineer, Create:Editor Extensions
Elwyn BensonElwyn Benson Senior Frontend Engineer, Create:Editor Extensions
Erran CareyErran Carey Staff Fullstack Engineer, Create:Editor Extensions
Jean-Gabriel DoyonJean-Gabriel Doyon Backend Engineer
John SlaughterJohn Slaughter Staff Backend Engineer, Create:Editor Extensions
Juhee LeeJuhee Lee Fullstack Engineer
Karl JamoralinKarl Jamoralin Backend Engineer
Laura IonelLaura Ionel Senior Backend Engineer
Marvin GayMarvin Gay Backend Engineer, Create:Editor Extensions
Michael Angelo RiveraMichael Angelo Rivera Fullstack Engineer, Create:Editor Extensions
Olena HK.Olena HK. Senior Frontend Engineer, Create:Editor Extensions
Tomas VikTomas Vik Staff Fullstack Engineer, Create:Editor Extensions
Tristan ReadTristan Read Senior Frontend Engineer, Create:Editor Extensions

Create:Remote Development

Name Role
Adebayo AdesanyaAdebayo Adesanya Engineering Manager
Chad WoolleyChad Woolley Staff Backend Engineer, Create:Remote Development
Cindy HalimCindy Halim Fullstack Engineer, Create:Remote Development
Daniyal ArshadDaniyal Arshad Backend Engineer
Enrique AlcántaraEnrique Alcántara Staff Frontend Engineer, Create:Remote Development
Joseph FletcherJoseph Fletcher Associate Frontend Engineer
Paul SlaughterPaul Slaughter Staff Fullstack Engineer, Create:Remote Development
Safwan AhmedSafwan Ahmed Backend Engineer, Create:Remote Development
Vishal TakVishal Tak Staff Backend Engineer, Create:Remote Development
Zhaochen LiZhaochen Li Backend Engineer, Create:Remote Development

Create:Source Code

Name Role
André LuísAndré Luís Senior Engineering Manager, Create:Source Code, Create:Code Review
Devi PoosarlaDevi Poosarla Engineering Manager, Create:Source Code Backend
Jacques ErasmusJacques Erasmus Senior Frontend Engineer, Create:Source Code
Chaoyue ZhaoChaoyue Zhao Frontend Engineer, Create:Source Code
Paulina Sedlak-JakubowskaPaulina Sedlak-Jakubowska Senior Frontend Engineer, Create:Source Code

Stable Counterparts

The following members of other functional teams are our stable counterparts:

Name Role
Désirée ChevalierDésirée Chevalier Senior Software Engineer in Test, Dev:Plan
Emilio SalvadorEmilio Salvador VP, Dev Relations and Community
Jay McCureJay McCure Senior Software Engineer in Test, Dev:Create
John CoghlanJohn Coghlan Director, Developer Advocacy
Kalyani YerraguntlaKalyani Yerraguntla Learning & Development Program Manager
Nivetha PrabakaranNivetha Prabakaran Software Engineer in Test, Dev:Manage

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.

  • Issue Tracker
  • Slack Channels
    • #sd_dev_engineering
    • #s_manage
    • #s_plan
    • #s_create

Create Stage
The Create Stage is a group of teams including Code Creation, Code Review, Editor Extensions, Remote Development, and Source Code.
Foundations Stage
The Foundations stage deals with cross functional work from the design system, to importers, to the navigation.
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.

Training