Canva
Principal Production Engineer
Remote role where the employee must remain based in a particular country.
Australia only
From the listing details: Source listing states candidate location: "Adelaide, SA, Australia, Adelaide, SA, au, Remote"
Employer listed it 2 months ago · Added 8 weeks ago
Listed for 51 days before it closed.
This job has closed
Canva has taken this listing down, so it is no longer accepting applications. The details below are kept for reference only.
Browse open rolesSalary
Not stated
Location
Australia only
Timezone
APAC
Contract
Full-time
Experience
Lead
Category
Software
The employer did not publish a salary, and we have too few comparable roles to estimate one.
What the advert says
Quoted word for word from the employer's advert. Where it says nothing, we say so.
- Working hours
- Not mentioned in the advert
- Where you can work from
- Location eligibility not confirmed
- Contract
- Not mentioned in the advert
- Experience asked for
- Not mentioned in the advert
- Pay
- Not mentioned in the advert
Remote flexibility
Work from home
This is a remote role, but the employee must be based in Australia. It is work from home rather than work from anywhere.
What the employer says
- Source listing states candidate location: "Adelaide, SA, Australia, Adelaide, SA, au, Remote"
What Nomaders makes of it
- Residency required in Australia
- Payroll and tax are likely handled in that country only
The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.
Before you apply
Questions worth asking: Nomaders interpretation
- The advert does not say where you can be based. Ask which countries they can legally employ or contract you from.
- No pay is stated. Ask for the salary range before investing time in interviews.
- The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.
Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.
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.
What you'd be doing in this role
The Production Engineering team sits at the intersection of software engineering and the hardest reliability problems in Canva's infrastructure. At 240M MAUs, the hardest problems aren't on any product roadmap. Production Engineering exists to find them first and fix them properly. Writing software. Changing how production behaves. When it works, every team ships with more confidence and Canva gets faster and more resilient for the people who use it every day.
The strategic bet is a different model entirely. Canva's own take on what production reliability looks like, built for how we work. Senior software engineers embedded long-term in the areas that carry the most technical risk, working shoulder to shoulder with product teams, close enough to the roadmap to shape how features land in production before the problems compound. Not operationalising systems. Not running alerts. Writing software that changes how production behaves.
The engineers who do this work well have gone deep in systems most people only operate. They can walk into a codebase they didn't write, understand what's actually happening at scale, win the technical respect of the team they're embedded with, and then bend the software to make it more reliable, more efficient, and more resilient.
At Principal level, you're also the person who defines what this practice looks like at Canva. The calibration anchor for every hire, every engagement, and every standard the team sets.
At the moment, this role is focused on:
Defining the engagement model: How Production Engineering pairs with product and infrastructure teams, how engagements are scoped, and what handoff actually looks like. This model is new. You're shaping it.
Leading the hardest engagements: Taking personal ownership of the most technically complex areas, sharding, multi-region architecture, JVM performance at scale, while the team builds depth in adjacent domains.
Setting the technical bar: What it means to be a production engineer at Canva. The standard for technical credibility. The archetype that future hiring calibrates against.
Pairing strategy across the team: Deciding how staff and mid-level engineers are paired and what they should be learning from each engagement. Growing production engineering capability across the org, not just within the team.
Connecting to the product roadmap: Working with engineering leadership across Canva to ensure Production Engineering is upstream of problems, not downstream. Influencing how product teams think about production readiness before they ship.
Building the measurement story: Incident severity and duration trending down. Feature launches going to production cleanly. You define what the metrics are and how they're tracked.
Compounding at organisation scale: One well-placed Production Engineering engagement changes how engineers build for years. At Principal level, your leverage is the sum of all those engagements, plus the standard you set for how each one runs.
What success looks like:  As a secondee, developing trusted relationship with your team. Guiding them towards, shipping at velocity, with more confidence and less toil.
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
Production at scale: You've owned reliability in large-scale distributed systems. When things went brake, you investigate how and shipped the solution that lasts forever.
Technical leadership in embedded models: You've led or helped shape a function where engineers work across team boundaries rather than within a single one. You know what makes that model work and what makes it fail.
Hands-on through seniority: You've stayed close to the code. At this level, you're the engineer others consult when the problem is genuinely hard.
Cross-org influence: You've shaped how teams outside your own make technical decisions because your technical judgement is trusted.
Requirements
The employer hasn't listed requirements separately, they're described in the role summary above and on the original listing.
Benefits
No benefits package published with this listing. Ask about it at first interview.
Applying
This listing has closed, so there is no application link. The details above are kept for reference only.
Found 2mo ago. Last checked 1 Nov. Always confirm the details on the original posting, salary and location can change after publication.
Listing sourced from Company boards.
This role is closed, applications are no longer accepted.