Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Manage Team

On this page

Manage

The purpose of this page is to document engineering-led processes and initiatives specific to the Manage team.

The responsibilities of this team are described by the Manage product category. Among other things, this means working on GitLab's functionality around user, group and project administration, authentication, access control, and subscriptions.

To find out more about what areas of the product we are responsible for, the product vision, and the product process (e.g. how to get Issues prioritized), then please head over to the Manage product page.

Team members

Person Role

Stable counterparts

Person Role
Luke Bennett Frontend Engineer, Manage
Dennis Tang Frontend Engineering Manager, Manage & Fulfillment
Martin Wortschack Senior Frontend Engineer, Manage
Brandon Labuschagne Frontend Engineer, Manage
Ezekiel Kigbo Frontend Engineer, Manage
Illya Klymov Senior Frontend Engineer, Manage
Liam McAndrew Engineering Manager, Manage:Access
Matej Latin Senior Product Designer, Manage
Chris Peressini Product Designer, Manage
Ahmad Sherif Site Reliability Engineer, Manage, Monitor & Configure
James Edwards-Jones Backend Engineer, Manage
Jeremy Watson Senior Product Manager, Manage:Access
Imre Farkas Senior Backend Engineer, Manage
Evan Read Senior Technical Writer, Manage, Verify, Configure, Growth
Manoj M J Backend Engineer, Manage
Adam Hegyi Backend Engineer, Manage
Aakriti Gupta Backend Engineer, Manage
George Koltsov Backend Engineer, Manage
New Vacancy - Liam McAndrew (Interim) Engineering Manager, Manage:Measure
Sanad Liaquat Senior Test Automation Engineer, Manage
Virjinia Alexieva Senior Product Manager, Manage:Measure
Małgorzata Ksionek Senior Backend Engineer, Manage
Pavel Shutsin Senior Backend Engineer, Manage
Désirée Chevalier Test Automation Engineer, Manage

Working on unscheduled issues

Everyone at GitLab has the freedom to manage their work as they see fit, because we measure results, not hours. Part of this is the opportunity to work on items that aren't scheduled as part of the regular monthly release. This is mostly a reiteration of items elsewhere in the handbook, and it is here to make those explicit:

  1. We expect people to be managers of one, and we use GitLab ourselves. If you see something that you think is important, you can request for it to be scheduled, or you can work on a proposal yourself, as long as you keep your other priorities in mind.
  2. From time to time, there are events that GitLab team-members can participate in, like the issue bash and content hack days. Anyone is welcome to participate in these.

When you pick something to work on, please:

  1. Follow the standard workflow and assign it to yourself.
  2. Share it in #g_manage to encourage transparency