Taro Logo

Software Engineer Interview Experience - Netherlands

August 1, 2021
Negative ExperienceNo Offer

Process

The interview process was quite long:

  • The first stage was a written interview, which was approximately 1 page and was a cover letter like assignment with areas that should be addressed.
  • The second stage was intelligence and personality tests.
  • The third stage was several interviews with people who don't work in the same team in which the role is open (6 different calls in my case), and these are called cross-team interviews.
  • The fourth stage was a technical assessment, writing a command line tool in python.
  • The final stage was an interview with the hiring manager.

The cross-team interviews are OK, but always follow the same pattern with the introductions and the same questions over and over again so it's tiring after a while. You don't really get any useful info about the role, as the interviewers don't work in the same team. It could be done in one call with all the people, but for some reason I only talked with one person at a time, which makes the process incredibly long.

The technical assessment was quite easy, the instruction was to finish it in 24 hours once I read the task description (that's a bit weird for a programming assignment but whatever). I did this midway through the cross-team interviews and we didn't really discuss my solution which was a disappointment, as it seemed like they didn't really checked it at all.

Finally after a month of interviewing I had a call with the hiring manager. At this point I was quite burnt out by the whole process. I didn't really prepare for the interview as I thought the hard part was already over (which was obviously a huge mistake).

The manager told me that they want someone with more seniority for this role and he has something else in his mind for me (which would have been nice to clarify in the beginning...). Went through the same stuff but dived into some more technical topics which was not going well because I didn't prepare.

Got rejected after the interview which was understandable based on my performance on the hiring manager's interview. The problem is, this interview should have been the first from the bunch, and the rest can be done in one bigger interview when there are several people are present.

The entire hiring process is severely bad, it wastes everyone's time. They emphasize in the beginning they do things a bit differently than others and engineers conduct these interview. Well, there is a reason why HR departments exist, they can do these things much better or at least they should oversee the process. It was an awful experience.

Fortunately got an offer from an other company after two interviews and a technical assignment.

Questions

  • talk about previous experiences
  • write a CLI tool in Python

technical questions from hiring manager:

  • what is GIL in Python
  • describe kubernetes components, what are the advantages of using k8s

Was this helpful?

Interview Statistics

The following metrics were computed from 5 interview experiences for the Canonical Software Engineer role in Netherlands.

Success Rate

0%
Pass Rate

Canonical's interview process for their Software Engineer roles in Netherlands is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral20%
Negative80%

Candidates reported having very negative feelings for Canonical's Software Engineer interview process in Netherlands.

Canonical Work Experiences