
Four candidates describe GitLab Software Engineer interviews that weigh behavioral and values questions alongside technical discussion, including merge request review for some, with reported loops of four to five rounds. Two received offers and two did not.
$162K
Avg. Base Comp
$200K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
GitLab's Software Engineer interviews, as four candidates describe them, give behavioral and values questions as much weight as the technical conversations. Two candidates received offers, one of whom accepted, and two were turned down.
The technical side leans on code review rather than puzzle solving. One candidate completed a take-home that involved reviewing a merge request of roughly 200 lines, then walked through it in the technical interview and implemented suggestions on the fly; they received a rejection the next day. Another described merge request reviews as central, with interviewers probing design decisions and trade-offs. A third said the technical portion covered computer science fundamentals and felt conversational.
Behavioral questions run through nearly every stage. Candidates mention STAR-style questions about conflict and difficult teammates, a time they disagreed with a manager, and why they wanted to join GitLab. The candidate who accepted an offer was asked whether they had read the handbook and which core value they felt most strongly about.
Reports describe four or five rounds, ending with a senior engineering manager or an area VP. Prepare specific stories, give a sincere answer about GitLab's mission, and practice explaining your reasoning on someone else's code.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the GitLab process.
The loop moved quickly, and I met a mix of team members and senior managers along the way. The technical conversations with people I would be working alongside were there to see whether I could hit the ground running. The other sessions leaned toward culture fit, and those carried a lot of weight. One question has stuck with me: whether I had actually read the company handbook, and which of its core tenets I felt most strongly about and why. I answered it by naming the values that matched how I already like to work and explaining the reasoning behind them. The culture side was clearly being evaluated as seriously as the technical side, so I would not treat it as a formality. I accepted the offer at the end of the process.
Prep tip from this candidate
Read GitLab's handbook before your interviews and be ready to name the core value you agree with most and explain why, since that exact question came up. Expect the culture-fit conversations to carry real weight alongside the technical ones, not as a warm-up.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at GitLab
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Random SQL Sample | |
| Raining in Seattle | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Find Bigrams | |
| Payments Received | |
| Get Top N Frequent Words | |
| N-gram Dictionary | |
| Minimum Change | |
| Employee Salaries (ETL Error) | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Find the First Non-Repeating Character in a String | |
| LRU Cache 1 | |
| Rectangle Overlap | |
| Google Maps Improvement | |
| Data Pipelines and Aggregation | |
| Fast Food Database | |
| KNN From Scratch | |
| Employee Project Budgets | |
| Integer to Roman | |
| Download Facts | |
| Nightly Job | |
| The Brackets Problem | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Friend Requests Down | |
| Lowest Paid |
Synthesized from candidate reports. Individual experiences may vary.
Candidates who describe the start of the process say it opened with a recruiter screen. One called the recruiting team responsive and said they followed their interview manual closely, which made the process feel structured. Expect to talk about your background and what draws you to GitLab.
One candidate received a take-home to review a merge request of roughly 200 lines, then discussed it in the technical interview and implemented suggestions live. Another described merge request reviews as central, with questions on design decisions and trade-offs. A third reported computer science fundamentals in a conversational format.
Candidates describe conversations with a hiring manager or engineering manager and, in one case, a panel with the team. Questions covered past experience, what interested them about GitLab, and a time they disagreed with a manager. One candidate noted that sessions with future teammates were meant to test whether they could contribute quickly.
Final stages reported include a senior engineering manager and an area VP. Culture fit carried real weight: one candidate was asked whether they had read the handbook and which core value they agreed with most. Another with a five-round process, who did not receive an offer, said STAR questions came up in nearly every round.