Backend Engineer, Secure C# applicants have rated the interview process at GitLab with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 50.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Backend Engineer, Secure C# roles take an average of 14 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at GitLab overall takes an average of 32 days.
Common stages of the interview process at GitLab as a Backend Engineer, Secure C# according to 2 Glassdoor interviews include:
Drug test: 50%
Presentation: 50%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at GitLab in Jun 2020
Interview
It was pleasant process, in my case I had about 4 interviews related to different areas, as for example: the initial screening interview, then a technical interview, later on an interview more about how I address work situations and my workflow, and the last interview was a mixture between tech questions and workflow. The overall process for me took about 3 months (since the 1st communication until I got an offer), since GitLab had to finish interviewing all other candidates. They were totally open to me about timing and open to accept questions or schedule meetings when needed. In general, they are totally open about how my application was moving forward.
Interview questions [1]
Question 1
I don't recall the exact words, but the idea of the question, it was about : What was the last mistake I had made and how did I address it?
I applied through a recruiter. The process took 2 weeks. I interviewed at GitLab (Panamá) in Jul 2020
Interview
First interview is just somebody selling you the company. Second interview was technical and very tricky. They have a GitLab handbook of how they conduct interviews that they encourage you to read but if the interviewer has not read it. It won't do you any good. It is a really awkward interview at times, you will not get any feedback as to what is expected from you. You will ask questions and will not get a response. Then, get an unrelated question. At some point the interviewer plays an uncooperative client but he wont really explain what the dynamic of the exercise is.
The other part of the interview is to make a merge request using GitLab. You should review the code but he wont really tell you what the code is suppose to do or what he wants you to fix. If this is a C# interview for the fuzz testing position, I will give you a clue. He wants you to implement dependency injection on a poorly implemented repository pattern. He will also asks you how to manage exception but with very vague instructions.
2
Top companies for "Compensation and Benefits" near you