How we use GitLab to build GitLab

GitLab employees actively engage in "dogfooding" by using their own platform for various operational and development tasks, allowing them to test and gain confidence in their product. GitLab.com is utilized for public work, while dev.GitLab.org is reserved for sensitive development activities, with access granted to team members. New employees are onboarded through a simple and accessible employee handbook, and communication is facilitated through Slack, emails, and the use of Issues and Merge Requests in repositories. This approach fosters a collaborative environment where team members contribute to problem-solving and product improvement. Additionally, annual team events, such as attending OSCON in The Netherlands, promote team building and personal interaction.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.