Senior Software Engineer applicants have rated the interview process at Canva with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 56.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 33 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Canva overall takes an average of 29 days.
Common stages of the interview process at Canva as a Senior Software Engineer according to 6 Glassdoor interviews include:
Skills test: 23%
Phone interview: 23%
One on one interview: 23%
Background check: 15%
Personality test: 8%
Group panel interview: 8%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 day. I interviewed at Canva
Interview
- Phone Screen
- Coding interview
I did twice in 2 years, the first time I went through everything, but in the end the position was closed because of uncertain market.
The 2nd time I got a rejection letter without even a phone call, but the funny part is I applied a software engineer role, the rejection letter is QA engineer, so I was rejected to be a QA engineer, when I applied software engineer, so am I get rejected or not? this is the funny part and disappointed.
I guess they are too busy to manage the hiring well.
Pros: Interview prep materials were detailed and sent well ahead of each stage. The AI-assisted coding round was a genuinely interesting format.
Cons: The process took roughly two and a half months end-to-end, across seven separate touchpoints: a recruiter screen, an informal chat with an engineering lead, two technical interviews, a three-competency final loop crammed into one almost-three-hour session with a single 15-minute break, an additional vibe check with someone more senior, and a couple of feedback calls. After the final loop, communication went quiet. I had to follow up twice over the following fortnight before getting any answer. After all that time investment, unpaid and unsupported by any interim feedback, the outcome was a generic "closer match" rejection.
Advice to Management: Consider consolidating the number of discrete interview stages, or at minimum be upfront about the likely timeline so candidates can plan around it. If a decision date slips, a proactive heads-up beats making candidates chase twice for a status update.
Interview questions [1]
Question 1
Design a system architecture to generate multi-media outputs from design templates and related resources.
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.