San Francisco, California, United States of America
Company Reviews
GitLab is the Intelligent Orchestration Platform where software teams and their AI agents stay in flow to amplify their capacity for innovation. Together, they automate repetitive tasks to plan, build, secure, test, deploy and maintain software. With GitLab, software teams spend less time on coordination overhead and more time on the next big idea.
GitLab Duo Agent Platform provides AI agents that automate tasks across the software lifecycle. Agents handle code generation, security analysis, code review, CI/CD troubleshooting, and custom workflows — while teams maintain control through enterprise governance.
Build what's next with us. Explore open roles and join our talent community: https://about.gitlab.com/jobs/
Rating Reviews
Rating is calculated based on
18
reviews and is evolving.
Pros: The best part is the flexibility. Being remote means I can manage my day around appointments or family stuff. It's awesome for anyone in a software engineer role who needs that kind of autonomy, especially at a big tech company like this.
Cons: It's easy to work too much if you don't set boundaries. There's always more to do on the DevOps platform, and sometimes it feels like the expectation is to be always available. Some teams have more intense deadlines, making true work-life balance tough.
Advice to Management: Managers need to actively encourage team members to disconnect and take breaks. Help distribute the workload better so people aren't constantly feeling swamped. More emphasis on sustainable pace, not just output.
Show more
Pros: I love the total remote flexibility; you can truly work from anywhere, which is a huge benefit for work-life balance. It's awesome for managing personal appointments and staying productive without a commute. For a Software Engineer, this kind of work arrangement is a massive plus.
Cons: Sometimes communication can feel a bit fragmented with everyone in different time zones. It's easy to get lost in Slack, and impromptu whiteboarding sessions don't really happen. Not ideal if you thrive on constant face-to-face interaction or quick, synchronous problem-solving.
Advice to Management: Keep fostering that asynchronous communication and maybe offer more virtual team-building events. It helps bridge the distance for remote teams and build stronger connections.
Show more
Pros: I appreciate GitLab's transparency; it's a huge plus for a remote-first company. My direct managers and project leads in software development have been really supportive and understanding of the async work style. There's a lot of freedom in how you get your work done.
Cons: Higher-level leadership can feel pretty distant from day-to-day engineering. Sometimes, major decisions come down that don't quite make sense for specific teams or projects. The strategic direction for the DevOps platform can shift, which makes it tough for long-term planning.
Advice to Management: Focus on better communication from executive leadership down to individual contributors, especially for those of us on engineering teams. Try to make sure strategic shifts are clearly tied to day-to-day impact for Senior Software Engineers.
Show more
As a remote-first company, what is GitLab's approach to fostering team connection and maintaining its unique culture across different time zones?
No answers yet.
What is the day-to-day experience like working remotely at GitLab, and how does the asynchronous communication model affect team collaboration for engineers?
No answers yet.
How does GitLab support remote employees in maintaining work-life balance, especially for those in different time zones?
No answers yet.
What is the remote work culture like at GitLab, especially for software engineering roles?
GitLab is fully remote, with a strong emphasis on asynchronous communication. This means collaboration often happens across different time zones, and documentation is key for keeping everyone informed on projects.
What is the day-to-day experience like for a remote software engineer at GitLab, and how does the asynchronous communication model impact collaboration?
As a remote-first company, GitLab's engineering teams operate asynchronously, which means documentation and written communication are key. This structure allows for flexibility across different time zones, but requires proactive effort in sharing updates and seeking feedback from colleagues globally. You'll find a strong emphasis on transparency in all aspects of work.
How does GitLab's remote-first culture impact collaboration and team bonding for software engineers?
GitLab's remote-first approach fosters asynchronous communication and documentation, which is effective for globally distributed software engineering teams. While it requires intentional effort, the company encourages virtual coffee chats and team events to build connections across different time zones.
What is the remote work culture like at GitLab, and how does it foster collaboration among globally distributed teams?
GitLab's remote-first culture is deeply ingrained, with asynchronous communication and extensive documentation being key to collaboration. Team members utilize tools like Slack and GitLab issues to stay connected and share progress across different time zones, which is essential for their large, international engineering teams.
How does GitLab's remote-first approach impact team collaboration and management for software engineers?
GitLab's remote-first culture emphasizes asynchronous communication and documentation, which can be very effective for distributed software engineering teams. Management focuses on outcomes, providing flexibility but requiring clear goal setting and regular check-ins to ensure alignment across globally dispersed teams.
