
Canva Data Analyst candidates report a recruiter screen focused on background and role fit, followed in one account by a Google Sheets SQL exercise using licensing data, ranking, grouping, windows, and product interpretation.
$130K
Avg. Base Comp
$155K
Avg. Total Comp
2 rounds
Typical Rounds
1-2 weeks
Process Length
Canva Data Analyst interview reports point to an early process that starts with a recruiter conversation, but the depth of that conversation varies. One candidate described a lightweight initial screen and was asked to explain how they use SQL in plain language. Another described a standard recruiter discussion of their current role, scope, the open position, and the qualities Canva was seeking. Prepare a concise account of your current analytical scope and how SQL supports your work, rather than assuming the first conversation will immediately become a technical interview.
The clearest technical detail comes from a subsequent SQL screen completed in Google Sheets. The candidate reported working with a licenses table and being asked to count and rank licenses, use GROUP BY and window functions, and interpret the resulting data to help shape product roadmaps. Multi-table joins were specifically not tested in that account. Practice explaining both your query logic and the decision-oriented meaning of the output: the reported exercise combined SQL mechanics with product interpretation. One other candidate did not advance beyond the recruiter discussion, so the evidence is limited on later stages and does not establish a universal sequence.
Synthesized from 2 candidate 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 that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| Search Ranking | |
| Address Schema | |
| Hurdles In Data Projects | |
| Duplicate Rows | |
| Digital Marketing Metrics | |
| Generate Shopping List from Recipes | |
| International e-Commerce Warehouse | |
| k-Means from Scratch | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| First to Six | |
| Closest SAT Scores | |
| Experiment Validity | |
| Download Facts | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Random SQL Sample | |
| Button AB Test | |
| Compute Deviation | |
| Top 3 Users | |
| 500 Cards | |
| Minimum Change | |
| Raining in Seattle | |
| Employee Salaries (ETL Error) | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter screen covering their current role and scope, the open requirement, and desired qualities. One account also included a plain-language question about how the candidate uses SQL.
The recruiter conversation may ask you to connect your background to the role before any technical exercise. Prepare concrete examples of your scope and explain SQL usage clearly without assuming an advanced assessment at this point.
One candidate then completed a SQL exercise in Google Sheets using a table of licenses. It reportedly covered counting and ranking licenses, GROUP BY, and window functions, followed by interpreting results for product-roadmap decisions; multi-table joins were not tested.