Principal Partner Engineer — Ecosystem

Join the team redefining how the world experiences design.

Thanks for stopping by. We know job hunting can be a little time‑conscious, and you’re probably keen to find out what’s on offer, so we’ll get straight to the point.

Our flagship campus is in Sydney. We also have a campus across the world and co‑working spaces in numerous locations in the USA. But you have a choice in where and how you work; we trust our Canvanauts to choose the balance that empowers them and their team to achieve their goals. You’ll work on Pacific Time hours and collaborate daily with Canva’s engineering teams in AEST.

Canva’s Ecosystem platform sits at the centre of how the world’s agentic AI systems connect to visual design. Anthropic, OpenAI, Google, Microsoft, Meta, and the next wave of AI‑native platforms are all building on, against, and through our MCP server, REST APIs, and Apps platform. The shape of those integrations is being decided right now, at the engineering layer, in real conversations with real technical counterparts.

• Drive decisions and alignment across Partners and Canva engineering. When a partner proposes a solution that won’t work, you’ll explain why, generate the realistic option set, and drive it to a decision with the owning Canva teams. You’ll hold the technical detail on both sides and translate without losing precision.
• Set technical direction for Canva’s external platform surface. The strategic question of where to invest, deprecate, and evolve doesn’t sit inside any single team. You’ll contribute to that direction, grounded in partner signal and engineering reality.
• Ground partner conversations in working code. At this level, partner conversations need to be grounded in what’s actually runnable. You validate proposed solutions against Canva’s real architecture to drive decisions that span multiple teams and partners, using working code as the proof point. When it helps unblock a decision, you’ll sketch what a change could look like in code, giving the owning Canva team a concrete starting point while leaving the change itself to them.
  
  The outcome is a partner decision backed by a runnable artifact.
• Drive product‑line engineering across our external platform surfaces. Canva’s agentic AI story is delivered across MCP, REST APIs, Apps‑in‑Canva, and the middleware PaaS. You’ll work across all of them, making sure the overall surface stays coherent as new capabilities land. This is the product‑line engineering layer that today falls between teams.
• Carry the platform direction outward early. Canva pivots on a dime. You’ll sit inside Ecosystem engineering leadership, hear direction as it forms, and carry it to partners before they’re reacting to it. This is the single highest‑leverage thing the role does for GTM.
• Shape strategic partner and customer engagements. For a small number of flagship engagements (major AI platforms, and at a stretch, strategically significant enterprise customers), you’ll lead the technical relationship end‑to‑end: shaping the roadmap, driving the spikes, carrying the decisions back through Canva.

You’ll hold product shape, engineering feasibility, and partner intent in the same conversation. In a single afternoon, you might move between a product‑roadmap discussion, an API design review, and a partnership alignment call, and bring each of them closer to resolution.

• You have 10+ years of software engineering experience, with several of those in roles operating at the seam between partner engineering, platform engineering, and product.
• You’ve built developer platforms, not just evangelised them. You’ve shipped code in production on platforms used by external developers.
• You move fluidly between a product roadmap conversation, a system design discussion, and a partner negotiation, and you bring each one forward.
• You bring a prototype or sample code to a hard conversation. You don’t oversell what’s doable, and you don’t overbuild what isn’t needed.
• You’re technically deep on the modern AI platform stack. You have real opinions on MCP, tool‑use, agentic API design, and the tradeoffs between them.
• You…