Please see our primer for more general information about GitLab.
Back in May 2016, the whole team was a total of 85 GitLabbers
Top 10 reasons to work for GitLab:
Work with helpful, kind, motivated, and talented people.
Work remote so you have no commute and are free to travel and move.
Have flexible work hours so you are there for other people and free to plan the day how you like.
Everyone works remote, but you don't feel remote. We don't have a head office, so you're not in a satellite office.
Work on open source software so you can interact with a large community and can show your work.
Work on a product you use every day: we drink our own wine.
Work on a product used by lots of people that care about what you do.
As a company we contribute more than we take, most of our work is released as the open source GitLab CE.
Focussed on results, not on long hours, so that you can have a life and don't burn out.
Open internal processes: know what you're getting in to and be assured we're thoughtful and effective.
Approximately every 6-9 months, we gather in person to see how tall everyone is (hard to see with video conferencing), and to get to know each other better by working and 'playing' together.
Summit in Amsterdam, the Netherlands
Here are some impressions from our first Summit in October 2015.
Summit in Austin, TX, the USA
In May 2016, with a team existing of 85 people, met up in Austin,TX to see if they are (still) as awesome as seen on Google Hangout. Here is some footage that our team put together to show how much fun we had.
Anniversary of our first ever summit in Amsterdam with 25 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!
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!
By sending out our Feedback Form (find the link to the "open" form by accessing this "closed" document) we gather feedback from the team members anonymously. We then share the main highlights and concerns / wishes / things people wonder about with the entire team by discussing them during our Team Call and posting all topics that came up along with their responses here (with the exception of topics that by nature are not shared outside of the company). The responses may be altered from the original wording in an effort to maintain anonymity, while also maintaining the same spirit and message of the response.
Feedback from January 2016, and responses
"What do you wish we had / What are you wondering about"
"Contractor or employee? Worried about job security as a contractor."
We value all team members equally, regardless of the legal arrangement that you have with GitLab. Due to legal restrictions and the difficulty of having people be employees outside of the US or NL (where we have a legal entity), a large portion of the team are contractors (21 out of 46). At GitLab, as everywhere else, job security relies mostly on how you are performing as a team member, and how the company performs as a whole. By the way, the contracts that we use are all viewable on https://about.gitlab.com/handbook/contracts/
"More patience and consideration with ideas from newer people, things are sometimes quickly rejected as 'won't work' or 'not interested' without much explanation."
It is difficult to comment on what may have been specific circumstances, but if you have felt that your idea was rejected too quickly or without explanation, then please know that this was not intended to be unkind or harsh. There are many ideas and for the sake of efficiency we give minimal reasoning in responding. This is also due to the nature of asynchronous communication where it is hard to tell if an answer is extensive enough to satisfy the question. If you feel that an idea is being rejected rather quickly, you can and should request more explanation. This might lead to a fruitful discussion and a reconsideration.
"Wish we had more time"/ "Wonder if sometimes we go too fast and should go slower to focus on quality and testing more"
Always be sure to reach out to your manager if you feel that you need more guidance. Your peers are a Slack message away.
"Maybe a more competitive salary"
From the handbook: "If you are unhappy with anything (your duties, your colleague, your boss, your salary, your location, your computer) please let your boss, or the CEO, know as soon as you realize it. We want to solve problems while they are small."
"A step between review/QA and deployment."
Review happens through merge requests, and QA happens as part of the release process. We can't think of anything else at the moment that would not introduce gates that cause delay and inefficiency.
"Off-site meetings during the year and/or team-specific summits, like a hackathon"
We had a Summit in Oct'15, and are having one in May'16. We aim to have these every 6-9 months. We are thinking about organizing a hackathon during the Summit; please upvote if you want it to happen!
"We share a lot about our software 'side'; can we share more about our other 'sides' (like how marketing does marketing) in a "team blog"? This would help in hiring awesome people!"
We love blog posts and sharing all of GitLab's 'sides'. Please channel your inner need to write a blog post (or part of it!) on our blog repo.
"Additional training for dev people, maybe? Specific suggestions for topics include agile coding, code quality, and there is a suggestion for Robert "Uncle Bob " Marcin (https://sites.google.com/site/unclebobconsultingllc/) for code quality
After some research within the team there was a greater interest in a "birds of a feather" gathering than formal training. We're looking to do this during our Summit trip to Austin.
"What features are we planning? I hear about price changes and optional features?"
"How are we doing? How does the Board see it? Can we keep up the growth and the Sales?"
Khosla is really happy so far. Keeping up growth depends on demand generation
"If we are sometimes too open and too transparent in a way that hurts us?"
So far the only negative thing is that we suspect that competitors release their stuff early to preempt us, we think it is great that they are adjusting their schedule to ours!
"Creating/using a standard for interviewing candidates."
Good idea, a lot of us use standard interview questions https://about.gitlab.com/handbook/hiring/#interview-questions but merge requests are welcome.
"More formality in development process."
What form of formality? We welcome changes that don't reduce our productivity. Potentially we could start using issue weights more to gauge the load.
"What do you like about working here?"
A lot of love for the team
Keywords people used to describe their fellow team members are: 'talented, caring, teamwork, approachable, honest, frank, smart, brilliant, skilled, team spirit'.
Four people mentioned it specifically, and this one sums it up nicely: "Working on a product that I actually love to use". Respondents also mentioned the fast pace of development.
Respondents value being involved in Open Source, with phrases such as: 'proving that open source is awesome and working with the rest of the community, working on open source while getting paid for it is a dream job!'
Freedom and opportunity
We are a remote-first company and our team members like: 'being remote-first, working from home, having personal independence, the freedom to choose what to work on, the freedom that you don't get in a corporate office environment, flexibility to get things done, slim process, slack oriented'
People also mentioned the opportunity to learn, and the massive opportunity that the project and the company has.
Several people mentioned that they really like the team dynamic, specifically: 'the support that you need is there, you have the ability to take on multiple hats and responsibilities, everyone and everything is open to constant improvement, ability to collaborate even though we're remote, we're remote but still have a great sense of "team", love the cross discipline collaboration that goes on every day'
Freedom, flexibility, enthusiasm, passion, great, smart, engaging, enjoy teaching, feels like a family, great dynamic, supportive, approachable execs, supportive, transparency, speed of innovation, remote working, company sponsored training, great Summit in Amsterdam.
Great product, ability to create new processes, company growth, no burocracy, no high pressure, opportunity, our growth, the challenge of maintaining quality of people, product, brand etc, laser focus on improving collaboration through social coding, market adoption, our work is public so we can talk about it, and our ability to create new processes.
What we wish we had or what we want to be doing & What we’re doing about it
More team members.
Bigger feature gap between CE and EE.
Current plan is to have one EE feature added per release, so over time the difference will grow.
Current plan is to have a summit every 6-9 months.
We're working on this with GitLabUniversity (GLU) content, continuous improvements to documentation and the handbook
Customer success events, starting in the Bay Area.
Cool idea, start an issue and make it happen!
Coaching on Agile and Lean approaches for Engineering team.
Great idea, we'll look into it. Suggestions are welcome.
A scale with happiness of last work week for feedback.
We've working this into our feedback from in a different setting for now.
Global presence of Service Engineers, and dedicated trainer and training materials.
We're working on this through hiring. Also, we have high hopes of GLU, ongoing content creation, etc. to help out here.
What we’re wondering about & the answers to our thoughts
Stock options: terms, conditions
Does the handbook answer your questions? (https://about.gitlab.com/handbook/stock-options). Please feel free to ask Paul.
What the company will look like 3, 6, 12 months from now? (community-ish, enterprise-ish)
The community and people using GitLab will keep growing. 12 months from now we'll answer all questions from the community on all platforms (from forum to Stack Overflow), we 'll have a proper swag shop and have more developer oriented content (blog posts, videos).
Enterprise wise we'll have double the features we have now, a twice as large sales team, and many add-ons. Feel free to ask something more specific if you need more detail. And of course try to shape it as you think it should look.
How committed are we to building EE features and having significant releases each month?
Very committed. At least one tentpole EE feature every month. Next 3 releases contain 2 or 3 each! https://about.gitlab.com/direction/
Sales team hiring plan
We're hiring but it is not a priority until everyone is up to speed and trained. But we expect that to happen soon, and the marketing machine will come up to speed soon, after which hiring becomes a priority.