Process
Applied online, had an initial video call screening with an HR person, had a video call interview with a designer, completed a design challenge, then was turned down.
The video calls were very casual. There were no technical or difficult questions. Everyone was very friendly.
I spent a significant amount of time studying their handbook before the calls, and more time on the design challenge. I was perfectly fine with being turned down. However, it is a little frustrating receiving zero feedback on why and zero feedback on the design challenge that I had taken the time to complete.
I received a very generic, canned letdown email, to which I replied soliciting feedback. That was ignored.
Advice to GitLab: Be transparent and honest with candidates. It doesn't take much time and goes a long way to write one or two sentences of honest feedback. Don't send canned email replies to people. It goes against your self-proclaimed brand and values.
Questions
Why do you want to work for GitLab?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitLab Web Developer role in United States.
Success Rate
GitLab's interview process for their Web Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for GitLab's Web Developer interview process in United States.
GitLab Work Experiences
- 5.0Excellent Company, No ConsTechnical Architect • Current EmployeeAugust 19, 2021Pros: Good company, and I recommend others.Cons: No cons at all. Good one.
- 5.0Open by default, and remote-firstSoftware Developer • Current EmployeeJuly 18, 2016Pros: Work from anywhere. Remote-first company. Flexible work hours. Most positions are very visible to the public, so that provides many opportunities for your career, but also for your feeling of accomplishment. Being personally thanked by users for something you have contributed to is great. Extremely smart groups of peers, across all positions, but also extremely positive and excited about the work we do. Many aspects of the company are very transparent to the public, like the marketing and IT issue tracker, and the company handbook. Within the company, many things that aren't normally public to most employees often are. By that, I mean things like the status of revenue and sales, and the progress of executive-related decisions. For developers, lots of opportunities to speak at conferences.Cons: Most of the cons that come with remote work include not seeing your co-workers face-to-face nearly enough (though we do all meet up at least once a year so far, and make extensive use of video calls, even just for random life chats). Growth has been in response to demand, which means there is always a lot of demand. Everyday, we are fighting fires. This means that sometimes you will be the one to fight the fires, which sometimes requires above-average hours and effort. Cats. If you own a cat and haven't worked remotely before, it's time to get used to your cat "helping" you with your work. This is not specific to GitLab, though. ;)
- 5.0Very good comapny with Great Remote cultureFullstack Engineer • Current EmployeeBerlinDecember 3, 2025Pros: GitLab has the best company culture.Cons: Nothing as such; it has been great.
