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. Where and how you can work Our flagship campus is in Sydney, with a second campus in Melbourne and co-working spaces in Brisbane, Perth, & Adelaide. You have flexibility in how and where you work — whether that's from one of our spaces, from home, or a mix of both. This role is remote-friendly within Australia , so you can choose the setup that empowers you and your team to do your best work. What You'd Be Doing in This Role: Every team at Canva builds and ships on top of infrastructure that has to be fast, reliable, and easy to work with. That's what this role is about: owning and evolving the core systems that let engineering teams across Canva talk to each other's services, route traffic safely, and build in the languages that suit their work. As a Staff Software Engineer, you'll take technical ownership of a meaningful piece of that platform and help set the direction for where it goes next. At the moment, this role is focused on: Designing and building the core infrastructure that connects services across Canva's backend engineering org Leading a major migration of how our backend services communicate, working closely with partner engineering teams & leaders Driving support for more languages and frameworks so more teams can build natively on our platform Owning the reliability, performance and correctness of systems that sit in the critical path for the whole engineering org Mentoring engineers and helping raise the technical bar across
the team You're Probably a Match If: You've built and operated infrastructure that other engineering teams depend on, ideally something in the API gateway, RPC, or service mesh space (high traffic & large-scale). You're comfortable owning systems where reliability and correctness really matter, and you think in trade-offs rather than quick fixes You can drive a technical direction across teams that don't report to you, and communicate it clearly to both engineers and the teams who consume what you build You take genuine ownership of outcomes, and you're motivated by platform work that quietly makes everyone else's job easier You've spent years owning large-scale, high-transaction production systems commercially, and ideally worked in more than one language along the way.
