Real, anonymous reports from people who interviewed for Software Engineer at Canonical, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role and found the overall experience extremely punishing mainly because of an unusually long, essay-style written stage followed by aptitude and/or other tests, then slow or non-specific rejection.
I interviewed for the Software Engineer role and experienced the process as unusually slow, with written tasks spread over long windows that didn’t fit urgent hiring timelines.
Candidates typically start with a lengthy written assessment that includes essay-style questions about their background and motivations, often requiring significant self-reflection and detailed responses.
The interview process includes timed psychometric and cognitive assessments, which candidates found to be challenging and critical for early filtering before technical discussions.
Candidates undergo multiple technical interviews that cover a range of topics, including Linux, Python, and full-stack development, often requiring in-depth knowledge and problem-solving skills.
The overall interview process is described as lengthy and structured, often spanning several weeks to months, with candidates experiencing delays and a lack of timely communication regarding their status.
Many candidates reported receiving little to no feedback after interviews, with some experiencing ghosting or automated rejections, leading to frustration and uncertainty about their performance.
Late-stage discussions often revolve around salary expectations, with mismatches leading to rejections, highlighting the importance of aligning compensation discussions early in the process.