Product Solutions Resources Partners Pricing Support Talk to an expert Get free trial Login GitLab Culture On this page Introduction Life at GitLab Everyone can contribute Freedom to iterate All-remote work Culture at GitLab Advantages Other pages related to culture Historical Anecdotes October 8th, 2011 August 24th, 2012 September 14th, 2012 November 13th, 2012 July 22nd, 2013 April 18th, 2014 March 4th, 2015 August 15th, 2015 October 10th, 2015 Team Stories The Boat The cattle IPO date comes in handy… 2 years out So that's what it's like to work at GitLab… You are here: About GitLabGitLab Culture Introduction Please see our company page for more general information about GitLab. You can see how our team has grown at the GitLab Contribute page. Life at GitLab It’s an exciting time to be part of GitLab. We're a fast-growing, all-remote team, and we're looking for people to join us around the world. Here's a look at what you can expect from our culture and all-remote environment. Everyone can contribute Our size and our mission (that everyone can contribute) mean that our team members can — and are expected to — make an impact across the company. Because we all use our product internally, you don't have to be a developer to learn to collaborate in the GitLab tool. From your very first week, no matter your role, you'll gain the technical skills needed to access, question, and contribute to projects far beyond your job description. This unique approach works because we're a team of helpful, passionate people who want to see each other, the company, and the broader GitLab community succeed. We learn from each other, challenge each other, and thank each other. Come prepared to do meaningful work that will help shape the future of the company. While the opportunities to contribute are boundless in a growing organization like GitLab, they may not be clearly defined. You'll need to think creatively, speak up to see how you can help, and be willing to try something new. Freedom to iterate At GitLab, our value of iteration has a unique impact on the way we operate and get things done. Working this way means our team members are expected to quickly deliver the minimum viable change in their work instead of waiting to produce a polished, completed product. While this can be a challenging practice to adopt at first, it's liberating to be able to make mistakes, get feedback quickly, and course correct to reach a better outcome, faster. As our company and the industry continue to grow, you'll have the freedom to change and constantly evolve everything from your schedule and your workspace to your job description and your skills. All-remote work In the above interview with Stuart Miniman of theCUBE, GitLab CEO and co-founder Sid Sijbrandij discusses the merits of operating a 100% remote organization, and why he believes it's the future of work. At GitLab, we're figuring out a lot of things you have to do to be all-remote, and we're trying to share those lessons. That's anything from working handbook-first to communication styles and being intentional about informal communication. If you Google "GitLab all-remote", you'll find tons of tips. And those are based not just on what we say, but what we do. We have a public handbook of over 3000 pages with all our internal processes. You can check out what we really do to make this work. I think it's going to be the future. In the future, companies who make digital products are going to be much more all-remote. And we want to enable that trend. We think it's great for team members. GitLab is one of the world's largest all-remote companies, and being a part of our team offers unique advantages beyond the requisite flexibility you'll find in many organizations. As a GitLab team member, you can work from anywhere with good internet. Whether you're an adventurer looking to travel the world while still pursuing your career, a parent or caregiver who wants a job that allows you to spend more time with family, or somewhere in between, you'll have the freedom to contribute when and where you do your best work. But there's more to our all-remote culture than the daily flexibility it provides. By nature, having no offices or headquarters makes us more inclusive, more transparent, and more efficient in everything we do. With a team spread across over 65 countries around the globe, we invite diverse perspectives, we document everything, and we collaborate asynchronously. Despite all of its benefits for team members, our company, and the world, remote work isn't for everyone. Learn more about all-remote work at GitLab and decide if it's right for you. Culture at GitLab Culture at GitLab is established in the following ways. Work style (how we work). This is defined and articulated in our values and handbook. Camaraderie (mutual trust and friendship). This is created and maintained by informal communication. In other organizations, culture may be defined through the personality of the group. This includes people who have traits in common and people who you enjoy spending time with. Note that this is not something that should matter when evaluating people for work, and this is not what we mean with Culture at GitLab. Watch this live speaker series, hosted on 2021-11-18, with Carter Gibson and Markus Mühlbauer from Google on Building Internal Culture. Some key takeaways from the call include: Culture isn't preserved. Instead, it evolves. Every team member can contribute to and iterate on the company culture. It's important to scale communication as companies grow to accommodate differnt learning styles, communities, and taem member expectations. Culture shouldn't look at roles or levels in the company. There’s no way for a company to dictate a culture from the top down. If you manage to build up this sense of belonging in everyone in the company, it builds up resilience. Advantages Top 10 Reasons to Work for GitLab: Mission: Everyone can contribute Results: Fast growth, ambitious vision Flexible Work Hours: Plan your day so you are there for other people & have time for personal interests Transparency: Over 2,000 webpages in GitLab handbook, GitLab Unfiltered YouTube channel Iteration: Empower people to be effective & have an impact, Merge Request rate, We dogfood our own product, Directly responsible individuals Diversity, Inclusion & Belonging: A focus on gender parity, Team Member Resource Groups, other initiatives Collaboration: Kindness, saying thanks, intentionally organize informal communication, no ego Total Rewards: Competitive market rates for compensation, Equity compensation, global benefits (inclusive of office equipment) Work/Life Harmony: Flexible workday, Friends and Family days Remote Done Right: One of the world's largest all-remote companies, prolific inventor of remote best practices Other pages related to culture GitLab 101 GitLab Contribute Internal Feedback Diversity, Inclusion and Belonging All-Remote GitLab Songbook Still a Startup Historical Anecdotes October 8th, 2011 Dmitriy started GitLab when he pushed the initial commit. August 24th, 2012 Sid announced GitLab on HN. September 14th, 2012 First 10 people get access to GitLab Cloud (now known as GitLab.com). November 13th, 2012 GitLab CI is officially announced. July 22nd, 2013 GitLab Enterprise Edition is announced. April 18th, 2014 GitLab Cloud renamed to GitLab.com. March 4th, 2015 GitLab in Y Combinator winter 2015 batch. August 15th, 2015 Series A Funding was signed. October 10th, 2015 Anniversary of our first ever summit in Amsterdam with 25 GitLab team-members. Team Stories What better way to convey a sense of who we are and how we work together, than by sharing the stories about it? The Boat Back then, the whole team used to fit in one car. And the car was called "the Boat". We even took the Boat from San Francisco to Las Vegas to celebrate Job's bachelor party, but as you can see in this video, he thought we were going to visit a customer in Los Angeles! The cattle Staring down the cattle? Our CFO, Paul, was on vacation on a cattle ranch, during a time of fundraising. Normally vacation is vacation of course, but in this case it was necessary to have some calls now and again which required strong internet. To get to strong internet, Paul had to cross fields with cattle in them, and stare them down. Over the course of many trips he learned that cattle are docile, mostly... but don't turn your back on them because they can't be outrun! IPO date comes in handy… 2 years out After spending a couple of days in meetings with customers in New York City, USA, Sid and Kirsten had a few hours before their flight and wanted to visit the WTC Observatory deck. It didn't work out but our IPO date did work out in their favor. In the keynote at our Cape Town event, Sid explains what happened. So that's what it's like to work at GitLab… Being new to GitLab, our CRO, Michael McBride joined Sid in meeting with customers in New York City, USA where customers got a glimpse of what it's like to work at GitLab for him Twitter Facebook YouTube LinkedIn Why GitLab? Product Solutions Services DevOps tools Is it any good? Releases Pricing Get started Resources All resources All-Remote Blog Newsletter Events Webcasts Topics Training Docs Developer Portal Install Community Customers Contribute Community Programs Direction Technology Partners Channel Partners Open Source Partners GitLab for Open Source GitLab for Education GitLab for Startups Shop Community Forum Support Get help Contact Sales Contact Support Support options Status Customers Portal Company About What is GitLab? Jobs Culture Leadership Team Press Investor Relations Analysts Handbook Security Contact Terms Privacy Cookie Preferences Trademark Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license View page source — Edit in Web IDE — please contribute. © 2021 GitLab B.V. This website uses cookies We use cookies to make our websites and services operate correctly, to understand how visitors engage with us and to improve our product and marketing efforts. See our cookie policy for more information.Cookie Policy Cookies Settings Accept All Cookies