J'ai postulé en ligne. J'ai passé un entretien chez Canonical (Londres, Angleterre) en avr. 2022
Entretien
This company has one of the strangest interview processes that I have encountered.
The process starts with a fairly lengthy questionnaire that starts by asking what your high-school peers would remember you for. The next stage is a web-based reaction time test in which you have to solve verbal, spatial and arithmetic puzzles as fast as you can, as these are flashed on the screen.
While I can understand the use of an extended statement of purpose, I just don't see how how a speed of reaction test maps to the ability to write any kind of code, leave alone kernel code where the ability to hold a LOT of context in one's head -- multiple threads of control, multiple address spaces in concurrent use - would be far more important than 'speed'.
Questions d'entretien [1]
Question 1
- What would your high school peers remember you for?
... 20+ questions of this nature.
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
Questions d'entretien [1]
Question 1
How would you criticize Canonical's technical decisions that you know of?
J'ai postulé en ligne. J'ai passé un entretien chez Canonical
Entretien
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.
Questions d'entretien [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?
