GitLab Senior Engineer: merge request review, pair programming and a behavioural hiring manager call
After I applied I got an email to schedule an initial recruiter screening call where we discussed my motivations, background, compensation expectations and what I thought about working remotely. I have been working remotely for a few years so it was easy to convince them that I know how to work well remotely.
The next round is pretty unique. You get a merge request link and are expected to review it and then do a pair programming session with one of their engineers. I spent a lot of time reading the MR and the code so that by the time it came to the interview I had already guessed the way they were going to ask me to improve it, so it's an easy way to look good.
Once I passed that I had a hiring manager call where I had a few technical questions about past projects but then the rest were all behavioral that are covered in the playbook so prep your answers for that and you will be fine.
I heard back from the recruiter after about a week and the total comp was good but my company decided to outbid them so I ultimately rejected the offer.
2 comments
How long did you get with the merge request before the session? And was it in a language you knew, or do they pick for you?
Interesting that the counter-offer won. GitLab comp tends to be location adjusted, so that might be why it was easy for your current company to beat.