🔧 My journey to GitLab
Nachrichtenbereich: 🔧 Programmierung
🔗 Quelle: dev.to
In this article, I'll share my interview process at GitLab
GitLab Inc. is an open-core company that operates GitLab, a DevOps software package that can develop, secure, and operate software. GitLab includes a distributed version control based on Git, including features such as access control, bug tracking, software feature requests, task management, and wikis for every project, as well as snippets.
Intro 😃
I am Pratik Singh, a DevOps and Go developer.
Here is my Twitter and GitHub
I go by the name kitarp29 online.
My story ✒️
Being in DevOps, GitHub, and GitLab both have been on my bucket list of companies. I was lucky enough to work with GitHub as an extern back in 2022. I was very close to getting into GitLab back in 2022. Why I didn't get into GitLab at that time is a whole other story. But you can understand the obsession grew stronger.
I was happy at my job at Nasdaq as a Senior Software Developer. I started to look for a completely remote job, because of my family conditions. GitLab was one of the companies I started to apply for.
The whole interview process was spread across 2 months.
Interview Process 👨🏻💻
Before I get started, there is already a resource from GitLab for this: Here
I think this answers most of the questions one might have. I will try to just add my personal experience to it.
Let's dig deeper!
1. Application 📝
I am not sure if I found the job application on Linkedin Jobs or from their career page. I follow the red car theory so it's harder to keep track. The form takes barely 5 minutes to fill. But I tried to apply for only relevant jobs.
GitLab career page: Here
2. Screening round 🧐
This was a 30-minute call with the Recruiter. It was a call where we both exchanged basic information about my profile and the job role. I was briefed about the interview process, the compensation, and my role in detail. I don't think it's an elimination unless you have diametrically opposite opinions.
3. Technical Round 🤓
This was one of the longest and in my opinion the second-hardest round of the entire process. It is 90 minutes call. After the initial chitchat, I was briefed about the project I'll be working on. I was told about 2 different tasks. I was made aware of the task and asked to go through the docs and give a possible solution on the spot. For each task, I was given ~45 mins. The interviewers were there to answer my questions and nudged me in the right direction. I was not supposed to code within the call but explain my approach.
Post the call, I was assigned both issues and was asked to complete within 3 days. The interviewers were there to help me with the comments on the task.
Luckily I was able to complete one of the tasks flawlessly. But for the other task, I had made the code changes that seemed correct. Unfortunately, it didn't compile on my system. I worked enough on it and the interviewers were satisfied with my work.
4. Manager Round 👩🏻💼
My manager is the sweetest interviewer I have ever dealt with. It was a 60-minute call. She made me feel comfortable at the start. After the basic intro, we went deep into my work. She asked me about my work and my internships. Other than the tech questions.
We also started to discuss behavioural questions. After her round of questions, it was my turn to ask questions. I asked about my day-to-day responsibilities, my team, and opportunities. I was confident that I had cleared this round.
5. Tech/Behavioural round 🫡
This is a 60-minute call. This was a call with two of my other teammates. This round was both of tech and behavioural rounds. It was more about how I work with my team. One mistake I kept making was addressing all my answers as "We". As in what we did as a team or handled some situations as a team. Although they were interested in learning more about me. I don't think there is much preparations needed for it, be honest and communicate clearly.
Read on STAR approach to answer such questions.
6. Leadership round 🙄
This was the hardest round in my opinion. It was a 60-minute call. The interviewer started with a technical chitchat about my work. He went through my resume and was curious about my projects. After a couple of behavioural and Agile-related questions, the hardest part started!
Yes, it was the system design part. I won't be discussing the questions itself. But man, it was so open-ended questions! I guess it was the first call I was silent for more than 5 minutes thinking of a solution. I was terrified that I would ever clear this round!
Under the circumstances of my life, I was not able to prepare for it well. But I strongly urge you to prepare for it well.
My sister had just given birth to my nephew a few days before this call.
7. HR Round 🖊️
It was the point I was assured my team wanted to recruit me. Now it was all discussions about the compensation and references.
The night I got this email. I recall I was with my Mom and sister. We all were SO happy! 🥹
8. References 🫱🏻🫲🏼
One has to provide three references, at least one being your manager in one of your past companies. This took a week.
Hired! 😇
My suggestions
- Keep applying. I have been applying since 2022. Once I got very close to an offer. But after 2 years I finally got in!
- Be thorough with your resume.
- Practice STAR pattern-based questions.
- Important to be good at System Design questions.
- Each round is almost 1 to 2 weeks apart, so it's important to lower your anxiety. My suggestion, go on trips in the meantime.
I traveled to Seattle during this duration
My friends and I took a road trip to Wayanad
If you liked this content you can follow me here or on Twitter at kitarp29 for more!
Thanks for reading my article :)
...
🕵️ Medium CVE-2020-13306: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2020-10978: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2021-22185: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-13326: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-19255: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2018-19575: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2019-10114: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-13286: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-12444: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2022-2185: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-26412: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2020-7974: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-6785: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2019-9485: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2018-14603: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-13301: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-10975: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2021-22176: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-13305: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-12434: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-19309: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2018-19576: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2019-10114: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2020-13281: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-12442: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2022-1983: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2020-26408: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Medium CVE-2020-7978: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken
🕵️ Low CVE-2019-6789: Gitlab Gitlab
📈 17.56 Punkte
🕵️ Sicherheitslücken