Job Description Join the team redefining how the world experiences design. Hello, 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 office is in Sydney, Australia, but we've made our way from down under to a hub in San Francisco, which is now home to our US operations. We offer flexibility in how an
About the role
Job Description Join the team redefining how the world experiences design. Hello, 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 office is in Sydney, Australia, but we've made our way from down under to a hub in San Francisco, which is now home to our US operations. We offer flexibility in how and where you work. We trust our Canvanauts to choose the balance that empowers them and their team to achieve their goals. About the role Video is the most resource-hungry thing Canva does. Every layer of it costs something: the browser, the phone in someone's hand, the native engine underneath, on-device ML, and the backend pipelines behind all of it. As a Staff Software Engineer on the Video Performance team, you'll own how fast all of that actually feels. You'll decide what good performance means for Video, build the measurement that makes it visible, then lead the work that moves the numbers. That work runs across product surfaces, our cross-platform Native Video Engine, the Effect Platform, on-device ML and backend services. Deep expertise in one of those layers is a good place to start from. What matters most is being able to follow a slow user journey wherever it leads, and leaving behind tools that let other engineers do the same. Most of our users are on mid-range and older devices. Keeping the experience fast for them, while the group keeps adding AI features and high-fidelity effects, is the genuinely interesting part of this job. 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 a flavour of the type of things you'll be working on when you start, but this will likely evolve. Own performance across the whole video creation lifecycle: template load, media import, timeline scrubbing, real-time preview, effects and export, on web, iOS and Android. When a bottleneck turns out to live in someone else's layer, you follow it there. Define the performance metrics and service level objectives for Video, and make sure they track what people actually notice rather than what happens to be easy to measure. Build the telemetry, tracing, dashboards and alerting that keep video performance visible, including regression detection that catches problems before users feel them. Build the profiling and benchmarking tooling: traces, device labs, automated performance suites. The goal is that any engineer in Video can diagnose a slow path without waiting for you. Ship measurable improvements to latency, frame stability, memory and battery life. Sometimes that means a product or pipeline change. Sometimes it means critical-path work in the native engine, the shaders, or the ML-powered effect pipelines. Work with the Native Video Engine, on-device ML and Editing teams to rework hot paths for better parallelism, caching, hardware acceleration and asynchronous processing. Help the rest of Video treat performance as part of the product, rather than something to tidy up afterwards. You're probably a match if You've made real systems measurably faster, and you can talk through the numbers. You move comfortably between product code, backend services and native or platform layers, and you can find your bearings in an unfamiliar stack. You've built performance tooling that other engineers came to rely on: profilers, tracing and instrumentation, benchmarking harnesses, regression suites or telemetry pipelines. You're at home in tools like Perf, Instruments, Perfetto, Android Studio Profiler and Chrome DevTools, and happy to build your own when none of them fit. You can define a metric that means something, read telemetry at scale, spot a regression, and prove an optimisation worked. You understand concurrency, memory behaviour and CPU and GPU cost mo