My recent interview experience with GitLab was disappointing and felt like a significant waste of time. The process was extensive, involving multiple stages:
I successfully passed all these stages, which built up my anticipation for a positive outcome. However, during the team interview, I was informed that I was not selected due to a lack of experience with Large Language Models (LLM).
This feedback was particularly frustrating because my CV, which clearly outlines my extensive experience in Computer Vision, was available to them from day one. My expertise in AI, particularly in computer vision, was evident, and I believe AI skills are highly transferable across domains.
To add to my frustration, it became apparent that the selected candidate was an internal transfer from a different team within GitLab. If this was the intended outcome, it is baffling why they subjected external candidates to such a lengthy and rigorous process, only to dismiss them for reasons that were apparent from the outset.
This experience has left me questioning the efficiency and transparency of GitLab's hiring practices. It felt like my time and effort were not respected, and the rationale behind the final decision was not adequately aligned with the requirements communicated during the initial stages.
Questions about different situations.
Technical questions about PR.
Pretty easy and simple questions.
The following metrics were computed from 1 interview experience for the GitLab Custom Model Backend Engineer role in United Kingdom.
GitLab's interview process for their Custom Model Backend Engineer roles in the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for GitLab's Custom Model Backend Engineer interview process in United Kingdom.