Growth:Acquisition Group
Vision
The Acquisition Group is part of the [Growth Stage]. We work on connecting our users with our product value.
- I have a question. Who do I ask?
Questions should start by @ mentioning the Product Manager for the Acquisition group or creating a new issue in the Growth Product [Acquisition issues] list.
Mission
The Growth:Acquisition Group works on product priorities and growth deliverables with our Growth product managers and contributes to Growth initiatives including the Registration Flow and Continuous onboarding.
Team Members
The following people are permanent members of the Growth:Acquisition team:
Name | Role |
---|
Stable Counterparts
We work directly with the following team members in the Growth:Acquisition group:
Name | Role |
---|---|
![]() |
Senior Fullstack Engineer, Growth::Acquisition |
![]() |
Senior Security Engineer, Application Security, Plan (Project Management, Product Planning, Certify), Create:Source Code, Growth, Fulfillment:Purchase, Fulfillment:Provision, Fulfillment:Utilization, Systems:Gitaly |
![]() |
Staff Fullstack Engineer, Growth:Acquisition |
![]() |
Principal Product Manager, Growth:Acquisition |
![]() |
Senior Fullstack Engineer, Growth::Acquisition |
![]() |
Engineering Manager, Growth |
![]() |
Senior Security Engineer, Application Security, Secure (Static Analysis, Dynamic Analysis, Composition Analysis, Vulnerability Research), Growth (Acquisition, Activation). |
![]() |
Senior Product Manager, Growth:Activation |
![]() |
Customer Success Manager, Growth (Enterprise EMEA) |
![]() |
Associate Fullstack Engineer, Growth:Acquisition |
![]() |
Fullstack Engineer, Growth:Acquisition |
How We Work
- We’re data savvy
- In accordance with our GitLab values
- Transparently: nearly everything is public
- We get a chance to work on the things we want to work on
- Everyone can contribute; no silos
Prioritization
Prioritization is a collaboration between Product, UX, Engineering, and Quality.
- We use the ICE framework for experiments
- We use Priority and Severity labels for bugs
Workflow
-
We use the Product Development workflow when working on issues and merge requests across multiple projects.
-
We use a shared Kanban workflow board for both groups - Acquisition and Activation for work in the build phase of the product development flow.
-
We use refinement threads on issues to discuss our approach and estimate weight of upcoming work.
Common Links
- Growth Stage
- Acquisition issues
#g_acquisition
in Slack (GitLab internal)
14f88a89
)