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.
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.
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.
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.
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 is established in the following ways.
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:
Top 10 Reasons to Work for GitLab:
Dmitriy started GitLab when he pushed the initial commit.
Sid announced GitLab on HN.
First 10 people get access to GitLab Cloud (now known as GitLab.com).
Series A Funding was signed.
Anniversary of our first ever summit in Amsterdam with 25 GitLab team-members.
What better way to convey a sense of who we are and how we work together, than by sharing the stories about it?
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!
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!
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.
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