GitLab Application Support Engineer Interview Questions
& Process

You get to pick your own interview schedule, which is nice. It went through a bunch of different parts, maybe too many? I got to the second to last one, and the team seemed to like me and said they'd approve me. But then, three days later, I was rejected. Not sure why. It felt like a big waste of time with about 6 stages.

So after I sent in my resume, they hit me with an assessment. It had me making some bash scripts, a Git commit graph thing, I had to write a blog style "how to" guide, and then there was this personal question. After I got that submitted, I talked to someone from HR. It was pretty standard stuff, you know, about my background and what I've done, and they covered the job details, pay, and benefits. Towards the end, they threw a couple of Linux command questions at me, which honestly caught me off guard and I got a bit nervous, but they were actually super easy commands. Next up is a real technical interview with some team members, and then two more interviews that are more behavioral. I'm only at the HR interview stage right now, so I'll update if I hear back about the next steps.

It was a mess. The technical interviewer was late, and the test environment wasn't working right. The interviewer even said it was his first time doing a technical interview. The tests themselves were easy, like fixing Apache and Nginx issues on GitLab. But the questions were badly explained, unclear, and missing info. I got them all right, but it took a while because I didn't understand what he wanted at first. I had to ask him to re-explain each time. I was rejected because of a 'GAP in technical skills', but I don't think it was fair. Other candidates might have had a more experienced interviewer who could explain things better. I'd rather have a technical writing test to avoid these misunderstandings, or at least have the same interviewer for everyone.