Taro Logo

Software Engineer, Backend Interview Experience - Saint Paul, Minnesota

September 1, 2019
Positive ExperienceGot Offer

Process

There were 4 phases: Phone Screen, Technical Interview, Manager Interview, Director Interview.

The phone screen was a quick 20-30 minute phone call with an HR Representative. They asked me mostly basic questions about my knowledge of Rails and my work history. At the end of the interview, they told me the next steps and answered my questions.

The technical interview was one of the most interesting I've seen. They assigned me a merge request in a private repository a couple of days before the interview and had me review it. Then, in the interview, we talked through my proposed changes and what to do. The merge request itself was a change to a Rails codebase and some requirements. It had a few questions asking about why tests were failing and why things didn't work.

The manager interview was pretty standard. The manager of the team I was interviewing to join asked me about my experiences and practices.

The director interview was pretty similar to the manager interview but a little more forward-looking. This was described to me as a "Personality Fit" interview.

I had another offer pending, so they were willing to schedule the manager and director interview for the same day to speed things up.

Questions

What does good collaboration look like?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the GitLab Software Engineer, Backend role in Saint Paul, Minnesota.

Success Rate

100%
Pass Rate

GitLab's interview process for their Software Engineer, Backend roles in Saint Paul, Minnesota is incredibly easy as the vast majority of engineers get an offer after going through it.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for GitLab's Software Engineer, Backend interview process in Saint Paul, Minnesota.

GitLab Work Experiences