My GitLab interview process began with a straightforward screening call with a Sr. GitLab Recruiter. We discussed my salary expectations and GitLab's compensation package, including benefits and RSUs. We also reviewed my experience and the responsibilities of the Engineering Manager, Engineering Productivity role.
The Sr. GitLab Recruiter clearly outlined the four-step interview process, providing details about each stage and sharing the interviewers' LinkedIn profiles. This transparency was appreciated. I promptly provided my availability for the next three weeks via a Calendly link.
However, communication stalled after the initial call. While the Sr. GitLab Recruiter had mentioned observing Indigenous Peoples' Day, I didn't anticipate this would lead to a delay in scheduling. After several weeks without updates, I followed up with the corporate recruiting email address to confirm my availability. Unfortunately, I did not receive a response and ultimately was not moved forward in the process.
This lack of communication was disappointing, especially given the initial clarity and my promptness in providing scheduling options. While my experience with GitLab wasn't positive, I hope others have a smoother process. I've since secured an interview with GitHub and remain optimistic about finding the right opportunity.
Technical Interview (60 minutes):
Design an incident triage system and discuss your approach to balancing immediate and long-term productivity improvements.
The following metrics were computed from 1 interview experience for the GitLab Engineering Manager role in Detroit, Michigan.
GitLab's interview process for their Engineering Manager roles in Detroit, Michigan is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for GitLab's Engineering Manager interview process in Detroit, Michigan.