From application to offer, the process took around 2 months.
As the reason for the delay, I was told it was because of the GitLab Summit and a change of the applicant tracking system. While still a bit long, it is understandable under these circumstances.
Every contact I had was excellent and very nice.
About 3-4 weeks after my application, I was sent a questionnaire with some factual questions and a programming task. After I passed this stage, I had meetings with my recruiter, team members, and management. There were about 6 total, each taking around 30-45 minutes.
In these meetings, I was asked general application questions and again some factual and behavioral questions.
In the end, I was asked to provide 3 references from previous companies.
A few days later, I got the offer to join, which I gladly accepted.
How do you behave when a coworker and yourself have an argument?
The following metrics were computed from 1 interview experience for the GitLab Site Reliability Engineer role in Remote, Oregon.
GitLab's interview process for their Site Reliability Engineer roles in Remote, Oregon is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for GitLab's Site Reliability Engineer interview process in Remote, Oregon.