Taro Logo

Frontend Engineer Interview Experience - United States

March 1, 2020
Negative ExperienceNo Offer

Process

The first interview was a behavioral screening interview, which was pretty standard.

For the technical interview, I was given a small merge request to review with a few changes. There were maybe 30 lines of SCSS, 10 lines of Javascript, and 30 lines of HTML/Haml. The instructions merely told me to look over the requirements and suggest some changes to the code, and to download the code and make sure I could run it locally. I saw a few style and performance issues, but overall the MR appeared to adequately implement the changes suggested in the requirements. I left a comment with a few of the things I noticed.

At the interview, I showed the interviewer my comments with a few changes I had come up with. He immediately told me I hadn't left enough suggested changes in my comments. The interviewer seemed overall uninterested in what I had to say, even when I came up with some more suggestions of things that could be changed. He seemed eager to end the interview and ended it after only a few minutes. I didn't even get a chance to write one line of code.

I spent 4-5 hours preparing for this interview, reading over all the email and materials, setting up the dependencies, running the code locally, and went over the MR several times to try and find any changes to be made to help it more closely match the requirements. There really wasn't a lot to go off of, and the code appeared to function correctly according to the requirements; it did what the requirements said it needed to do.

I set up a call with the recruiter to give feedback on my experience, and she basically invalidated my feedback. When I told her that it wasn't clear to me that I would be coming up with everything to do during the interview on my own, and that the changes I suggested would be the only content in the interview, she told me that it was very clear in her opinion what had to be done during the interview in the email.

I got the sense that the position was no longer available, but that the staff wasn't being transparent with me about this and was giving me short shrift.

I received a polite email a few weeks later stating that the position was indeed no longer available. It's disappointing to have an experience like this at a company that boasts transparency as one of its core values. I would have preferred for the interviewers to tell me up front that the position was no longer available instead of wasting my time and acting like I had somehow failed the interview.

Questions

What are the changes you suggested and how would you implement them?

Was this helpful?

Interview Statistics

The following metrics were computed from 8 interview experiences for the GitLab Frontend Engineer role in United States.

Success Rate

25%
Pass Rate

GitLab's interview process for their Frontend Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive38%
Neutral25%
Negative38%

Candidates reported having mixed feelings for GitLab's Frontend Engineer interview process in United States.

GitLab Work Experiences