Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en GitLab en mar 2019
Entrevista
I applied on the careers page and attached my CV for them to review. They replied within a week with an email containing a link to a form, for me to fill in. The form contained around ten open-ended questions like:
- Why and when would you use a JavaScript framework?
- Can you explain what XSS is and how can it be prevented?
After four days passed, we scheduled a Zoom interview.
The interview started with general questioning from the Gitlab handbook. We spoke about management styles and some simple STAR based questions. At the end of the interview, the interviewer casually mentioned that because I have worked for a couple of companies for less than two years that I will now be rejected. They explained that it is company policy not to hire anymore that has previously worked for a company for less than two years. I said that was a shame and the call ended.
It would have wasted less time to tell me right at the beginning. A simple "Hey! You look like a good candidate, but we can't hire anyone that has worked for a company for less than two years. Sorry."
Envié una solicitud electrónica. El proceso duró 1 día. Acudí a una entrevista en GitLab (Detroit, MI) en oct 2024
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Technical Interview (60 minutes): Design an incident triage system and discuss your approach to balancing immediate and long-term productivity improvements.
Very good process, clear communications. Nice feedback in the end. Everyone is well prepared for the interview, with a lot of empathy and positive vibes. The hiring manager was pretty skilled and experienced. Gave me a lot of excellent and actionable development tips.
Preguntas de entrevista [1]
Pregunta 1
Lots of good questions on tech process organization
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en GitLab (Londres, Inglaterra) en feb 2022
Entrevista
Interview was four rounds, four interviews total not counting the recruiter phone screen which you can fail. Interviews were:
Managerial Behavioral
Reverse System Design - talk in depth about a project or two you've done in the past
PM chat - interview with a product manager
Director interview - interview with an engineering director