GitLab · Primly Community

GitLab behavioral interview questions and values: what actually came up in my loop

frontend_fran · 4 replies

i applied for a senior engineering manager role at GitLab and made it to the final round earlier this spring. sharing the behavioral prep stuff because i think it's underrated for GitLab specifically.

first thing to know: GitLab has 10+ company values that they take seriously. the full list is public in their handbook (which is literally public online). they will ask behavioral questions that map to specific values. this isn't just culture-fit fluff, they're actually mapping your answers.

some of the values questions that came up across my three behavioral interviews: 'tell me about a time you had to make a decision with incomplete information and couldn't wait for consensus' (this is their 'bias for action' / 'results' value) 'describe a situation where you had a strong opinion but changed your mind based on new data' (transparency + iteration) 'how have you worked with a teammate in a completely different time zone where async was the only option?' (remote-first collaboration -- this one is almost guaranteed to come up) 'tell me about something you shipped that you later realized was a mistake. what did you do?' (ownership / blameless culture) 'when did you have to push back on a product decision even when it was unpopular?' (directness)

the async angle is real. GitLab is genuinely all-remote and async-first. every behavioral round touched on how you handle communication when you can't just tap someone on the shoulder. if your examples are all 'i walked over to their desk and we figured it out,' you need different examples.

prep tip: read the GitLab Values page + the section on 'collaboration' in their handbook before the loop. it's not a long read and it telegraphs exactly what they're looking for. map your STAR stories to specific values before you go in. i had a spreadsheet with columns: value, situation, outcome. it helped a lot.

the tone in my behavioral rounds was genuinely warm and conversational, not interrogative. the interviewers volunteered their own examples when they asked questions, which made it feel more like a real discussion. that was refreshing.

4 replies

director_dee

the handbook-mapped behavioral prep is the move. i've interviewed at GitLab twice (got an offer the second time) and the first time i just did generic STAR prep. bombed the 'remote collaboration' question because all my examples were hybrid. second time i had specific async communication stories and it clicked immediately.

ops_omar

did they ask about metrics or results quantification? i always struggle with 'tell me about a decision with incomplete data' because my work is more qualitative ops stuff. wondering if that's a dealbreaker.

firsttime_mgr

for manager roles they definitely care about results but i don't think you need exact revenue numbers or p99 latency stats. they seemed fine with 'reduced time-to-close by roughly 30%' or 'team shipped 3 weeks ahead of plan.' directional clarity matters more than precise metrics in my read.

apm_aisha

saving this whole thread. the GitLab handbook is genuinely one of the most useful interview prep resources for any GitLab role. people sleep on it.