Taro Logo

Senior Software Engineer Interview Experience

November 1, 2019
Neutral ExperienceNo Offer

Process

The interview process was a bit lengthy; getting meetings scheduled across timezones can be a challenge, with roughly one week between each interview.

The technical interview involved reviewing a merge request and answering questions about refactoring and how Go channels work. There were two behavioral interviews: one with a hiring manager and another with the director of the group I was being considered for.

Lots of good information was written down on their wiki, which helps with reviewing beforehand to understand product roadmaps, frame STARs answers in terms of company values, and understand the career path.

No feedback was provided, only a generic rejection via email. I expect more after three rounds of interviews.

Questions

Review a merge request with Golang channels and fix some broken tests.

STAR type questions around leadership and situational behavior.

Emphasis on previous experiences working at large scale on a distributed system.

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the GitLab Senior Software Engineer role in United States.

Success Rate

0%
Pass Rate

GitLab's interview process for their Senior Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral25%
Negative75%

Candidates reported having very negative feelings for GitLab's Senior Software Engineer interview process in United States.

GitLab Work Experiences