After I submitted the application on their website, they sent me a series of questions and asked me to compose an essay to answer them.
They said they expect you to spend 1-2 hours to finish it. While most of the questions are quite general, like who are the competitors of Canonical? and how do you think Canonical can win? something like that. And some questions are about how you did in college or high school. I am not a native speaker, so it took me much more time to finish it.
Then they sent you an aptitude test. I don't think it's like an intelligence test, it's more like testing your speed on some specific kind of questions. Finally, I got their rejection letter. I never encountered this kind of interview where the interviewer turns you down without asking any technical questions.
Are you involved in open source software? Describe any significant contributions to open source (with links where possible), if any. What do you think are the key ingredients of a successful open source project? Why do you most want to work for Canonical? Which other companies are building the sort of products you would like to work on?
Which companies have the most interesting approach to devops and site reliability engineering? What do you think could raise the bar for site reliability engineering, globally? What do you think Canonical needs to improve in its engineering and products? Who do you think are key competitors to Canonical? How do you think Canonical should plan to win that race?
The following metrics were computed from 3 interview experiences for the Canonical Software Engineer role in Taipei.
Canonical's interview process for their Software Engineer roles in Taipei is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Canonical's Software Engineer interview process in Taipei.