Taro Logo

Solutions Architect Interview Experience - New Zealand

September 17, 2019
Negative ExperienceNo Offer

Process

Applied and didn't hear back for 7 months.

Got an automated email out of the blue asking me to book a timeslot for a first interview. Booked in and didn't hear anything until the scheduled time.

Jumped on the call and the person was very friendly. But I let them know that this was the first I had heard from them after applying 7 months ago, and they acted surprised and asked if I had interviewed and been turned down, etc. But no, just no contact (seems the norm reading other reviews). Felt like the person I was talking to had been given my details 10 minutes before.

Interview was more just a chat and get-to-know-you session. But they did ask about tech stacks that are very uncommon here (Ruby, for example). Given the role was a pre-sales role (not working on the core product), it was a little strange. It was clear that no one had read my CV, as they would ask about my experience level with particular tech that I didn't claim to have any knowledge in.

A few days later, I got an automated email from a no-reply address with a "thanks but no thanks."

Questions

Experience levels with Linux, Ruby, Docker, etc.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the GitLab Solutions Architect role in New Zealand.

Success Rate

0%
Pass Rate

GitLab's interview process for their Solutions Architect roles in New Zealand is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for GitLab's Solutions Architect interview process in New Zealand.

GitLab Work Experiences