Taro Logo

Software Engineer Interview Experience - Canada

August 1, 2022
Negative ExperienceNo Offer

Process

Standard recruiter screen, then a 90-minute technical interview. I was told it would involve reviewing a merge request and making changes to improve it.

After finishing this task, I was surprised when the interviewer asked a completely unrelated object-oriented design question.

Honestly, I thought I did well. I was able to answer all follow-up questions, and from my perspective, I got along well with the interviewer. However, the recruiter followed up with feedback from the interviewer which didn't make any sense (e.g., "did not memorize arguments for a specific method").

I know it might sound like I'm a disgruntled candidate writing a negative review after being rejected, but I have completed hundreds of interviews and have left positive feedback even when I didn't get the job. This experience has left me completely confused.

For what it's worth, my advice to Gitlab would be to have two interviewers per interview. For a company of its size, I have never had a technical interview where it was just one interviewer evaluating the candidate. Having two interviewers would increase accountability and allow for a more objective evaluation.

Questions

Suggest and implement changes to a merge request.

Object-oriented design question (not mentioned anywhere in any communications or the interview guide).

Was this helpful?

Interview Statistics

The following metrics were computed from 7 interview experiences for the GitLab Software Engineer role in Canada.

Success Rate

14%
Pass Rate

GitLab's interview process for their Software Engineer roles in Canada is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive29%
Neutral14%
Negative57%

Candidates reported having very negative feelings for GitLab's Software Engineer interview process in Canada.

GitLab Work Experiences