
What two candidates report about GitLab security interviews: a technical recruiter screen, a hiring manager talk centered on vulnerability disclosure, and a slow final decision. Neither candidate received an offer.
$135K
Avg. Base Comp
$208K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates describe GitLab security interviews, and both ended without an offer. Their reports differ, so treat them as two separate experiences rather than one fixed process.
One candidate, interviewing for a security role connected to PSIRT, said the recruiter screen was surprisingly technical, more so than they expected from a recruiter conversation. The hiring manager interview that followed stayed high-level. Most questions were introductory and focused on vulnerability disclosure, including a request to walk through a disclosure the candidate had handled before. The candidate left without a clear sense of what the team owned or where PSIRT was heading.
The practical takeaway is to prepare a vulnerability disclosure story you can tell from intake to resolution. Cover triage, how you communicated with the reporter and with engineering, and how it was closed out. Also bring your own questions about team priorities and PSIRT's direction, since the candidate felt those were not made clear.
The second report is from a different role, Senior Threat Intelligence. That candidate completed five rounds, reached the finalist stage and waited about 2.5 weeks for a decision, with the timeline slipping more than once. They were told an internal candidate was being prioritized. Candidates in similar situations may want to ask the recruiter early about timing and the status of the search. With only two reports, the number of rounds and the total length of the process are not established.
Synthesized from 2 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.
I completed five rounds of interviews for GitLab's Senior Threat Intelligence role and made it to the finalist stage. I received strong feedback after each round I finished, and my recruiter was very kind and kept me in the loop the whole way. The hard part was the waiting. After the final stage I spent about 2.5 weeks waiting for a decision, and the timeline slipped more than once. When I finally heard back, I was told that an internal candidate was being prioritized. Later I learned that one of the people who had interviewed me was the one selected for the role.
Internal promotions happen, and I understand why companies make them. What bothered me was the possibility of a conflict of interest, since someone who helped evaluate my candidacy ended up in the seat. I don't know when that person became a candidate or how their feedback factored into the final decision, so I can't say the outcome was predetermined. Still, five rounds, a long and delayed wait, and that result left me disappointed and questioning how transparent the process was.
My main feedback for GitLab is to keep interviewers and candidates for the same vacancy clearly separated, to communicate changes in hiring direction promptly, and to respect the time applicants put in. Candidates deserve timely decisions and confidence that their assessments are independent.
Prep tip from this candidate
Ask your recruiter early about the decision timeline and whether any internal candidates are in play, since the wait here ran about 2.5 weeks with repeated delays after the final round.
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
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Find the Missing Number | |
| Find Bigrams | |
| Scrambled Tickets | |
| Get Top N Frequent Words | |
| N-gram Dictionary | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Hurdles In Data Projects | |
| Good Grades and Favorite Colors | |
| Rectangle Overlap | |
| LRU Cache 1 | |
| Integer to Roman | |
| The Brackets Problem | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Priority Queue Using Linked List | |
| Level Of Rain Water In 2D Terrain | |
| Basic Regex | |
| Greatest Common Denominator | |
| Target Indices | |
| Nearest Common Ancestor | |
| Longest Increasing Subsequence | |
| Find Duplicate Numbers in a List | |
| Reverse List Starting at Index K | |
| Swap Variables | |
| Target Value Search | |
| Cyclic Detection | |
| Valid Anagram | |
| Dijkstra implementation | |
| Binary Tree Conversion |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports the recruiter screen was the most technical part of their process and more thorough than expected for a recruiter call. It may work as an early filter, so be ready to discuss your security background in concrete, specific terms.
The same candidate reports a high-level conversation with the hiring manager. Questions were mostly introductory and centered on vulnerability disclosure, including walking through a disclosure they had handled. They left unclear on team priorities and PSIRT direction, so prepare your own questions.
A candidate for a Senior Threat Intelligence role reports five rounds in total, reaching the finalist stage. They then waited about 2.5 weeks for a decision, with the timeline slipping more than once, and were told an internal candidate was being prioritized. This is one report for a different role, so later stages for Security Engineer may differ.