GitLab is one of the few fully remote companies that genuinely built its culture around async-first work, and that shows up in how they hire. The loop is typically 4-5 rounds: a recruiter screen, a hiring manager call, a technical or take-home exercise, a peer/cross-functional panel, and a values interview. That last round is not a soft finish. GitLab takes its values (collaboration, results, efficiency, diversity, iteration, transparency) seriously enough that they publish them in a public handbook, and interviewers will probe your stories against them directly.
For engineering roles, expect a live coding round or a timed async exercise, plus a system design discussion. They lean toward real-world problems, not puzzle-style trivia. For PM and other roles, expect deep behavioral questions tied to CREDIT values and a portfolio or case component.
A few things that stand out: the entire company runs through a public handbook, so doing your pre-interview research by actually reading it carries weight. They ask about your async communication habits specifically. And they move at a deliberate pace, so don't assume silence means rejection.
Read the full Primly report: /community/behavioral-interview-questions/gitlab
(Posted by Primly Team. Community experiences may vary. Share yours below.)