Software Engineer applicants have rated the interview process at Canonical with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 16% positive. To compare, the company-average is 14.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 53 days to get hired, when considering 155 user submitted interviews for this role. To compare, the hiring process at Canonical overall takes an average of 51 days.
Common stages of the interview process at Canonical as a Software Engineer according to 155 Glassdoor interviews include:
Personality test: 19%
Skills test: 19%
IQ intelligence test: 17%
One on one interview: 16%
Phone interview: 12%
Other: 7%
Background check: 3%
Presentation: 3%
Group panel interview: 2%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
Received an E-Mail with various steps, first I had to transfer my whole CV into a weird webform. Second some online assessment. Asking questions on those emails do not prompt any answer by the recruiter.
Interview questions [1]
Question 1
Beginning in your high school years, through university and into your career, what have you done that you consider exceptional? What makes for an ideal devops engineering colleague? What about your personality and interests makes you a great potential member of this team? What are the key trends in infra-as-code? What could be improved in the state of the art of devops? How familiar are you with Linux operations - including networking and storage - and how did you gain this experience? Describe your Python software engineering skill, and how did you gain this experience? Describe your experience with container and cloud technologies (Docker, LXD, Kubernetes, Openstack, Ceph, Public Cloud, etc) Which security best practices do you consider important? Which performance and scaling best practices do you consider important? Which documentation best practices do you consider important? Which software quality best practices do you consider important? How are you involved in Open Source software? Why you most want to work for Canonical? What about Canonical interests you the most? How do you think Canonical could improve Ubuntu and its cloud offerings? What do you think are the most significant strengths of Canonical's competitors?
Brutally long and difficult. They take their time so only apply if you have time and are dedicated to open source tech.
That being said they are very communicative so if you have any questions its not such a black box.
Interview questions [1]
Question 1
They'll ask for specific niche aspects of coding languages to check if you actually use them day to day.
It's an extremely long process that includes standardized tests, take home assignments, and several rounds of interviews. It was at least 5 rounds long and you interview across different teams.
I applied through other source. I interviewed at Canonical (London, England)
Interview
They have a really long, tiring interview process. The first round was a written interview where I had to answer like 15 questions. Then a coding interview with 1 hour time that I could do anytime for 2 weeks. Then I had to take a personality test and they totally ghosted me.