Canonical logo

Canonical Frontend Engineer Interview Questions
& Process

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

Based on 28 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
17.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Canonical.

Showing 3 of 28
Canonical logo
Canonical

Frontend Engineer

Engineering · nearly a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Background check Offer
Interview formats
Coding Technical Behavioral Other

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.

Confirmed questions7 questions
  • Could you describe a frontend project you were involved in, detailing the technical choices you made?
  • Tell me about your background and experience.
  • What are your thoughts on JavaScript programming?
Canonical logo
Canonical

Frontend Engineer

Engineering · a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Technical screen Technical screen
Interview formats
Technical Coding Behavioral

The interview process started with a few stages. First, there was a written response that was pretty long, asking about my academic history, past jobs, and technical background. It took a while to get it done. Then there was a technical assessment with multiple-choice questions on computer science basics and a coding challenge to make a Polish notation calculator. The last part of the first phase was an aptitude test from Thomas International, which was about an hour long with puzzles involving words and shapes. After getting through that, there were three technical interviews. These were face-to-face and focused on tech experience. The first was about web and UI, the second about Linux, and the third about software engineering. I did two of these before I decided it wasn't worth the time for the pay and benefits offered.

Confirmed questions3 questions
  • Which web technology stack do you know best, and what frontend and CSS frameworks have you utilized?
  • Can you tell me about your experience with different frontend and CSS frameworks?
  • What frontend frameworks and CSS frameworks are you most familiar with?
Canonical logo
Canonical

Frontend Developer

Engineering · a year ago

Entry Average Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Take home Background check
Interview formats
Behavioral Technical Other

I applied online to 3 different job postings and got an email saying my resume was selected. They sent me a questionnaire with over 30 questions about my high school graduation and current work, asking for subjective answers. It mentioned a team would review these anonymously. Answering took me 3-4 hours, and 90% of the questions weren't related to the job. Two positions rejected me within 5 minutes of sending my answers, suggesting manual review. For one position, I advanced to an assessment, which took about 90 minutes and was unrelated to the job description, focusing on math and reasoning. After that, I had a 20-30 minute behavioral assessment. I received a rejection email a few hours later. I'd suggest avoiding this company; it was a waste of time. No human interaction after 3-4 rounds is bad, and the questions were often off-topic.

Confirmed questions1 question
  • How were you in Mathematics during high school?

Canonical Frontend Engineer Interview Questions

Quoted word for word from Canonical interview reports.

Could you build a prefix operator calculator using frontend code?

Read reports

When would you opt for utility-first frameworks like Tailwind CSS versus component-based ones like Bootstrap?

Read reports

What do you think your high school friends would remember about you?

Read report

Could you explain the distinction between [concept A] and [concept B]?

Read report

Could you tell me what your final grade was in high school?

Read report

What specific memory would your high school friends have of you?

Read report

What percentage of students were you ranked above in high school?

Read report

Formats, difficulty and experience

Across all 28 Canonical interview reports.

Interview formats

Technical 38.9%
Coding 23.6%
Behavioral 20.8%
Other 16.7%

Interview difficulty

Easy 17.9%
Average 53.6%
Difficult 28.6%

Candidate experience

Positive 17.9%
Neutral 25%
Negative 57.1%