Taro Logo

Site Reliability Engineer Interview Experience - Canada

April 1, 2022
Neutral ExperienceNo Offer

Process

Got a recruiter call from a resume I dropped back in 2019. Probably as my current position is more interesting to them now.

The process involved several rounds:

  • Recruiter reached out about various teams/positions. I decided to pick the Delivery team. They were working with releasing the Gitlab application stack (Rails app + DB) on Kubernetes. Plus, they are also involved with the process of packaging features from other teams into a release.
  • Chat with the hiring manager.
  • Technical interview (Kubernetes).
  • 2x Peer Interviews (general Q&A with members of the team).
  • Final interview with Director of Infra + another manager.
  • Decision.

Questions

In the technical interview, I was given a Kubernetes cluster with some common problems in connectivity/scheduling, etc. The task was to figure out what was wrong.

The next couple of interviews focused on specific knowledge in releasing software (due to the team).

There wasn't a clear format, just "tell me how you release this web app + what problems do you expect."

My guess is that they are trying to see if you have done this in multiple ways.

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the GitLab Site Reliability Engineer role in Canada.

Success Rate

0%
Pass Rate

GitLab's interview process for their Site Reliability Engineer roles in Canada is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for GitLab's Site Reliability Engineer interview process in Canada.

GitLab Work Experiences