Staff Front-End Engineer - Telemetry

Requirements

• Telemetry at scale: Built or significantly evolved a frontend telemetry, observability, or instrumentation system in production.

Benefits

Additional Information

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 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. Every decision Canva makes about its product gets better when the people building it can actually see what's happening. Frontend Telemetry is the layer that makes that possible. Every click, every interaction, every page that loads, the data captured here is what tells the company whether the product is working, where it's slow, where users are getting stuck, and where the next bet should go. Hundreds of engineers across Canva depend on what this team ships. The decisions made on top of it shape the product. The strategic bet is a new telemetry SDK that gives every developer at Canva one consistent way to measure performance and reliability connected to user interactions. The aspiration is high: an SDK so well-designed that, in many cases, developers don't need to instrument anything at all. The data is just there. That's the ceiling this role is reaching for, and getting there means rethinking how instrumentation works from the ground up. There's a second reason this work matters now, and it's the part of the role that's genuinely new. AI-driven experiences bypass the traditional frontend. There's no click, no rendered UI to measure, no familiar interaction pattern to instrument. There's no settled playbook for measuring it yet, and the engineer in this seat will help shape one. Telemetry for AI-native experiences is frontier work, and that's the part of the brief that's hardest to find anywhere else. At the moment, this role is focused on: Building the SDK developers love: Easy to instrument, easy to reason about, easy to extend. The bar is an SDK so well-designed that, in many cases, instrumentation happens automatically and developers don't have to think about it. Get this right and every product team at Canva gets faster. Going deep into the browser stack: This is where the work earns its level. Performance APIs, the rendering pipeline, the network layer, the way the browser actually executes code. The candidates who land this role are the ones who think at that layer naturally. Defining how Canva measures AI: AI-driven experiences interact with users in ways traditional frontend telemetry doesn't capture. There's no playbook for this. The engineer in this seat shapes what good looks like. Owning the telemetry SDK direction: Set the architecture, the patterns, the path from where measurement is today to where it needs to be. Set the direction that helps other teams build. Rally the product teams behind the solutions. Leading with code, not whiteboards: Canva doesn't have an architecture function - Staff engineers stay hands-on. You'll live in the code, build the SDK, and push commits. Driving adoption across the product: Every product team at Canva eventually moves onto this SDK. That's a technical problem and an organisational one. You'll need the credibility to bring teams along, not the authority to mandate. Sparring with strong peers: The team is cross-functional by design - frontend, backend, data science, analytics engineering. The technical debate is rich, fast, and substantive. Bring strong opinions, change your mind when better evidence shows up. What success looks like: Every product team at Canva has the visibility they need to find and fix performance and reliability problems in their own code. The SDK is the default - adopted broadly, easy to reason about, deep enough to cover what matters. The patterns set by this role become the standard way Canva measures the frontend, including the way AI-native experiences are measured. You're probably a match if 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.