Taro Logo

Engineer Interview Experience - Washington, District of Columbia

October 4, 2021
Negative ExperienceNo Offer

Process

The interview process took about 3 weeks.

I interviewed with the hiring manager and 2 other team members on three separate days.

One interviewer was a no-show and did not make my interview.

I had to take off a fourth day and reach out to the hiring manager in an attempt to reschedule because the recruiting POC was out of the office.

I think we had some good discussions, but they decided to go another way, which is fine. However, after taking off 4 days and speaking to 3 people and being flexible through their disorganization, it would have been nice to receive an email from a human being or a quick phone call to let me know the news and to give me some feedback.

I instead just received an automated email from their HR system.

People invest a lot of time and effort into these interview processes, and companies owe a bit more courtesy to candidates who are deep in their interview loops.

The people I spoke to were perfectly nice, and the interview was pleasant enough; I just didn't love the HR process.

Questions

How do you communicate with team members?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the GitLab Engineer role in Washington, District of Columbia.

Success Rate

0%
Pass Rate

GitLab's interview process for their Engineer roles in Washington, District of Columbia is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for GitLab's Engineer interview process in Washington, District of Columbia.

GitLab Work Experiences