Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

8 stories

Likes earn the author +10 XP for the first 3 likes each day

CanonicalSoftware Engineer
Reported Apr 2026

Canonical Software Engineer interview spanning React, C++, Linux, and full-stack JavaScript

I interviewed for a Software Engineer role through a multi-interview, all-technical process. It moved from front-end topics into broader full-stack engineering, including Linux and open source. In the front-end interview, I was asked about React and general front-end topics. The systems and programming interview shifted to C++ and Linux. Another round covered full-stack development fundamentals i…

Technical Screen0
CanonicalSoftware Engineer
Reported Apr 2026

Canonical Software Engineer technical rounds on Linux and open source

I interviewed for the Software Engineer role and went through a two-track technical process in the middle of a longer interview sequence. One track focused on architecture and engineering depth. The other covered Linux, open-source topics, and platform fundamentals. In the software architecture and engineering round, I was asked about architecture qualities, engineering methodologies, and how eng…

Technical Screen0
CanonicalSoftware Engineer
Reported Apr 2026

Canonical Software Engineer interview with a long written stage

I interviewed for a Software Engineer role, and the overall experience felt extremely punishing. It started with an unusually long, essay-style written stage, followed by aptitude and other tests, and ended with a slow or non-specific rejection. For the written interview, or long questionnaire, I answered extensive essay-style questions about my background. They often asked for school-related det…

Online Assessment0
CanonicalSoftware Engineer
Reported Mar 2026

Canonical Software Engineer interview with multiple assessments and late-stage rounds

I interviewed for the Software Engineer role through a drawn-out but structured process. I completed several assessments, followed by interviews covering coding, systems concepts, and behavioral collaboration. I started with a written-style screen, then completed logic and personality testing. The technical stages included long interview sessions, another technical segment later in the process, a…

RejectedOnline Assessment0
CanonicalSoftware Engineer
Reported Mar 2026

Canonical Software Engineer interview with questionnaire and Python assessment

I interviewed for the Software Engineer role through a multi-assessment process that started with a long questionnaire and two tests, before any deeper technical discussion. I answered around 30 questionnaire questions. The first assessment was a non-standard test made up of different types of tasks. The second assessment focused on Python. I didn’t receive an offer. Early filtering leaned heavil…

Online Assessment0
CanonicalSoftware Engineer
Reported Mar 2026

Canonical Software Engineer online assessments with unclear follow-up

I interviewed for the Software Engineer role through a process that was quick to schedule but ultimately unclear. It involved questionnaires and online tests, followed by either an early decline, no follow-up, or a rejection with little explanation. I filled out a form-like application and completed a detailed written interview about my background and problem-solving. I also took an aptitude-styl…

RejectedOnline Assessment0
CanonicalSoftware Engineer
Reported Feb 2026

Canonical Software Engineer interview: written and psychometric testing

I interviewed for the Software Engineer role through a straightforward screening process. First, I completed a written test by listing my achievements, then completed a psychometric assessment. If I had been shortlisted, I would have moved on to a one-on-one interview. I didn’t move forward. My takeaway was that the process depended heavily on scoring well in the written and psychometric tests. L…

Other0
CanonicalSoftware Engineer
Reported Jan 2026

Canonical Software Engineer interview: Python, Docker, Linux, and Kubernetes rounds

I interviewed for the Software Engineer role through a long, executive-heavy process with multiple technical rounds. The questions covered Python, Docker, Linux, and Kubernetes, and I spoke with senior leaders and team leads. I didn't receive an offer. After all the stages and conversations, the final decision was described as a skills-set mismatch. Location: India. Overall feedback: Negative. Of…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP