Initial stage was a written interview and two tests. The written interview is very long, and does ask some odd questions like how you did in high school (and requires proof). Everyone does it, regardless of seniority. If you find the written interview annoying you are best to just not continue through the process, as it's a pretty good look into the vibe of the rest of the process. You are told that your answers on the written interview will come up in interviews, but in both interviews I had it seemed like the interviewer hadn't even read it.
First real stage was two interviews, each with a current engineer. First was with a newer engineer -- was good, just discussion about my experiences and things I've worked on, no LeetCode/whiteboarding or anything else of the sort. Second was titled "Linux & Open Source", also had no LeetCode/whiteboarding. Was with a much higher engineer, questions were looking for a certain answer, but were phrased too open-ended to communicate that.
The notes online about their slow process are very true. I got assigned a hiring manager, didn't hear anything for almost a month, then assigned another and again didn't hear for two weeks. In the second case it turned out that an automated email to schedule hadn't gone through -- they have an online portal for your application, so I'm not sure why that doesn't note that you should've received something. The hiring managers are not dedicated hiring managers, rather are regular employees with presumably regular work, so you're asked not to contact them unless really necessary, so the complete radio silence just goes on.
The following metrics were computed from 1 interview experience for the Canonical Software Engineer role in Kalamazoo, Michigan.
Canonical's interview process for their Software Engineer roles in Kalamazoo, Michigan is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Canonical's Software Engineer interview process in Kalamazoo, Michigan.