I'd applied online from a job listing found via LinkedIn. The initial application form had a few technical questions. I was then contacted by a technical recruiter from GitLab to set up a time and date for screening call. I was then asked to set up a time and date for a technical interview, and was provided access to a GitLab repository for a Ruby on Rails project, and asked to make comments on anything I saw worthy.
Having worked with Ruby for a number of years and with GitLab in my current position, I felt fairly confident going into the interview. However, the role appears to require extensive knowledge of Ruby on Rails, and I was told 20 minutes or so into the interview that unfortunately a strong background in Rails specifically was required for the position. So it looks like I'll be brushing up on Rails before reapplying. Gitlab is a great product and would love to work there one day.
Overall, technical interview and recruiters were pleasant and helpful.
Interview questions [3]
Question 1
A user browses to https://gitlab.com/gitlab-org/gitlab-ce in their browser. Please describe in as much detail as you think is appropriate the lifecycle of this request and what happens in the browser, over the network, on GitLab servers, and in the GitLab Rails application before the request completes.