Pros: For most companies, values are just buzzwords with very little meaning or relevance. This is not true at GitLab. The pros of working at GitLab almost all tie directly back to the values that GitLab takes very seriously. Collaboration: People here are kind. There are all sorts of resources and helpful tips to welcome newcomers and collaborate with the greatest community in the kindest way. Folks share their opinions, say thanks, and give feedback. For challenging collaborative problems, GitLab provides a variety of resources to educate folks on how to navigate the tough bits. Results: One of the sub-values of "results" is "Measure results not hours" – and it shows. People are not tracking how often you're "active" on Slack, how many meetings you make, or how many things you say in meetings. Being handbook and async-first in an all-remote company means that the value of your contributions speaks volumes more than how you "appear". Efficiency: People, for the most part, write things down. This is the core of being handbook-first. And let me tell you: I can't imagine working any other way. It's a lot of information to parse out. But imagine working somewhere where your coworkers don't interrupt you every 15 minutes to ask the same question someone else asked. Or where you don't feel bad having to interrupt your coworkers with the same thing. You can literally Google internal company processes and get an answer. Not sure how to write a good code review? Google "GitLab code review process," and you'll find the handbook page. Want to know how to submit an expense report? Type "expense reporting GitLab" in your navigation bar, and you've got the answer. It's amazing, and I think it's extremely understated as a benefit here. It gets overshadowed by being all-remote. But if you're an information-savvy knowledge worker, this is the way you must demand to get work done. Diversity, Inclusion & Belonging: This is where asynchronous communication comes in. And there are explicit instructions about having uncomfortable conversations. The company explicitly talks about what this value means, instead of being an overarching idea that's too broad to be useful. I've never believed a company ever cared about this value until I interviewed at GitLab. The interviewing process is as equitable as it can be (there is still a power differential, of course. And human systems are imperfect, and I have many privileges so I can't necessarily evaluate this objectively). But again, you can Google all the hiring details and know what to expect. You can see the statistics in terms of hiring length, hiring metrics, etc. There are some confidential pieces of information here, of course, but the transparency builds to this diversity value. Iteration: This value can be challenging, but it can also be freeing. I feel empowered to make small, reversible changes all the time. To pitch ideas, deliver on promises, and come back later to clean things up. I'm never blocked because I'm waiting for approval three levels up. Transparency: This is another value that lends to the handbook-first pro. Other pros: * Remote work is awesome. * It's clear how you add value to the company. * The company is clearly growing, and the opportunity is there. * The brand name is super cool – I am so proud and excited to have it on my resume. * People are welcoming, excited, and always thinking of cool new ideas. * Lots of opportunity to work on new projects, but also a healthy focus on making sure existing solutions are appropriately leveraged and maintained. * All levels of management are very accessible. * The compensation is transparent, and more than fair.

Cons: There is a lot of information out there. It can be very challenging to parse through and find signal versus noise, especially as a newcomer. Being remote is great, but sometimes you miss the in-person relationships and collaboration style. The company is moving at a fast pace. They talk a lot about work/life balance, and they clearly take steps to enforce it. But I personally find myself being highly engaged and thoughtful about work outside of working hours because of all the activity going on. It's exciting, but it can be hard to turn off when your "office" is just inside your laptop, and the company is abuzz with activity at all hours of the day. This is a personal problem, not necessarily a systemic one. But I think many people share this. The onboarding process itself is very structured and easy to follow, with plenty of information. But I have spoken with many colleagues who feel like they were thrown into the deep end early on. I think a startup at this phase has a lot of that – the company needs to move quickly, and employees need to be ready for that. Be ready to feel a little lost for the first few months with information overload and a fast pace of work. I think most folks adjust, and GitLab has plenty of resources and systems to help. But it can be a lot, for sure. Because everything is handbook-first, everyone is empowered to make decisions, etc. There are plenty of conflicting information sources out there. I think this is true of any company. The challenge at GitLab is that having all the documentation public means that any person in the company might stumble upon two conflicting pieces of information – rather than a different company where those conflicting points of view are siloed to teams. In that specific case, being siloed can actually be useful for individuals.

Pros: Nearly everything you do can be shared with others, which helps to give a real sense of accomplishment. Work with people from dozens of countries around the world; our internal chat and team calls have made me more aware of events and cultures around the world. A significant portion of your work will involve contributing to open-source software. Everyone is remote. You can work anywhere with no manager looking over your shoulder and no (physical) interruptions from coworkers. The handbook is available for anyone to read, and our issue tracker and merge requests offer useful insight for any engineers looking to apply. If you spend a few hours reading through issues, merge requests, the handbook, etc., you can get a very good feel for how the company operates, including the stuff that doesn't always give the appearance of perfection (I wouldn't have it any other way). Summits give you the opportunity to travel to other cities and countries every nine months to be with your teammates and hang out for a week, about half work and half activities (scavenger hunt, zipline, tubing, rafting, etc.).

Cons: - Remote work can at times be lonely if you don't take full advantage of video calls, coworking spaces, etc. (though there are policies in place to help with this, it's something to note). - Chat can be distracting if you let it be; you definitely want to have self-control to avoid spending too much time on its distractions. - Depending on what time zone you live in and what hours of the day you work, it can be difficult to quickly get answers to questions, feedback on product/technical decisions, etc. Most Europeans and Americans will have plenty of people available. - We rely heavily on written documentation to allow for asynchronous work, but things can sometimes get lost or become outdated due to the sheer amount of documentation we have.

Pros: Good WFB, competitive pay, and remote.

Cons: Management is not that great.