Initially, I was impressed with there being a hiring handbook. I read it thoroughly to prepare for my interview. In the end, it wasn't followed at all, so why did I waste my time reviewing something that wasn't going to be followed. - I interviewed for the Engineering Manager, Frontend position. - The interviewer was my peer, another Engineering Manager, Frontend. He asked me some STAR questions which I believed I answered thoroughly and sufficiently. He then went into some technical questions, and before asking me these questions said that he knows I'm not going to spend a lot of time coding so it is ok if I don't know all the answers. I aced the technical questions segment. He then asked me to screen share, and to my surprise asked me to create a LinkedList data structure. I was completely thrown off guard but completed 50% of the code based on his guidance. - After a few days, I was turned down for an interview, and after inquiring, I was told by the recruiter that "they" felt my Frontend skills were not on the level they needed. I have been doing JS for 17+ years. I'm sure if the table was turned, I would be able to stomp the interviewer on some esoteric bit of JS. - The handbook states that only the hiring manager can decline a candidate. So that means that my peer, based on one "gotcha" code example, was able to convince the hiring manager not to continue the interview process without talking with me. - When I finished the coding exercise, I asked if there was any concern that I didn't know how to create a LinkedList off the top of my head and was told that it wasn't an issue and was only used across the company with all engineers as a measuring stick to see where everyone was at. - The handbook stated that data structures would only be asked if that was something I would be doing on the job. I don't like "gotcha" interviews, because they don't accurately show your skillset but rather your ability to actually get lucky and remember that extremely unique bit of code. In the end, you either hired someone who can memorize code just for an interview or someone how got lucky.

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.