> Markdown version of [/jobs/ext/2956702-staff-software-engineer-video-performance](https://www.wearedevelopers.com/jobs/ext/2956702-staff-software-engineer-video-performance). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Staff Software Engineer - Video Performance - **Company:** CANVA L.C. - **Location:** San Francisco, CA, United States - **Salary:** $262,000.0 - $329,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Android Software Development, Android Studio, C++ (Programming Language), Mobile Application Development, Profiling, Codecs, FFmpeg, OpenGL, Open Source Technology, Performance Tuning, Backend, Perf (Linux), HLSL, Hardware Acceleration, TensorRT - **Published:** September 17, 2026 - **Apply:** https://startup.jobs/staff-software-engineer-video-performance-bay-area-only-canva-2-10087326 ## About the Role * Hands-on iOS or Android development focused on system-level performance (strongly preferred): UI responsiveness, startup, memory, battery and thermal behaviour, especially on low-end Android devices. Having built native apps, players or editors yourself counts for a lot here. * Proficiency in C++, or a comparable systems language such as Rust, optimising critical paths in a native engine, plus familiarity with graphics APIs (OpenGL, Metal, Vulkan, WebGPU) and how rendering choices affect frame times. * On-device ML performance work, such as tuning inference latency with CoreML, TFLite or TensorRT, or WebAssembly performance tuning for heavy compute in the browser. * Contributions to open-source multimedia or graphics projects such as FFmpeg or Chromium. ## Description 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. This is a full-stack performance role, anchored in the client. 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 web and mobile surfaces, our cross-platform Native Video Engine, the Effect Platform, on-device ML and the backend services behind them. 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: 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, playback, 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 measurement layer underneath that: telemetry, tracing, dashboards, alerting and regression detection, plus the profiling and benchmarking tooling, traces, device labs and automated performance suites, so 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, wherever the data points. * 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, and get Video treating performance as a product feature rather than cleanup work. You're probably a match if: * You count every millisecond, byte and milliamp, and you've made real systems measurably faster. You can talk through the numbers. * You've built at the client layer, on web, mobile or native, and you can follow a problem down into backend services or platform code when that's where the time is going. You find your bearings in an unfamiliar stack quickly. * 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, happy to build your own when none of them fit, and you can define a metric that means something, spot a regression and prove an optimisation worked with data rather than intuition. * You understand concurrency, memory behaviour and CPU and GPU cost models well enough to explain why something is slow, not only where. * You have a working understanding of video pipelines: playback, codecs, container formats, frame-accurate seeking and composition. Or the appetite to pick it up quickly. * You prioritise by user impact, starting with the journeys people use most on the devices that struggle most, and you can influence engineering teams you don't own, across time zones, to get that work landed. ## Related Videos - [WeAreDevelopers LIVE - Speeding up with WebGPU](https://www.wearedevelopers.com/videos/1876-wearedevelopers-live-speeding-up-with-webgpu) - [AI vs Recruiters and Applicants, Turmoil in the Games Industry, What to Put on a CV](https://www.wearedevelopers.com/videos/1363-ai-vs-recruiters-and-applicants-turmoil-in-the-games-industry-what-to-put-on-a-cv) - [Agents, Version Control and Bunnies - Daniel Siegl & David Payr](https://www.wearedevelopers.com/videos/1897-agents-version-control-and-bunnies-daniel-siegl-david-payr) - [3x Performance: A Humbling Journey](https://www.wearedevelopers.com/videos/100165-3x-performance-a-humbling-journey) - [Building Better Apps with React Native](https://www.wearedevelopers.com/videos/1466-building-better-apps-with-react-native) - [WeAreDevelopers LIVE - Demo Time, Live Coding, End-to-End Testing and more](https://www.wearedevelopers.com/videos/1713-wearedevelopers-live-demo-time-live-coding-end-to-end-testing-and-more) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 103 - Superb Owl Trafficking](https://www.wearedevelopers.com/magazine/388-dev-digest-103-superb-owl-trafficking) - [How Much FAANG Companies Actually Pay Software Engineers in 2025](https://www.wearedevelopers.com/magazine/230-how-much-faang-companies-actually-pay-software-engineers-in-2025) - [Dev Digest 130 - The Diablo is in the details](https://www.wearedevelopers.com/magazine/470-dev-digest-130-the-diablo-is-in-the-details) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)