Staff Software Engineer - Experiments Platform (AU remote)
Canva
- Location
- Sydney, , Australia
- Employment
- Full Time
- Work model
- Remote
- Level
- Staff
- Posted
- 1h ago
Skills
About this role
Company Description
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.
Job Description
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: Canva is making experimentation a much bigger part of how we build and ship product. At our scale, shipping changes and watching what happens isn't enough. Teams need to know whether a change actually improved the product and catch changes that unexpectedly hurt important guardrails such as retention or application performance. This Staff Software Engineer will provide senior technical leadership across the backend systems behind Canva's experimentation programme. You'll help evolve the platform teams use to set up experiments, target users, expose variants and measure outcomes in the safest and most intuitive way possible. We're moving towards a platform that does more than report results. It should reinforce good experimentation practices, surface signals faster and alert early when things go wrong. With the advent of AI, we’re also looking at how we can automate more of the analysis process to help our teams learn faster and iterate. You'll take ownership of significant technical problems, work with senior leaders across Canva and help shape where the platform should go next by working with the teams building the platform. 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 the team, we're invested in helping you grow.
Experience
Backend platform engineering: You've built backend systems or platforms that other engineers depend on, and understand what changes when your software becomes part of somebody else's critical path. Experimentation exposure at scale: You've built, operated or worked deeply with experimentation, A/B testing, feature-management or progressive-rollout systems in a large engineering environment. Technical leadership: You've taken ambiguous engineering problems, formed a technical direction and helped other engineers move towards an outcome. Driving adoption: You've built internal platforms or capabilities and understand that the technology only succeeds when other teams trust and use it. Technical knowledge: Backend and distributed systems: Strong software engineering fundamentals, with experience designing reliable backend systems and reasoning about scalability, availability, consistency and failure modes. Data systems: Enough familiarity with data engineering, analytics engineering or large-scale data processing to understand how experimentation data is generated, moved and consumed. Experimentation concepts: Familiarity with experiment assignment, targeting, variants, feature flags, metrics, guardrails and progressive rollout. Language depth: Java is our primary language and would be useful, but it isn't a hard requirement. At Staff level, we're more interested in strong engineering fundamentals and your ability to transfer them between languages.
Nice to haves
You've built this before: Direct experience designing or building experimentation, A/B testing, feature-management or rollout infrastructure — either inside a large technology company or for a platform vendor. Data crossover: A background spanning software engineering and data science, data