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.
|Liam McAndrew||Engineering Manager, Manage|
|Rubén Dávila||Backend Engineer, Manage|
|James Lopez||Senior Backend Engineer, Manage|
|James Edwards-Jones||Backend Engineer, Manage|
|Imre Farkas||Senior Backend Engineer, Manage|
|Małgorzata Ksionek||Senior Backend Engineer, Manage|
|Pavel Shutsin||Senior Backend Engineer, Manage|
|Luke Bennett||Frontend Engineer, Manage|
|Dennis Tang||Interim Frontend Engineering Manager, Manage, Growth, and Fulfillment|
|Martin Wortschack||Senior Frontend Engineer, Manage|
|Brandon Labuschagne||Frontend Engineer, Manage|
|Ezekiel Kigbo||Frontend Engineer, Manage|
|Matej Latin||Senior UX Designer, Manage|
|Chris Peressini||UX Designer, Manage|
|Jeremy Watson||Product Manager, Manage, Fulfillment|
|Andreas Kämmerle||Product Manager, Manage|
|Devin Sylva||Senior Site Reliability Engineer, Manage|
|Sanad Liaquat||Senior Test Automation Engineer, Manage|
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:
When you pick something to work on, please:
#g_manageto encourage transparency