GitLab logo

GitLab Security Engineer Interview Questions
& Process

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

Based on 10 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GitLab.

Showing 3 of 10
GitLab logo
GitLab

Security Engineer

Engineering · more than a year ago

Mid Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical

My interview experience at GitLab was pretty disappointing, especially given how much they emphasize their core values. The whole process dragged on for more than 6 weeks, and that was just for two interviews after the initial screening. My interview schedule also didn't match what they described in their handbook. The handbook also says recruiters should keep candidates updated on their progress, but that wasn't my experience. I actually got an offer from another company, but I really wanted this role at GitLab because their culture seems great. I tried to ask my recruiter about the timeline since I had another offer pending. She briefly replied that the next session would be scheduled soon and that they'd try to do it before my other offer's deadline. After that, I heard nothing. I sent another follow-up email, and still no response. Then, the next week, I got an email saying the position had already been filled. Luckily, I didn't turn down the other offer, but I really wish GitLab had been more upfront and communicative. I get that they might be looking at other candidates, but I believe respect, transparency, and courtesy should be mutual. This includes responding to candidates and letting them know where things stand. I'm sharing this in hopes that GitLab can improve its talent acquisition process.

Confirmed questions1 question
  • Will you be asked about the core values and if you have read the handbook?
GitLab logo
GitLab

Security Engineer

Engineering

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

So I had this interview experience and as a US MILITARY RESERVIST, I was declined just because I was transparent and asked about how Gitlab supports active reservists. Their policy handbook is publicly available and states that a prospective member of Gitlab shall not be discriminated due to military obligations. The tech recruiter mentioned I came across well. I replied back with more details about my “1-weekend every 2 months commitment” which is better than most reservists I know. The security manager never gave me a chance to prove myself. Disqualified me based on being military? I’m honestly disgusted. The tech recruiter was very pleasant to talk to and shared some really good info. I’ve shared my experience with other big software companies I’ve interviewed with and they were shocked as I am(military experience or not). Hopefully the executives read this and are able to make changes. But if you’re a reservist, I advise you to stay away and save yourself some time from being discriminated.

Confirmed questions1 question
  • Could you describe your background and experience with SIEM and SOAR tools?
GitLab logo
GitLab

Senior Security Engineer

Engineering

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

The interview process followed the company's handbook exactly, so there were no surprises regarding the timeline and steps. Everyone I spoke with, from the recruiter to the final interviewers, was very pleasant and created a comfortable atmosphere. They seemed genuinely interested in understanding me as a person, my values, and my technical abilities relevant to the position. The interviews were spaced out nicely, with about 3-4 days between each.

Confirmed questions4 questions
  • Can you tell us about yourself and your background?
  • How do you typically interact with colleagues?
  • Describe a situation where you faced a conflict and how you handled it.

GitLab Security Engineer Interview Questions

Quoted word for word from GitLab interview reports.

Can you discuss attacks and defenses related to the OWASP top 10 vulnerabilities?

Read reports

What are your thoughts on high-level DNS and networking concepts?

Read report

What makes you interested in Gitlab, and what do you appreciate about the company?

Read report

What are your thoughts on adapting to a fully remote work environment?

Read report

Will you be asked about the core values and if you have read the handbook?

Read report

Could you describe your background and experience with SIEM and SOAR tools?

Read report

Formats, difficulty and experience

Across all 10 GitLab interview reports.

Interview formats

Behavioral 50%
Technical 45%
Coding 5%

Interview difficulty

Easy 40%
Average 50%
Difficult 10%

Candidate experience

Positive 40%
Negative 50%
Neutral 10%