GitLab logo

GitLab Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 550 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
50.5% Positive experience

Which role are you interviewing for?

30 roles · 550 reports

Candidate interview experiences

First-hand accounts from people who interviewed at GitLab.

Showing 4 of 550
GitLab logo
GitLab

Stock Administrator

Finance · half a year ago

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical

The interview process felt pretty disorganized; I was scheduled and then had my interview cancelled three times before I could finally talk to the hiring manager. While the hiring manager was pleasant, the overall experience was a bit unusual. I felt the interview went well and even ran over the allotted time. However, the very next day, I received an email stating the position had already been filled. The timing of this seems a little off, and I'm left wondering how seriously my application was truly considered. If you're considering this role, I'd advise proceeding with caution.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

GitLab logo
GitLab

Software Developer

Engineering · nearly a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding Behavioral

The interviews for the frontend and backend roles were well-executed. The interviewers were composed and allowed me to demonstrate my technical abilities. However, the hiring manager interviews were less satisfactory. Each hiring manager has a unique interview style, making it difficult to know what they are looking for. I believe GitLab should implement a more consistent process and provide better training for their interviewers. In one interview, the example I provided was clearly not what they sought. They could have either pointed this out and changed the topic, or initially clarified their expectations. In another interview, I was criticized for not mentioning information that the interviewer hadn't even inquired about. It's concerning to receive excellent feedback on technical stages from recruiters and hiring managers, yet barely pass the hiring manager rounds. This indicates a significant discrepancy. Interviewing is generally challenging in software engineering, and it's an area that both individual contributors and engineering managers need to continuously improve.

Confirmed questions1 question
  • Can you review this code written in Vue and Rails?
GitLab logo
GitLab

Analyst

Analytics · nearly a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Take home Onsite
Interview formats
Behavioral Technical Case

it was pretty straightforward: first a recruiter screen for about 30 mins, then an interview with the hiring manager for about 45 mins, followed by team interviews with 3 team members, each lasting 30 mins. Sometimes we have to do a case study where you gotta show your data analysis skills on an anonymized data set.

Confirmed questions3 questions
  • Tell me about a time when your data analysis influenced the course of your work.
  • How did you transform raw data into actionable insights?
  • Demonstrate your data analysis abilities with an anonymized dataset.
GitLab logo
GitLab

Data Analyst

Analytics · nearly a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Take home
Interview formats
Behavioral Technical Coding

The recruiter reached out to set up a call to chat about culture fit and career goals, and said I could ask her anything and she'd get back to me fast. That same day, she set up a meeting with the hiring manager, who really dug into my resume and asked some smart scenario-based questions. I passed that part and got a take-home assignment with scenario questions, SQL, and Tableau. After sending it back, I tried contacting the recruiter a few times to see what was next. But I got zero response. Even a quick 'yes' or 'no' would've been useful, but hearing nothing back after trying so many times was a real downer.

Confirmed questions1 question
  • Can you explain how you make sure KPIs are aligned across different teams?

GitLab Interview Questions

Quoted word for word from GitLab interview reports.

What are the differences between database queries and selecting objects using the application's memory?

Read reports

Were you able to get the repo cloned and running on your machine?

Read reports

Could you review this merge request and give some detailed comments on potential improvements to the code?

Read reports

For a new feature or product idea, how would you define and plan out the Minimum Viable Product (MVP)?

Read reports

Imagine you're the CEO of Netflix. What's your 3-5 year strategy to dominate the streaming market and become number 1?

Read report

What charts would be appropriate for a CPO or other high-level product executive's dashboard?

Read report

Can you suggest some potential acquisition targets that would be of interest to GitLab?

Read report

Can you describe a common security weakness pattern and how to overcome it?

Read report

How do you communicate technical information to people who don't have a technical background?

Read report

Formats, difficulty and experience

Across all 550 GitLab interview reports.

Interview formats

Behavioral 42%
Technical 33%
Coding 9.3%
Presentation 9.1%
Other 3.7%

Interview difficulty

Easy 16%
Average 69.5%
Difficult 14.5%

Candidate experience

Positive 50.5%
Neutral 15.1%
Negative 34.4%

Reports by job function

Engineering 256
Sales 108
Operations 47
HR 26
Marketing 26
Product 19