Process
I applied through the Gitlab website and was contacted by a recruiter. He asked me to set my availability on a shared calendar, choosing times outside of my normal working hours to accommodate interviewers located in different timezones.
The first interview was with the recruiter. He informed me that I would "probably be a no" because I lacked experience in the feature I'd be managing. He said that they had already passed on several candidates for the same reason.
Surprisingly, I was invited to interview with a Director-level person. The interview, I thought, went well. It was not rushed, and she asked me a lot of questions related to my managing experience. There were very few questions regarding my technical aptitude.
After the interview, I received a rejection email a few days later with no feedback or reason.
Questions
What's the biggest team you've managed?
Why do you want to work at GitLab?
Have you ever had to fire someone? What was that like?
How do you source candidates?
What is your process for interview and vetting candidates?
Was this helpful?
Interview Statistics
The following metrics were computed from 7 interview experiences for the GitLab Engineering Manager role in United States.
Success Rate
GitLab's interview process for their Engineering Manager roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having negative feelings for GitLab's Engineering Manager interview process in United States.
GitLab Work Experiences
- 2.0Great culture and talent, but company is strugglingEngineering Manager • Current EmployeeSeattle, WAJune 8, 2026Pros: It used to be a great company with talented people and an amazing culture.Cons: The company is becoming a sinking ship. There is a new layer of VPs and CTO that drive the company downhill.
- 5.0GitLab sets the standard for remote workingEngineering Manager • Current EmployeeJuly 9, 2019Pros: I have worked remotely for several years and worked at GitLab remotely for 1 month. I must say that GitLab is light years ahead of most companies when it comes to creating the most efficient remote work environment. I think the key to their success is using tools to support their remote needs. I have listed a few below: Recruiting Remotely * Use Zoom for candidate interviews Release Planning Remotely * Use GitLab to track and plan software releases Agile Ceremonies * Use Automated Slack Bot to facilitate daily Stand Ups across remote time zones * Use GitLab to perform asynchronous Sprint Retrospectives Meetings & Company Announcements * Use Zoom and YouTube for meetings & company announcements Socializing Remotely * Use Zoom for informal Coffee Chats * Use Slack for various social channelsCons: I have nothing to report.
- 5.0The best company to work for!Engineering Manager • Current EmployeeOctober 8, 2021Pros: So transparent about everything we do. GitLab really lives by its values every single day, and we apply them in everything we do. Benefits are very, very good too! Though GitLab is an all-remote company, there are so many recurring events/activities and encouraged coffee chats with team members that make us feel very connected to each other. The idea that everyone can contribute is very accurate from the very first day, and they trust you to make decisions regardless of how long you've been here. It really feels like family (they also even say family comes first), and I'm grateful to be a part of this embracing and talented team!Cons: Honestly, there is nothing I can think of.
