Slow. An interview step every 2 weeks, 11 interview steps in total. From writing an essay, doing an IQ test, psychometric test, take-home test, tech interviews, culture..At each step I had to describe my background, story, and experience from scratch, as it was evident they did not read my CV, or the essay. First 2-3 culture "generic" interviews were with random people who did not even know the role I was interviewing for.. so totally useless. Moreover all their job ads mention lots of different techs, while the real role does not.
You might have applied for a role mentioning cloud DevOps and end up interviewing for a role all about packaging software for their APT repos and Snaps.I interviewed for 2 different roles that both mentioned open source, while the truth I discovered during the tech interview is that I would work on closed source projectsTech interview was random. Random questions, and they want you to have experience in their tech stack and frameworks (do not apply for a role using Flask if you used different frameworks).In the end I was offered a low salary, not on par with other remote companies, and the minimum amount of PTO possible. Like the absolute minimum that is legal in your country.
(I am European, and they offered 20 days while I am getting 35 now).It is possible to negotiate and you should do so, especially the PTO
Why do you want to work here?
Do you have experience working in a remote environment?
The following metrics were computed from 5 interview experiences for the Canonical Software Engineer role in Italy.
Canonical's interview process for their Software Engineer roles in Italy is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Canonical's Software Engineer interview process in Italy.