I applied online. I interviewed at Canva in May 2024
Interview
Was Interviewed for Senior Software Engineer position for Canva (Sydney) virtually in May 2024. After initial screening with HR on basic OOPS concepts followed by technical interview, was considered for Backend engineer position only. Got rejected based on the consolidated results of system design, programming language fluency and behavioural rounds
Technical interview 1 : was asked to implement an interface with Power generator, Capacity and Area
Technical interview 2 -
System Design : Whatsapp/FB like chat app
PLF : Implement an interface of Design editor and make the test cases pass. Was questioned on making the main class re-usable by multiple projects.
Behavioural : General questions on conflict management and team communication
Overall process was smooth, got response for each round within 2 days of completion.
Interview questions [3]
Question 1
Implement an interface for Power generators with Capacity and Area mapping
I applied through a recruiter. I interviewed at Canva (Sydney) in May 2026
Interview
Recruiter was very friendly. He was new at the company though and gave inaccurate information about what was to be asked. I got 2 strong hires in the final round (language fluency, values). For technical communications, it is unclear what the outcome was. I was presented with a very detailed document and unclear expectations. Feedback was very unfair and contradictory to what happened in the interview. I thought I just had an unfair interview, but since found out that the company rescinded offers and froze positions and kicked people out after probation. Something is looming at Canva.
Interview questions [1]
Question 1
Tech comms round included system design concepts, contrary to recruiter's guidance.
The technical interview process felt poorly calibrated and inconsistently framed. The main issue was not that the questions were difficult, but that several rounds seemed to test a different skill set than what was communicated beforehand.
In practice, it often felt unclear what the primary evaluation criteria actually were. Some rounds started as if they were focused coding exercises, but the expected discussion appeared to extend into broader design, scaling, or product-style considerations without that scope being made explicit early on. That made it difficult to judge how much time to spend on core implementation versus higher-level tradeoff discussion. The result was a process that felt noisy rather than rigorous.
Round 1 - HR screening call - asking about experience and motivation
Round 2 - AI assisted programming (1h), System design (45m)
Round 3 - Language proficiency (45m), Technical review (45m), Culture and leadership (1h)
The engineers were very friendly. However, the feedback was that I wasn't hitting the seniority expectations.
AI assisted programming - the interviewer expected to see the final result, although I was very close to it, I was disqualified for that. Everything else was acknowledged with strong signals
System design - I was asked to design a rendering system where users download the rendered outcome. The interviewer spent about 5 mins talking about his this role, the other interviewer role, and asked about my experience.
The engineers do not consider your background, if you haven't worked with media files, and related resources like CDN, SAS tokens etc. or you never engaged with downloads, they expect you to know it, and provide your immediate design.