Canonical's interview process is famously ponderous and this was no exception. Over the course of 5 months I had a written interview (took a day), a psychometric assessment, an introductory video call, a coding exercise, two technical interviews, an HR interview, two management interviews, and another psychometric assessment.
Each stage of the process typically carried a 2-week lag before the next stage could be scheduled, and the process largely shut down between Thanksgiving (US) and New Year's. Some of the discrete steps were thoughtfully implemented and I legit enjoyed the coding exercise, but the amount of time investment simply to get a "no" at the end was frustrating. Every interviewer asked about my experience working with difficult personalities, which I eventually understood to be a veiled reference to the CEO and CTO who are not spoken well of on this site or others like it. I eventually asked one interviewer point blank about the adverse reviews of management, and received a thoughtful answer in which the individual conceded that this is a problem and discussed why some people nonetheless stay at the company a long time.
Tech interview questions were role specific. I got questions on Python proficiency, Linux systems admin competence, and Kubernetes. For one example, I was asked "You have a Linux server that will not boot. You can see the BIOS but there is no bootloader. How do you troubleshoot this?"
The following metrics were computed from 1 interview experience for the Canonical SRE/DevOps Engineer role in Boston, Massachusetts.
Canonical's interview process for their SRE/DevOps Engineer roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Canonical's SRE/DevOps Engineer interview process in Boston, Massachusetts.