Staff Software Engineer - Export
Canva is hiring a Staff Software Engineer - Export in Sydney, Australia. Level rates it ; you can apply on Canva.
Level's read on this job
- Little AI ●○○○ is how Level rates this software engineer role: aI is not part of the work.
- The posting mentions Chromium, C and rendering pipelines among its tools and skills.
- Level classes it as a lead role.
- Canva has 96 other open roles on Level.
AI in this role
Staff Software Engineer leading the technical direction of Canva's Chromium-based design export pipeline and rendering infrastructure.
Hey, g'day, mabuhay, kia ora, 你好, hallo, vítejte!
Thanks for stopping by. We know job hunting can be a little time consuming and you're probably keen to find out what's on offer, so we'll get straight to the point.
What you'd be doing in this role
As Canva scales, change continues to be part of our DNA. But we like to think that's all part of the fun. So this will give you the flavour of the type of things you'll be working on when you start, but this will likely evolve.
You'd be the second Staff Engineer on Export, splitting the domain with our existing Staff Engineer so neither of us is a single point of failure on the hardest parts of the system.
At the moment, this role is focused on:
- Owning the technical direction of how Canva renders designs into files, including our Chromium-based export pipeline, and setting the architecture that keeps it reliable as both Canva's editor and Chromium itself keep moving
- Being the person the team turns to on the hardest rendering problems: upgrade breakages, rendering race conditions, and production incidents caused by upstream Chromium changes
- Deciding how we absorb upstream change rather than react to it, which covers monitoring and testing infrastructure that catches Chromium regressions before users do, and designs that survive Chromium's frequent output structure changes
- Setting the direction for PDF accessibility and compliance (PDF/UA, WCAG) across exported files for our Enterprise customers, and making the calls on how deeply we tag, where we draw the line, and what we build versus buy
- Leading on export reliability and performance at the scale of over 50 million weekly downloads, spanning format optimisation, distributed systems design, and the failure modes that only show up at that volume
- Raising the level of the engineers around you through design review, pairing on gnarly debugging sessions, and the kind of documentation that turns one person's Chromium knowledge into the team's
- Working across the Editing Platform group and beyond it, so that teams shipping new editor features know their work will hold up when someone hits download
You're probably a match if
- You have deep experience with Chromium or another browser rendering engine, and you've worked inside it rather than just around it
- You're comfortable in C++ when a problem takes you into a large third-party codebase, and you can build a clear picture of code you didn't write
- A background in rendering pipelines, graphics programming, or print production systems
- You're a strong Java backend engineer, that's what our product is built on
- You've owned a technical domain end to end: you set the architecture, made the trade-offs, and lived with the consequences
- You've debugged layered systems where the problem spans multiple codebases and languages, and you've led others through that kind of investigation
- You bring the engineers around you along with you, through mentoring, design review, and the standards you hold
- You've built or maintained systems where upstream dependencies change frequently, and you have a view on how to make that sustainable
Nice to have:
- PDF specification knowledge, or experience with PDF generation and post-processing
- Experience with accessibility standards in document or file output
About the team
The Export team sits within the Editing Platform group and owns one of Canva's most critical workflows: transforming designs into downloadable files that users can share, print, and bring to life. Over 50 million people download their creations through us every week. We focus on three things: reliability users can count on, speed that keeps pace with their creativity, and flexibility across every format and use case.
Beyond the main download flow, we power print production, enable AI model training, generate thumbnails, and make sure every new editor feature works seamlessly when someone hits that download button. As a Staff Software Engineer here, you'd be shaping how one of Canva's highest-leverage systems evolves, and the decisions you make will be felt by every team that ships something a user needs to download.
Other stuff to know
We make hiring decisions based on your experience, skills and passion, as well as how you can enhance Canva and our culture. When you apply, please tell us the pronouns you use and any reasonable adjustments you may need during the interview process.
We celebrate all types of skills and backgrounds at Canva so even if you don't feel like your skills quite match what's listed above, we still want to hear from you!
Please note that interviews are conducted virtually.
How we rate this
Staff Software Engineer - Export at Canva rates 0 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.
Little AI. AI is not part of the work.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Also common in software engineer jobs at this level
Pay
- Typical software engineer job
- $168k
This posting doesn't list pay. Use the typical software engineer figure when pay comes up. See software engineer jobs
Questions you could be asked
- Tell me about a project where rendering pipelines was part of your work. What did you do?
- Tell me about a project where graphics programming was part of your work. What did you do?
- Tell me about a project where distributed systems was part of your work. What did you do?
- Tell me about a project where performance optimization was part of your work. What did you do?
- Walk me through how you've used Chromium in your day-to-day work.
Adapt your resume
- List these exact terms on your resume: Rendering Pipelines, Graphics Programming, Distributed Systems, Performance Optimization, and Chromium. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.
Get new software engineer jobs by email
One email a week with the new software engineer jobs, each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Software Engineering roles that involve little AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step