Canonical interview, decoded.
Updated · Sources at the end
Canonical asks for more writing than almost any other tech employer. Before any interview, candidates answer a written interview tailored to the job, and reported versions run to around 40 questions and 15 to 21 pages. It asks how you ranked in mathematics and in your native language at high school, and for your university result with the grading system, whatever your seniority. A five-part aptitude test follows, then three technical interviews, a talent interview and a late stage with senior people. The company says the whole thing takes about three months on average.
Canonical publishes Ubuntu and sells support and services around it. It has run as a fully distributed company for over 20 years, and its engineers work from home across the world, meeting in person a few times a year.
Free · 2 minutes · no account
The questions for your exact Canonical role and level.
Who Canonical hires
This guide follows the software engineer path, from graduates to senior engineers. Canonical says it values academic results at every level, and its blog adds that nearly everyone it hires has a good degree, while also saying it has hired outstanding people without one. Graduates who finished their first degree in 2025 or 2026 can apply to a fast-track process. Roles are globally remote, but every employee is asked to meet in person two to four times a year at company events that last one to two weeks.
Not sure your resume shows the level Canonical hires at? Check it with a free resume review.
What is the Canonical interview process?
Canonical describes its process on its careers site in three stages: assessment, interviews, and a late stage leading to an offer. It says the process takes around three months on average from application to offer, for every level from graduate to VP. The details below mark what the company says and what candidates report; candidates describe more interviews than the official outline, so plan for eight or more conversations.
7 roundsApplication questions · Written interview · Psychometric test · Technical assessment · Technical interviews · Talent interview · Late stage and offerSee each roundHide
Questions about your academic record come first. The graduate job ad asks how you did in mathematics and in your native language at high school, with reference to national or state rankings, and for your bachelor's result with the grading system used. A domain expert in the business reviews the application, and the company says people, not automated systems, read every CV.
A long set of written questions tailored to the job, uploaded as a PDF and graded anonymously, typically by two domain experts. One candidate reports 42 questions and about 15 pages, another 38 questions and 21 pages. Questions cover your education, why Canonical, open source work, and technical topics for the role, such as monolithic against microservice architecture.
The General Intelligence Assessment (GIA), sent by Canonical's assessment partner Thomas International: five parts measuring aptitude, problem solving and speed of learning. The company says it is not an IQ test but a measure of trainability. Every applicant takes it.
Some roles add a test of domain skills, graded by a domain expert and explored in the later interviews. Candidates report a two-hour Python test on DevSkiller, a 90-minute test of coding problems and, for a security role, a three-part take-home expected to take about three hours.
The company says three interviews focus on technical and domain skills. Candidates list software architecture and engineering, Linux system skills, and a deep dive into the domain of the job, such as microservices or security.
A conversation about your career motivations and path, after a 10-minute Personality Profile Analysis on your working style. The company says pay discussions start here. One candidate describes answering in the STAR format.
You meet your potential manager, the hiring lead and other senior stakeholders. The company says candidates for management or leadership roles also meet the CEO, Mark Shuttleworth, and one security engineer reports a final interview with him as well. The company's FAQ says the hiring lead runs the process and is ultimately the decision maker, and communicates the offer.
The Canonical written interview and aptitude test
What they ask and how to prepareMost of the effort in Canonical's process goes into two things before any interview: a long written interview and an aptitude test. Candidates report spending many hours on the written part; one estimated around 20 hours for the whole process including preparation. Both come early, so they decide whether you reach an engineer at all.
5 reported problemsSee them and how to solve themHide
- School and university results: Expect to state how you ranked in mathematics and in your native language at high school, with the scoring system, and your degree result with its grading scale. Find the documents before you start, and answer exactly. Candidates report being asked for proof later.
- The long written answers: Candidates report 38 to 42 questions and 15 to 21 pages. Write each answer around one specific example with a result, keep your own part exact, and reread the job ad so the technical answers match the role. Answer in question-and-answer form, which the company says is easiest to review, and leave out GitHub, LinkedIn or anything else that identifies you, because the PDF is graded anonymously. You have 14 days, so budget several evenings.
- The aptitude test (GIA): Canonical's FAQ says the email comes from its assessment partner, Thomas International. The GIA has five short timed parts: reasoning, perceptual speed, number speed and accuracy, word meaning and spatial visualisation, scored as a percentile against a norm group. It measures speed of learning, so practise the format with Thomas's free example booklet until it feels familiar, then take it rested on a reliable connection: the company resends it only for a fault on the platform, not for problems with your device or connection. You can request your report from the candidate dashboard afterwards.
- The Personality Profile Analysis: A 10-minute questionnaire on your working style before the talent interview. There is no right answer; answer consistently and honestly, because the talent interview picks up on it.
- No online aids, no AI: The company asks candidates to present their ideas without online aids, and its FAQ says using AI tools anywhere in the process is strictly forbidden and that every written or spoken answer will need clarifying later. Recording any part of the process gets you disqualified. Write the answers yourself, and expect interviewers to ask about them.
Candidates who published their experience describe a long process with little feedback at the end, and Glassdoor ratings of the interview experience are low. Weigh the time against your other applications, and keep them going in parallel.
The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Canonical.
Predict my Canonical questions →Canonical hiring process, step by step
What each step tests and how long it takesCanonical's hiring process runs in eight steps across three stages, and the company says it takes around three months on average from application to offer. The written interview has a 14-day deadline and the GIA takes 30 to 45 minutes; the company publishes no timing for the other steps, so the gaps below come from candidates. One Hiring Lead, a leader from the business rather than an HR recruiter, handles your application from start to finish and is ultimately the decision maker.
8 reported promptsSee them and how to take themHide
- 1. Application questions: Tests your academic record and how clearly you think. You apply through the job ad and answer its questions, including your high school and degree results. A domain expert reviews it by hand; the company says it uses no automated screening. If you pass, you get a personal candidate dashboard with your assessment and interview plan. You can apply to the same job once in 180 days, and to up to four different jobs in that period.
- 2. Written interview (14 days): Tests your achievements, education, motivation and thinking about the role, in your own words. It is tailored to the job; candidates report 38 to 42 questions and 15 to 21 pages, and one security candidate describes four areas: engineering experience, education, context and role-specific questions. You upload a PDF within 14 days and it is graded anonymously, typically by two domain experts. Daniele Procida, a Canonical hiring lead, wrote in 2023 that the interviewers read it before they meet you, so expect questions about your answers.
- 3. GIA aptitude test (30 to 45 minutes): Tests trainability: reasoning, perceptual speed, number speed and accuracy, word meaning and spatial visualisation, in five timed parts. It comes from Thomas International, and every applicant takes it whatever the level. The company says it is not an IQ test.
- 4. Technical assessment (some roles): Tests your skills in the job's domain. A domain expert grades it and the interviewers come back to it later. Candidates report a two-hour DevSkiller Python test, a 90-minute coding test and a three-part security take-home expected to take about three hours.
- 5. Three early-stage interviews: Test technical and domain skills, with interviewers who are likely to be your future colleagues, peers and close stakeholders. The company says this stage decides which team and role you fit best, and its engineering chief of staff gives the example of an engineer who applied for container orchestration and was placed on the distributed database team. Candidates describe video calls of about an hour each, covering software architecture, Linux and the domain of the job.
- 6. Talent interview, after a 10-minute PPA: Tests your career motivations and path. You first complete a 10-minute Personality Profile Analysis on your working style, then meet the Talent Science team. Pay discussions start here, and the FAQ says your type of contract is confirmed here too.
- 7. Late-stage interviews: Test fit with the team and its leadership. You meet your potential manager, your Hiring Lead and other senior stakeholders; candidates for management or leadership roles also meet the CEO, Mark Shuttleworth.
- 8. Offer: Your Hiring Lead communicates the offer. Candidates who are turned down get no individual feedback: the company's FAQ says the volume of applications makes it impossible.
Candidates report longer runs than the three-month average: one counted eight one-hour interviews over nearly three months, and a security candidate who applied in January 2026, on a sixth application, had five interviews done and two still to come at the end of April. Keep other processes going in parallel.
What Canonical screens for
Canonical's careers pages and blog are direct about what it screens for, and two rules shape how you should answer.
- Academic results at every level, from high school onward, which the company says it values regardless of seniority
- Evidence over claims: its blog says it wants to know how you can demonstrate the skills and qualities it looks for
- Initiative, leadership, commitment, technical excellence and persistence, the qualities the blog lists
- Your own work only: the company asks candidates to present their ideas without online aids in assessments and interviews
- Comfort with a fully remote company that still meets in person two to four times a year
Canonical interview questions
Candidate-reported themesMost Canonical interview questions come in writing first, in the written interview, and several candidates have published the questions they were asked. The practice questions below follow those reports; the interviewers come back to your written answers later, so practise saying them out loud too.
Rehearse these out loud for Canonical. Free to try.
See what's included →Behavioural & motivation
- Why do you want to work at Canonical?Cal
I'm Cal, your AI coach. Say whatever comes to mind: I'll put your answer in order, show what's missing, then score it.
Scored on Specificity · Connection · Research
- Your answer is scored on
- SpecificityNames at least two concrete things about this company or role that could not be copy-pasted to a competitor.
- ConnectionTies those specifics to their own goals or experience, so it reads as fit rather than flattery.
- ResearchShows they actually looked: a product, a technical choice, a public post. Generic praise for culture or mission does not count.
See how a strong answer sounds
Example · not your answer
“You're the only team I've found that publishes incident reviews with the real timeline in them, and I've read four now. I've worked somewhere that treated postmortems as a ritual you get through, and I'd rather not do that again.”
Strong. One row still open.
- SpecificityOne, not twoThe incident reviews are the only specific here. The rest could be said to any company.
- ConnectionJoined upTies the observation to how they want to work, not just to admiration.
- ResearchLooked properlyRead four of them. That is looking, not skimming an About page.
That comes back in about ten seconds, with what worked, what to fix, and what the question was really after.
We never store your recording or your answer. How this is handled ↗
- How did you rank in mathematics in your final year of high school, and how do you know?
- What is the most exceptional thing you have accomplished, and what exactly was your part?
- Tell us about your involvement in open source.
Technical
- Practice: outline your thoughts on monolithic, service-oriented and microservice architectures. When would you choose each?Software architecture in writing: Reported in the written interview for an engineering roleListening for: Clear distinctions · When to choose each · Costs named
- Practice: a Linux server is slow and the load average is high. Walk through how you find the cause.Linux system skills: A reported interview in its own right for engineering rolesListening for: A method · The right tools · From symptom to cause
- Practice: write a function that parses a large log file and returns the ten most frequent error messages, then say how it scales.Coding test: A timed online test for some roles: 90 minutes to two hoursListening for: Working code first · Scales with size · Edge cases
- Practice: explain in depth a system you built or ran in the domain of this job, and the hardest problem you hit.Domain deep dive: The third technical interview follows the job: microservices, security, Ubuntu packaging and so onListening for: Real depth · A hard decision · Their part
Don’t walk in hoping. Walk in rehearsed.
Calibrd predicts the questions Canonical is likely to ask for your role, interviews you out loud, and tells you what a hiring manager would hear.
Free · talk any answer through
Pay
Canonical posts a range on one live engineering ad: for the entry-level web frontend engineer role, US-based candidates are paid between USD 48,000 and 70,000, with the level set during the early interviews (read 9 November 2026; none of its other 315 ads on Greenhouse that day printed a range). Its job ads list an annual compensation review, a learning budget of USD 2,000 a year and parental leave, and the company says pay discussions start at the talent interview. Levels.fyi's self-reported figures (read 9 November 2026) sit well below the US median for software engineers, and pay varies by country because roles are hired worldwide. Calibrd benchmarks an offer against your level and location in the report.
Applying to Canonical? Paste the posting and see whether they’d shortlist you →
Job alerts at Canonical. Not interviewing yet? Calibrd reads the open jobs at Canonical every morning and checks each new one against your resume the way a hiring manager would. Get job alerts at Canonical.
How to prepare for a Canonical interview
- Gather your school and university results before you start, with the grading systems, and answer exactly.
- Budget several evenings for the written interview. Candidates report 15 to 21 pages.
- Practise the GIA format with Thomas International's free example booklet so the timed parts feel familiar.
- Prepare for a Linux systems interview even if the job is not a Linux role; candidates report one for engineering jobs.
- Plan for about three months, and keep other processes going alongside it.
- Write every answer yourself: the company forbids AI tools at every stage and says each answer will need clarifying in a later interview.
- Say yes to travel only if you mean it: the company asks everyone to meet in person two to four times a year.
This guide covers Canonical's engineering and research hiring. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.
Also interviewing at Crossover, Bending Spoons or Linear? Their guides follow the same format, from the first screen to the offer.
Knowing the questions isn’t the same as answering them out loud. Run a Canonical mock: spoken answers, coached on the spot. Your first mock is free.
Run a Canonical mock →FAQ & sources
What is Canonical's interview process?
Canonical describes its process on its careers site in three stages: assessment, interviews, and a late stage leading to an offer. The stages, in order: Application questions; Written interview; Psychometric test; Technical assessment; Technical interviews; Talent interview; Late stage and offer.
What does Canonical look for in candidates?
Canonical's careers pages and blog are direct about what it screens for, and two rules shape how you should answer. Academic results at every level, from high school onward, which the company says it values regardless of seniority; Evidence over claims; Initiative, leadership, commitment, technical excellence and persistence, the qualities the blog lists; Your own work only.
What questions does Canonical ask in interviews?
Most Canonical interview questions come in writing first, in the written interview, and several candidates have published the questions they were asked. Technical themes: Software architecture in writing; Linux system skills; Coding test; Domain deep dive.
What is in the Canonical written interview?
Most of the effort in Canonical's process goes into two things before any interview: a long written interview and an aptitude test. Candidates report spending many hours on the written part; one estimated around 20 hours for the whole process including preparation. Covered on this page: School and university results; The long written answers; The aptitude test (GIA); The Personality Profile Analysis; No online aids, no AI.
How long does each step of Canonical's hiring process take?
Canonical's hiring process runs in eight steps across three stages, and the company says it takes around three months on average from application to offer. The written interview has a 14-day deadline and the GIA takes 30 to 45 minutes; the company publishes no timing for the other steps, so the gaps below come from candidates. Covered on this page: 1. Application questions; 2. Written interview (14 days); 3. GIA aptitude test (30 to 45 minutes); 4. Technical assessment (some roles); 5. Three early-stage interviews; 6. Talent interview, after a 10-minute PPA; 7. Late-stage interviews; 8. Offer.
What is Canonical's hiring process?
Canonical describes three stages: assessment, interviews, and a late stage leading to an offer, taking around three months on average for every level. Inside them come application questions, a long written interview due within 14 days, Thomas International's GIA aptitude test, a technical assessment for some roles, three technical video interviews, a talent interview and late-stage calls with senior people.
Why does Canonical ask about high school?
Canonical says it values academic results at every level, from high school onward, whatever your seniority, so the written interview asks how you ranked in mathematics and in your native language at high school, with the grading system. Its careers FAQ says the questions help it understand your motivations, drivers and performance in your early years, and are not a reflection of the level of the role. Its blog adds that nearly everyone it hires has a good degree, and that it has also hired outstanding people without one.
How long is the Canonical interview process?
Around three months on average from application to offer, Canonical says, for every level from graduate to VP. Candidates describe eight or more conversations along the way.
How much does Canonical pay?
Web frontend engineer, entry level, US · job ad: $48,000–70,000; Graduate · Levels.fyi, US, self-reported: $83.7K; Software Engineer I · Levels.fyi, US, self-reported: $105K; Median, US · Levels.fyi, 134 self-reported submissions: $90K. Canonical posts a range on one live engineering ad: for the entry-level web frontend engineer role, US-based candidates are paid between USD 48,000 and 70,000, with the level set during the early interviews (read 9 November 2026; none of its other 315 ads on Greenhouse that day printed a range).
How do I get a job at Canonical?
This guide follows the software engineer path, from graduates to senior engineers. Canonical says it values academic results at every level, and its blog adds that nearly everyone it hires has a good degree, while also saying it has hired outstanding people without one. Hiring runs in 7 stages, starting with Application questions.
How do I get job alerts for Canonical jobs?
Calibrd reads the open jobs at Canonical every morning. Add Canonical to the companies you watch in Calibrd's Job search, with the role you're after, and each new job is checked against your CV: you see only the ones you could be shortlisted for. The first search runs as soon as you start it; after that a free account searches once a week, and with a pass the search runs every morning.
How do I prepare for a Canonical interview?
Gather your school and university results before you start, with the grading systems, and answer exactly. Budget several evenings for the written interview. Candidates report 15 to 21 pages.
- 01Canonical, Hiring processthe three stages, the Hiring Lead who handles the application from start to finish, the candidate dashboard, the 180-day reapplication rule, the written interview tailored to the job and graded anonymously, typically by two domain experts, the five-part 30-to-45-minute psychometric test that is not an IQ test, the optional technical assessment graded by a domain expert, three technical interviews, the talent interview with a 10-minute Personality Profile Analysis and the start of pay discussions, the late stage, about three months on average, no online aids, fully distributed for over 20 years (read 28 September 2026, reread 9 November 2026)
- 02Canonical, Careers FAQ14 days to submit the written assessment as an anonymous PDF without GitHub or LinkedIn links, question-and-answer format preferred, why high school grades are asked at every level, Thomas International as the assessment partner, the GIA's five components and norm group, resends only for platform faults, GIA and PPA reports from the dashboard, AI tools strictly forbidden and answers clarified later, no recording, the hiring lead as decision maker, contract type confirmed at the talent interview, no individual feedback, up to four roles in 180 days (read 9 November 2026)
- 03Canonical blog, Hiring the Canonical wayby Maksim Beliaev, Chief of Staff for software engineering, 6 February 2026: no automated screening, every CV read by hiring leads and associates, candidates redirected to a better-fitting team, with the container orchestration to distributed database example
- 04Canonical blog, Not just an annoying list of questionsby Daniele Procida, 9 August 2023: why the written interview exists, that the interviewers read it, and that each one is assessed by two to four independent reviewers in his hiring
- 05Canonical, Graduate Software Engineer job adthe high school mathematics and native language questions, the degree result with grading system, the fast-track process for 2025 and 2026 graduates, globally remote, meeting in person two to four times a year for one to two weeks, the USD 2,000 learning budget (read 28 September 2026; the ad no longer loaded on 9 November 2026)
- 06Canonical, Graduate Software Engineer, Open Source and Linux, job adthe live graduate ad: an exceptional academic record from high school and university, hiring 2025 and 2026 graduates, globally remote, twice-yearly in-person sprints, the USD 2,000 learning budget (read 9 November 2026). The native-language question, the degree grading system and the fast-track rest on the earlier ad above
- 07Ubuntu blog, How to get a job at Canonicalby Daniele Procida, 30 June 2025: the written interview shows what the company cares about, nearly everyone hired has a good degree, outstanding people without one have been hired, and the qualities it looks for
- 08Sahra Vadrot, Canonical hiring processa candidate's account (23 March 2026): 42 written questions and about 15 pages, a 90-minute coding test, the Thomas GIA, eight one-hour interviews, nearly three months, about 20 hours in total, a rejection
- 09dustri.org, My experience with Canonical's interview processa candidate's account (1 June 2025): the school grade questions, 38 written questions and 21 pages, the Thomas GIA and behavioural assessment, a two-hour DevSkiller Python test, interviews on software architecture, Linux, security, talent and hiring leads, and a final interview with Mark Shuttleworth
- 10Hacker News, a Canonical applicant's processa September 2023 thread listing about ten stages, written questions on accomplishments, motivation, open source and engineering strengths, and aptitude and personality tests
- 11mdimado, Canonical hiring processa candidate's account of the Ubuntu Security Engineer process (the page is dated 29 April 2025 but describes applications from June 2025 to late April 2026): the written interview's four areas, the Thomas GIA, a three-part security take-home expected to take about three hours, five interviews from March to April 2026 with the hiring manager and a VP still to come, the 180-day rule from the candidate's side
- 12Thomas International, General Intelligence Assessmentthe GIA's five parts: reasoning, perceptual speed, number speed and accuracy, word meaning and spatial visualisation
- 13OSnews, My experience with Canonical's interview processcoverage of the dustri.org account (2 June 2025), citing low Glassdoor ratings of the interview experience
- 14Canonical, Web Frontend Engineer (JS, CSS, React, Flutter) job adhome based, worldwide; for the entry-level position, compensation for US-based candidates between USD 48,000 and 70,000, with the early interviews establishing your level (read 9 November 2026)
- 15Levels.fyi, Canonical software engineer salariesUS figures from $83.7K for a graduate to $105K for Software Engineer I, a median of $90K across 134 submissions (page updated 23 September 2026, read 9 November 2026)
Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.
Prep for a real Canonical role
Practise your Canonical interview, out loud.
Paste a real Canonical posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — then listens to your spoken answers and coaches them. Your first mock is free.
Free to start · No card · Encrypted at rest, never used to train AI, remove anytime