All interviews took about a month.
After I sent the application, I was contacted by the hiring manager to organize a Zoom call. This was the general screening call; after that, a technical interview followed.
Before the technical interview, I was sent a task, which was to review a merge request and provide comments on it. During the call, I had to explain my comments and then share my screen to fix the tests in order for the CI pipeline to pass.
After that, a behavioral interview with a team manager followed. After that, the final interview, more or less the same as before, was scheduled with a director of engineering.
Three days after the final interview, which I thought went fine, I received a more or less standard email that GitLab will not be proceeding with my application. The reason was quite vague; the engineering team simply did not want to proceed.
I understand that GitLab aims for the great fit and tech skills, and almost all of the applications are rejected, but I feel like I spent 5 hours doing the interviews and double that preparing for the interviews for no reason. I would have preferred to be rejected ASAP so it would save everyone's time.
The people I was interviewing were friendly, helpful, and transparent. It's just that the final decision was far from transparent, but that's life, I guess.
How do you show your leadership skills?
What was the time that you had to do a very complicated task? How did you do it?
What challenges did you have working asynchronous remote work?
The following metrics were computed from 1 interview experience for the GitLab Software Engineer, Backend role in Lithuania.
GitLab's interview process for their Software Engineer, Backend roles in Lithuania is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for GitLab's Software Engineer, Backend interview process in Lithuania.