Canonical Interview Questions
& Process

We're looking for experience in customer success, but we also want to get a feel for your academic background and strengths. Tell us about your performance in high school math, sciences, and computing, your strengths, what you enjoyed, and how you ranked. What were you like as a high school student? What did you do outside of schoolwork? What would your friends say they remember you for? We also want to know about your performance in languages and arts in high school, your strongest subjects, and your ranking. Share any exceptional achievements from high school. If you've graduated or are about to graduate recently (last 1-2 years), tell us about your degree, university choice, why you chose it, which courses you excelled in, your ranking, and what you did outside of classes. What did you achieve at university that stands out? We're also keen to understand your interest in customer success in tech, your view on best practices for SAAS products, how you measure success for enterprise products, what customer would be a career highlight, and what innovations you'd bring to customer success. Additionally, describe your experience with technology projects, software, operating systems, development environments, languages, and databases. Share your thoughts on enterprise open source. Finally, we'd like to know who Canonical's competitors are and how they can be more competitive, why you want to work for Canonical, and which of our products and services you're most interested in.

The competency-based questions felt scripted and stunted, not allowing for real strategic dialogue. The atmosphere is exclusive, with a noticeable internal self-importance that can seem pretentious. The conversations felt more like administrative checkboxes than actual high-level talent assessment. Their interview structure needs to move beyond rigid, formulaic questions; it currently feels designed to exclude rather than assess true capability. The initial written interview was very time-consuming and wasn't even mentioned in the in-person meetings. The Thomas international test was quite simple.

The hiring journey kicked off with a review of my application. Then came an assessment phase, which was pretty comprehensive. It included a written interview, a JavaScript technical challenge, and a psychometric test. The tech task was all about frontend stuff, checking how I handle problems, my JavaScript basics, and if I can stick to instructions. I did it on my own machine, and it had clear guides and auto-tests. It felt like real work, not just theory. The psychometric part was timed and looked at thinking skills. The instructions were clear, and the system was easy to navigate. They were good with communication, always professional and quick to respond. Scheduling was a breeze using an online calendar, and they were cool about adjusting times for different zones. All in all, it was a solid, well-run process that felt like it represented actual frontend engineering tasks.

The interview process is a huge waste of time and extremely inefficient. It's very impersonable and they use an old-fashioned "aptitude test" that they weigh heavily. The test includes a letter comparison using a weird font where the lowercase 'g' looks like a 'q'. The initial document took me about 4 hours to write. The contact person doesn't respond, so I doubt they get any emails. They aim to reduce bias but have created an equally biased process. Using the GIA this way is misguided; it should be an early step to avoid wasting time on a document no one reads.