Taro Logo

Engineering Manager Interview Experience - Remote, Oregon

July 1, 2018
Negative ExperienceNo Offer

Process

The process took around 1.5 months. It included two screening calls with Directors of Engineering. Then, I had a management interview with a Director. After that, I was invited for two more interviews: one with a peer Engineering Manager and another with a Tech Lead.

I really enjoyed every talk I had with the Director. The rest of the interviews were just loose chats.

I was also asked to provide three referrals. A few days later, I received a rejection letter. I asked for some feedback and only got a quick message stating I "must be more clear with examples to asked questions." Fair enough. However, the way it was provided says a lot about a lack of good feedback culture.

The bad thing was also that I had to remind recruiters at every stage of the recruitment process about myself. The whole process was super slow and without enough communication. This was weird because I was used to the rule of overcommunication in remote companies.

Overall, I regret I invested so much time and energy.

Questions

Why did you become a manager?

What is your biggest achievement in your career?

What are you proud of?

What is the hardest thing about being a manager?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the GitLab Engineering Manager role in Remote, Oregon.

Success Rate

0%
Pass Rate

GitLab's interview process for their Engineering Manager roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for GitLab's Engineering Manager interview process in Remote, Oregon.

GitLab Work Experiences