
Canva Data Analyst interview typically runs 1 round: recruiter screen. It took about a week and was very lightweight, with no second round reported.
$140K
Avg. Base Comp
$177K
Avg. Total Comp
4
Typical Rounds
1-2 weeks
Process Length
Candidate experience patterns show a structured Data Analyst process at Canva.
We’ve seen Canva’s Data Analyst process start in a way that catches experienced candidates off guard: the first conversation can feel more like a casual familiarity check than a true evaluation. In the experience we received, the recruiter was described as very junior, and the only technical prompt was a basic question about SQL. That matters because it suggests Canva may be looking first for clear communication and role fit, not for an immediate deep dive into analysis depth.
A recurring theme is that candidates should not assume the opening conversation will be highly structured or technically rigorous. Our candidate report said the exchange felt like someone was explaining SQL back rather than probing how the candidate actually works with data. That’s a useful signal: Canva may care less about impressing them with complexity and more about whether you can describe your workflow in a straightforward, grounded way. The non-obvious risk here is overpreparing for a heavy screen and underpreparing for a conversation that rewards simplicity and clarity.
What makes this especially important is the mismatch between the role level and the apparent screening style. For mid-level analysts, we’d expect a sharper read on experience, judgment, and impact, yet this candidate never got that chance. So the key takeaway is that Canva may be filtering early on for basic alignment and communication polish before anything else, and candidates who can explain their SQL usage plainly without sounding rehearsed are likely to make a stronger impression.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Canva process.
Recruiter screen that asked about my current role and scope. Then discussed the open req and qualities they were looking for. Very standard recruiter screen. Next, I had the SQL screen which happened within a Google sheet. Straightforward test of group by and window functions. Multi-table joins wasn't tested.
Questions asked: SQL screen which happened within a Google sheet. Straightforward test using a table of licenses, and was asked to count and rank licenses. Also tested group by and window functions. Multi-table joins wasn't tested. Final question was interpreting the data to shape product roadmaps.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Canva
Write a query to get the percentage of search queries where all ratings are less than 3 rounded to two decimals
| Question | |
|---|---|
| Duplicate Rows | |
| Digital Marketing Metrics | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Experiment Validity | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Button AB Test | |
| First to Six | |
| Top 3 Users | |
| Compute Deviation | |
| Download Facts | |
| 500 Cards | |
| Last Transaction | |
| Random SQL Sample | |
| Network Experiment Design | |
| Subscription Overlap | |
| Month Over Month | |
| Prime to N | |
| Paired Products | |
| Upsell Transactions | |
| Swipe Precision | |
| Size of Joins | |
| Raining in Seattle |
Synthesized from candidate reports. Individual experiences may vary.
The only round in this experience was an initial conversation with a very junior recruiter for a mid-level Data Analyst role. The discussion was lightweight and centered on a very basic question about how the candidate uses SQL, rather than a structured assessment of analyst skills or a deeper review of background.
Instead of a formal technical screen, the recruiter seemed to be explaining SQL back to the candidate and asking simple usage questions. The candidate noted that this did not feel like a meaningful evaluation of their experience, especially given their seniority.
The candidate expected a more structured first pass that would cover their prior work and overall fit for the analyst role, but that did not happen in this case. The conversation did not progress into a deeper discussion of projects, metrics, or business impact.
There was no follow-up interview or additional stage after the recruiter conversation. The process ended after the first contact, and the candidate did not move forward to later rounds or an offer decision.