I was given a task three days prior to the interview. It was described as something you shouldn't have to invest more than an hour into.
The task was about reviewing a PR in GitLab's codebase. All the coding should be done in the live session.
The task itself didn't have any specific instructions, so it was more of a free-style code improvement. It was a bit confusing, and I failed to show my skills to the full extent.
I was very irritated about it because I do have the necessary level and actually like everything about the organization.
The backbone of the client is rendered with haml, and a Vue instance is attached to it. The task was a bit obfuscated, and as it turned out later, there were two parts to it:
I missed the second part in my preparation for the interview, and that was the reason I failed.
I got nervous, froze during the interview, and I wasn't given a second chance.
Fifteen minutes after the interview ended, I realized what I did wrong, corrected everything, and made some suggestions. I fixed the unit tests and the failing CI pipe, but there was no reply on my actions/email, and I felt like I was cut off cold turkey with no feedback from the tech lead at all.
Now, that's a bit harsh.
The following metrics were computed from 1 interview experience for the GitLab Frontend Developer role in Amsterdam, North Holland.
GitLab's interview process for their Frontend Developer roles in Amsterdam, North Holland is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for GitLab's Frontend Developer interview process in Amsterdam, North Holland.