Real, anonymous reports from people who interviewed for Software Engineer at GitLab, newest first and distilled into what to expect across the loop.
I had an overall average experience with a multi-round loop, and one later interaction noticeably soured the process.
I went through an average-but-frustrating GitLab process where technical performance didn’t translate into clear, consistent follow-through.
The interview process typically begins with a recruiter screening, where candidates discuss their background and expectations for the role. This stage is generally straightforward, with a focus on alignment and motivation.
Candidates can expect multiple technical interviews that may include coding assessments, PR reviews, and discussions on technical concepts. Interviewers are often calm and supportive, but the consistency of questions and feedback can vary significantly.
The hiring manager round often combines technical and behavioral assessments, but candidates report a lack of clarity regarding team direction and expectations. This stage can feel procedural and sometimes leads to abrupt rejections.
Candidates may encounter various assessment formats, including take-home assignments and live coding exercises. These assessments are designed to evaluate both technical skills and cultural fit, with an emphasis on real-world problem-solving.
Several candidates noted issues with coordination and communication throughout the interview process, including delays, lack of updates, and abrupt changes in role status. Clear communication is critical for maintaining candidate momentum.
Candidates often report receiving little to no feedback after rejections, which can lead to frustration. Understanding the outcome and receiving constructive feedback is seen as a valuable part of the process.