Your career compass awaits
Create a free account to unlock
- ✓ See how you match this role
- ✓ AI resume tailored to this specific job
- ✓ Inside Track Companion — find your insider contact
- ✓ Skills gap analysis and upskill plan
- ✓ Interview prep kit for this role
- ✓ Relocation concierge — salary, tax, cost of living
Free — no credit card required
Canva
✓ Verified SponsorConfirm Application
Are you applying to ?
We'll track this in your dashboard as Applied.
Staff Production Engineer
ICT
Company shared salary
NA
Market rate
A$18,333–A$25,000/mo (A$219,996–A$300,000/yr)
Based on similar roles (title + domain + location).
About the Company
Join the team redefining how the world experiences design. Hey, g'day, , 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. Writing software that changes how production behaves at 240M MAUs and growing. 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 it lands 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 improve the software to make it more reliable, more efficient, and more resilient. At the moment, this role is focused on: 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.
Requirements
- ● Production at scale: Owned reliability work within large-scale distributed systems. When things broke, you wrote the fix, not the ticket.
- ● Embedded delivery: Previously worked as an engineer embedded in or partnering closely with a product or feature team, not siloed in a platform org that throws tools over the fence.
- ● JVM or systems depth: You've built real things in Java, Go, Rust, C++, or a comparable systems language at production scale; commercial depth, not academic familiarity. We're language-flexible for the right engineer, but you need to show up and win the technical duel in the first meeting
- ● Distributed systems in practice: Navigated sharding, replication, failure modes, consistency tradeoffs in real systems.
- ● Debugging large codebases: Ability to parachute into an unfamiliar codebase, orient quickly, find where the problem actually lives, and fix it.
- ● Influence without authority: Proven to have made things better in systems through wisdom and trust.
- ● Networking Depth: You know the network stack and what traffic looks like a scale.
- ● Linux internals: Enough kernel-level understanding to reason about what's actually happening when a system misbehaves process scheduling, memory, I/O, network stack.
- ● Distributed systems patterns: Consistent hashing, leader election, consensus, backpressure, circuit breakers.
- ● Observability tooling: You've instrumented systems for real, built the tracing, the dashboards, the alerting that actually tells you what's wrong. You understand the difference between causal and symtom based alerting and know what a good SLO looks like
- ● Containerisation and orchestration: Kubernetes at production scale, you understand what happens at the scheduler level.
- ● Performance analysis: You've profiled JVM applications or systems-level processes, found the thing nobody was looking at, and fixed it in a way that lasted.
- ● Cloud infrastructure: AWS at meaningful depth, so you understand how they behave under load and at the edges.
- ● Incident response in practice: You've been on-call in a serious production environment and have opinions about what good incident management actually looks like.
- ● Enterprise SaaS background: You've done this specific kind of work at an org that's done it well. You know what "production engineering" means when it's not just a job title.
- ● JVM internals: You've tuned GC and profiled threads in production.
- ● Multi-region or sharding experience: You've been involved in a data store migration or multi-region architecture where getting it wrong was not an option.
- ● eBPF or kernel instrumentation: Production experience is valuable experience.
- ● Equity packages - we want our success to be yours too
- ● Inclusive parental leave policy that supports all parents & carers
- ● An annual Vibe & Thrive allowance to support your wellbeing, social connection, office setup & more
- ● Flexible leave options that empower you to be a force for good, take time to recharge and supports you personally
⚡ Full Resume Sandbox Canvas