GitLab Site Reliability Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GitLab.
GitLab
Site Reliability Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Technical Coding
I connected with the recruiter and had a positive initial conversation. Following that, I spoke with various team members, which was also a good experience. However, the team I was interested in had their SRE positions cut, so I was reassigned to a different SRE role. I then completed a technical assessment at home and discussed it with a developer. While he was polite, he seemed a bit distant. They mentioned that not knowing Ruby and Go fluently was acceptable, but I had the impression that wasn't entirely true. I didn't get an offer and tried to follow up for more information and feedback, but I never heard back.
Confirmed questions1 question
- GoLang code review assessment
GitLab
Site Reliability Engineer
Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical
The interview process was pretty long and annoying. There were 3 interviews in total, but it took 2 months to finish everything. First, I talked to the recruiter, then the hiring manager, and finally, a team member conducted a technical interview.
Confirmed questions1 question
- Can you tell me about your experience with PostgreSQL?
GitLab
Site Reliability Engineer
Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel
Interview formats
Behavioral Technical
So I was contacted on Linkedin by the recruiter and the whole thing took about three weeks, which I thought was pretty quick! It was supposed to be four rounds: Recruiter screening, Technical Interview, Hiring Manager Interview, and then a Leadership interview. For me, the order was a bit mixed up cause of the holidays, but it was all pretty chill. The team was super nice!
Confirmed questions3 questions
- The Hiring Manager Interview involved in-depth STAR-based questions.
- The Leadership Interview covered similar STAR-based questions but in a more general way.
- The technical interview was pretty straightforward; I had to troubleshoot some Kubernetes issues concerning deployments and node affinity.
GitLab Site Reliability Engineer Interview Questions
Quoted word for word from GitLab interview reports.
“How would you debug an Nginx problem on Ubuntu?”
Read reports →“What are some common kubectl commands you use?”
Read reports →“Can you show me how to parse log files?”
Read reports →“Given a Kubernetes cluster with common connectivity/scheduling issues, how would you identify the problems?”
Read reports →“Describe your process for releasing a web application.”
Read report →“What potential challenges do you anticipate during a web application release?”
Read report →“Can you share some feedback you've received? Which parts did you agree with, and which did you not?”
Read report →“Can you share a time when...?”
Read report →“Were you asked mostly cultural questions?”
Read report →Formats, difficulty and experience
Across all 14 GitLab interview reports.