About the role
Join
the team redefining how the world experiences design. 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. Canva’s engineering organisation is 600 people strong, and right now every one of them needs to make the shift from a world where React meant the browser, to a world where React means iOS, Android, and web all at once. The Portable Platform is that move. A production-scale React codebase, hundreds of engineers who’ve spent their careers building for the browser, and a migration that has to land cleanly enough that those engineers never have to become mobile experts. It’s a difficult engineering problem and it’s yours to help solve. As a Staff engineer, you’ll own the architecture layer of that transition. The abstraction you design becomes the foundation those engineers build on. The patterns you establish become the defaults the organisation works within. You’ll work alongside the Principal Engineer driving the deeper mobile architectural bets, and the engineers going deep on the mobile side. Your contribution is the expertise and clarity that brings everyone else with you. What success looks like. Within 12 months, the frontend layer of the Portable Platform is built and in use. Engineers write React without thinking about which runtime they’re targeting. Runtime concerns stay in the platform, not in product code. Web implementations of core components are in production, and hundreds of engineers have a clear path forward. At the moment, this role is focused on: Build the frontend layer of the Portable Platform: Design and ship the frontend architecture that lets React engineers write once and run across web and React Native. The abstraction has to be clean enough that product engineers never have to think about which runtime they’re targeting. Lead the React Web to React Native transition: Navigate the extraction from a pure React Web codebase to React Web plus React Native. Make the transition clean. The decisions made here shape how Canva’s frontend codebase evolves for years. Own the web implementations of common abstractions: Build the web side of shared Portable Platform components — the pieces that work consistently across iOS, Android, and browser. You own the web runtime slice of that contract. Support the upskilling of frontend engineers: Six hundred-plus frontend engineers are moving from a world where they only had to think about web. Help them understand the new mental model — through code standards, documentation, design reviews, and direct collaboration. Bring SSR and React Server Components into the picture: Server-side rendering and RSC are part of this story — particularly how a backend wires up to the portable frontend layer. This isn’t the headline, but it matters, and you’ll need to reason about it well. Stay hands-on: Staff engineers at Canva ship code. You’ll be in the codebase, writing design docs, committing to production. The architecture work and the engineering work aren’t separate here. 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
