Canonical logo

Canonical Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 340 interview experiences · FREE TO READ

4.3 Rounds average
Average Typical difficulty
16.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Canonical.

Showing 3 of 340
Canonical logo
Canonical

Software Engineer

Engineering · half a year ago

Entry Average Positive experience No offer 5 rounds
Interview process
Technical screen Take home Technical screen Technical screen Technical screen
Interview formats
Technical Coding Technical

So, first we did a written interview, then a psychometric assessment, followed by a Python coding test. After that, there were two more interviews, the first one was an early stage interview where we talked about software engineering and a project showcase, and the second one was also an early stage interview focusing on Linux and Open Source.

Confirmed questions1 question
  • Can you tell me about your experience using and working with Linux Systems?
Canonical logo
Canonical

Software Engineer

Engineering · nearly a year ago

Mid Easy Negative experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Technical Other

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.

Confirmed questions2 questions
  • I was asked to write a lengthy essay covering my high school and college experiences.
  • Following the essay, I had to complete the GIA test, which involved a letter comparison task using a non-standard font.
Canonical logo
Canonical

Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Technical screen Take home Recruiter call Background check
Interview formats
Technical Coding Behavioral

The interview process kicked off on June 25th, 2025, beginning with a written test, a timed technical assessment covering the ISBN check digit algorithm and another problem, and the GIA. There are online resources to help practice these, making them manageable. Following that, I had three interviews with different team members, all of which were positive experiences. The engineers seem to enjoy their work, although they did express dissatisfaction with the interview process's duration. They inquired about my Python assessment and asked general Python questions, such as about data types and function decorators, as well as Linux system concepts like the distinction between processes and threads. A personality assessment, lasting about 8 minutes, was also part of the process. Subsequently, I had a conversation with a Talent Scientist to review my resume, gain insights into Canonical, and discuss salary expectations. The talent scientist prompted me for my salary expectations, and I mentioned it was difficult to provide a precise figure given the broad job title of "Senior/Staff/Principal Engineer." She pressed for an estimate, so I provided a range for each potential role based on my experience, roughly $230k to $275k. She then asked for my current salary, which is illegal in my state. I declined to answer, so she asked for my minimum expected salary, which I stated as $230k, representing a significant raise. She indicated that meeting this figure might be challenging but thanked me for my time. Five days later, I received a rejection email, leading me to believe the salary expectations were too high. In total, I dedicated approximately 10-15 hours to the interview process, only to receive an automated rejection despite passing all prior stages, with no feedback provided. The interview process has a poor reputation, but in my opinion, it's not excessively difficult, just time-consuming. It's advisable to only invest time in applying if you are genuinely interested in working for Canonical or do not mind the extended application period. While the individuals I interacted with were great, I question the effectiveness of the interview process itself. Additionally, be aware of their bring-your-own-laptop policy and the requirement for at least two international trips per year for in-person meetups, which could be a pro or con depending on your preferences.

Confirmed questions5 questions
  • Could you write a Python function to determine if a given string represents a valid ISBN?
  • Can you explain how the ISBN check digit algorithm works?
  • What are the different data types in Python?

Canonical Software Engineer Interview Questions

Quoted word for word from Canonical interview reports.

If you noticed you were low on disk space, what commands or tools would you use to find out what's taking up the space? Also, what tools would help you discover which programs are using up too many resources?

Read reports

What are your thoughts on documentation for large software projects? What should teams do, and what are some excellent examples of open source documentation?

Read reports

What was your ranking in your final year of high school for your home language? Were you a top student, and what is the basis for that claim?

Read reports

A customer wants a new product feature and reaches out to you. You don't have time to include it in the upcoming release. What's your approach to handling this request?

Read reports

Describe the kind of high school student you were. Beyond academics, what were your interests and hobbies? What would your high school friends recall about you?

Read report

What are your thoughts on Canonical's mission? What aspects of the company's purpose and goals appeal to you the most? What do you perceive as risks or downsides?

Read report

In your final year of high school, what was your ranking in mathematics? Were you a top student, and what leads you to say that?

Read report

What kind of high school student were you? What were your interests and hobbies outside of academics? What would your high school peers remember you for?

Read report

Regarding high school, how well did you do in math and physical sciences? What were your best hard science subjects, and what was your class ranking?

Read report

Formats, difficulty and experience

Across all 340 Canonical interview reports.

Interview formats

Technical 36.9%
Behavioral 26.2%
Coding 22%
Other 9.2%
Presentation 3.3%

Interview difficulty

Easy 11.8%
Average 63.2%
Difficult 25%

Candidate experience

Negative 59.7%
Neutral 24.1%
Positive 16.2%