Job Description
Job Description
Join the team powering the foundation of Canva’s world-class user experience.
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.
Where and how you can work:
Collingwood is home to our Melbourne campus - a vibrant, creative hub for connection and impactful work. While Sydney is home to our HQ, Melbourne brings its own unique vibe, with local artwork, lush greenery, and thoughtfully designed spaces to help you collaborate, focus, and feel part of a welcoming community.
This role is based in Melbourne, and we’re looking for someone who calls it home. Our hybrid way of working gives you the flexibility to work remotely, and to come together on campus for meaningful in-person collaboration and connection when it matters most.
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.
Web Platform owns how Canva loads, renders, and runs in the browser. Every product team at Canva builds on top of what this group ships. Every user who opens canva.com sees the work of this team in the first few hundred milliseconds of their experience. Our ambition is to load the first page in under two seconds, and we’re not there yet. Getting there is one of the most interesting frontend engineering problems in the company.
The strategic bet is rebuilding how the web product is served. Server-side rendering. React Server Components. Reducing round trips between the client and the backend. A modern offline strategy that loads a minimal editor when the network drops. The kind of frontend architecture that takes a mature, complex product and makes it feel instant on every device a user might pick up.
There’s a second reason this work matters now. As Canva scales toward a billion monthly active users, performance becomes a defining property of the product. The architecture decisions made in this role will outlast most of the systems built on top of them.
At the moment, this role is focused on:
Owning the technical direction for the web platform: Set the architecture for SSR, React Server Components, and the shape of how pages get assembled and served. Define what good looks like and bring the rest of the frontend specialty with you.
Performance at Canva scale: Drive the path to sub-two-second first page load. Build the measurement, the observability, and the engineering discipline that makes performance a property of the platform, not a quarterly project.
Influencing the broader frontend specialty: This work touches every frontend engineer at Canva. You’ll be defining the patterns the frontend specialty adopts, authoring design documents, working prototypes and migration guides that make the new architecture the obvious default. You’ll work across product orgs to shape how teams organically transition to modern frontend practices, with the credibility to bring people along rather than mandating change.
Leading with code, not whiteboards: Canva doesn’t have an architecture function — Principal engineers stay hands-on. You won’t ship every line, but you’ll live in the code and push commits.
Owning the offline and resilience story: What happens when the network drops, the device is slow, or the user is on the other side of the world. Define how the product responds gracefully across the full range of real conditions.
Sparring with strong peers: You’ll join a small group of Principal and Staff engineers shaping how Canva’s frontend works. The bar is high. The work compounds.
Influential Individual Contributor: No direct reports. But every Staff engineer in Web Platform routes their architectural decisions through you. How you operate sets the standard others reach for.
What success looks like. First page load times reach the bar across every device and every geography users open Canva from. Performance is a property of the platform that holds even as the product grows, not a number we chase in quarterly cycles. The patterns set by this role are adopted across the frontend specialty as the default way to build.
You’re probably a match
We’d love to hear from you if you fit one or more of these. You don’t need to meet all of them, but the more the better — and if you join the team, we’re invested in helping you grow.
React at depth: Not just a user of React, you understand how React is built. Reconciliation, rendering, the server component model, the hooks model. You’ve shaped React decisions at scale, ideally with open-source contributions or production work that pushed the framework’s limits.
Performance at scale: Driven measurable performance gains on a complex, mature web product. You know how to measure what matters and how to filter the noise. Bonus if you’ve shipped server-side rendering or React Server Components in production.
Principal altitude: You’ve owned problems where the right answer didn’t exist when you started. You found it through prototyping and measurement, not a design doc written upfront.
Org-wide influence: You’ve shipped something foundational on a mature product - a bundler migration, an SSR rollout, a rendering model shift - without disrupting the teams building on top of the platform. You cut through the noise and bring a large number of leaders to consensus on a clear and compelling technical direction.
Active individual contribution: You’re still writing and committing code on a day-to-day basis.
AI fluency: Used agentic orchestration in real work. Have a view on what changes for frontend engineering when AI is a daily part of the workflow.
Technical knowledge
React internals: Reconciliation, the rendering model, server components, suspense
TypeScript depth: Production-grade fluency, not surface familiarity
SSR and RSC: Server-side rendering and React Server Components in production
Frontend-backend communication: How pages get served, how requests get batched, where the round trips live
Performance measurement: Real User Monitoring, synthetic testing, the metrics that matter
Offline resilience: Progressive enhancement strategies for complex web applications
Deep fundamentals: Engineering fundamentals from a CS background, including data structures, complexity, the hard parts
Nice to have
Open-source contributions: React, Next.js, or the broader frontend ecosystem
Live migrations: Experience evolving a complex frontend product without disrupting the teams building on top of it
Edge runtimes: Cloudflare Workers, Fastly, or equivalent
Backend partnership: Cross-functional work with backend platform teams on the request/response contract
About the Group
This role sits in the Client Platform Group, where our mission is to ensure a delightful experience for every user on every device. Client Platform owns the foundations that every product team builds on, including Web Platform, Mobile Platform, and the user-facing surfaces of the product. Hundreds of millions of users sit on top of what this group ships. Every Canva product runs on it.
What’s in it for you?
Achieving our crazy big goals motivates us to work hard — and we do — but you’ll also enjoy moments of magic, connection, and fun throughout life at Canva. We offer:
- Equity packages — we want our success to be yours too
- Inclusive parental leave policies supporting all parents & carers
- An annual Vibe & Thrive allowance supporting wellbeing, social connection, and office setup
- Flexible leave options empowering you to recharge and thrive
Check out lifeatcanva.com for more info.
Other stuff to know
We make hiring decisions based on your experience, skills, and passion, as well as how you enhance Canva and our culture. When you apply, please share your pronouns and any adjustments you might need during the interview process. We celebrate all kinds of skills and backgrounds — even if you don’t tick every box, we want to hear from you!
Interviews are conducted virtually.
