Taro Logo

Software Engineer, Backend Interview Experience - Remote, Oregon

March 1, 2019
Negative ExperienceNo Offer

Process

I had a technical screen with the recruiter, then a coding test consisting of a code review which took about 2 hours to do. I then had a pairing session with another developer to review my code review and implement the feedback. Following this, I had two behavioral interviews.

I received a notice that they were going to pass because I had some short stints in my employment history. I repeatedly discussed this with multiple individuals who gave no indication that my answers were sufficient, and the rejection immediately followed an email from them informing me they would check my references then make an offer.

The people themselves were nice enough, but they strung me along before ultimately passing due to a reason that was completely unrelated to my ability to actually do the job.

Questions

Code review of an existing PR with failing unit tests.

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the GitLab Software Engineer, Backend role in Remote, Oregon.

Success Rate

0%
Pass Rate

GitLab's interview process for their Software Engineer, Backend roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive50%
Neutral0%
Negative50%

Candidates reported having mixed feelings for GitLab's Software Engineer, Backend interview process in Remote, Oregon.

GitLab Work Experiences