Two things, first: #1. I have always been inspired by the idea of working in an organization like GitLab, as it is a synonym for Open Source code. #2. Despite generally negative reviews on Glassdoor, I tried not to be biased prior to the interview.
I was contacted by a Technical Recruiter one week prior to the interview via LinkedIn to arrange an initial call. I arranged the interview and informed the recruiter accordingly.
By then, the only information I had regarding the position was that it is an engineering position related to security (Defense).
The interview was via an online platform. The process was to be started by the recruiter and was done so, three minutes later than the arranged time. Of course, no one needs to be that punctual; no problem with that.
As stated, they had a kind of not-so-common online platform, so after those three minutes, it took me one minute to set my settings to 'allow' for my mic and webcam.
All set, and the first thing I hear from the recruiter is: "that took a while".
I tried to convince myself that I did not hear that clearly, but as it turned out by the end of the conversation, my impression was unfortunately correct.
First question, more or less, to describe my background and my current position's tasks. I started talking about them for about 3'-5'. The recruiter seemed not to be interested in what I was saying—that is the most appropriate way I can describe her reaction—and asked me about my technical skills.
I was figuring out by that time where this was going, so I told her about some recent development projects, as well as the fact that I am not comfortable with Go and Ruby On Rails, the two programming languages she mentioned in the beginning of the conversation.
As soon as I finished my sentence, she replied with something along the lines: "we will have to stop here, thank you for your time, ... (you know the rest probably)".
Duration of the call: 7' - 9'.
I was really upset by the end of this interview. Not only do technical recruiters sometimes seem to have no idea what they are looking for, but they also tend to be quite disrespectful.
I have been wondering why it was that hard to have been asked my experience in Go and Ruby On Rails via LinkedIn? Why was I being interviewed when I clearly stated nowhere that I know any of those two programming languages? WHO is supposed to know all the programming languages whatsoever?
Dear recruiters, please start to recognize the value of your candidates. You are dealing with people looking for a job while doing your job. That should be sufficient to treat them with the minimum amount of respect.
What is your experience with Go and Ruby on Rails?
The following metrics were computed from 1 interview experience for the GitLab Software Engineer role in Poland.
GitLab's interview process for their Software Engineer roles in Poland is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for GitLab's Software Engineer interview process in Poland.