A long written interview, followed by 3 schedulled calls. A long and tiring process to ultimately get ghosted. The more technical interviews (regarding OS) was quite a pleasant and enjoyable experience, but the python interview was heavily focused on trick questions and unneccessary details.
Detailed but long.
At first they may ask you questions concerning educational background eg highschool and uni. I found the highschool bit to be odd.
Later parts of the interview are moderately technical and straightfoward.
Having contributed to canonical open-src projects is a big plus
Interview questions [1]
Question 1
How would you criticize Canonical's technical decisions that you know of?
Il faul écrire un article sur toi-même, en répondant dizaines de questions sur les expériences, meme si elles sont déjà dans ton CV. Il y a aussi un test de caractéristique, qui est trop long et sans sens.
Interview questions [1]
Question 1
What kinds of software projects have you worked on before? Which operating systems, development environments, languages, databases? That is not a checklist, just some suggestions of what to describe you have worked with. Would you describe yourself as a high quality coder? Why? Would you describe yourself as an architect of resilient software? If so, why, and in which sorts of applications? What software products have you yourself lead which shipped many releases to multiple customers? What was your role?
