Gitlab hero border pattern left svg Gitlab hero border pattern right svg

GitLab Culture

On this page

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 creativity, 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 everyting from your schedule and your workspace to your job description and your skills.

All-remote work

Being part of our all-remote 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 60 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.

Advantages

Top 10 reasons to work for GitLab:

  1. Work with helpful, kind, motivated, and talented people.
  2. Work remote so you have no commute and are free to travel and move.
  3. Have flexible work hours so you are there for other people and free to plan the day how you like.
  4. Everyone works remote, but you don't feel remote. We don't have a head office, so you're not in a satellite office.
  5. Work on open source software so you can interact with a large community and can show your work.
  6. Work on a product you use every day: we drink our own wine.
  7. Work on a product used by lots of people that care about what you do.
  8. As a company we contribute more than we take, most of our work is released as the open source GitLab CE.
  9. Focused on results, not on long hours, so that you can have a life and don't burn out.
  10. Open internal processes: know what you're getting in to and be assured we're thoughtful and effective.

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


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 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


Planned date of November 18th, 2020 to take GitLab public

Many people ask "why are you going public on November 18th, 2020?" November 18th 2020 was set for the following reasons:

  1. It is roughly 10 years after DZ started working on the project
  2. It is roughly 5 years after the first employees received 4 year stock option vesting schedules
  3. When determined to do a public offering in 2020, it was as late as possible in 2020, as markets do not typically move in December
  4. It was originally decided to be November 16th, since that was the last week before Thanksgiving. Paul (our CFO) knew this because it was the birthday of his twins.
  5. Minutes after publishing the date Paul looked at the calendar and saw it was a Monday. This isn’t a great day of the week to go public since people are digesting the news of the weekend, so in 20 minutes after publishing the date was moved Wednesday, November 18th, 2020.
  6. Only after picking the new date Sid realized that it would have been the 100th birthday of the grandfather he is named after.