GitLab·Software Engineer

GitLab Software Engineer interview experience

No offer

Hard

Negative

Dallas, TXPosted Oct 2021 · Candidate report, summarized by Dataford

The start of my process was unusually drawn out, mostly because scheduling and my own inbox became part of the story—I missed an initial recruiter email, then caught a later follow-up.

Once I finally connected with the recruiter, the rest of the steps came together. I was invited to a technical interview where I was given a faux merge request on GitLab.com. I reviewed and commented on the code on my own time, then later did live corrections during the meeting.

After that, I expected the behavioral portion to work like a conversation about my real experiences—the kind of STAR-style stories I was used to based on the handbook I’d read. Instead, the behavioral interview felt technical, with very specific technical answers the interviewer seemed to be searching for. I got

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

GitLab Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All GitLab interview guidesEvery role we cover at this company