Director, Platform Engineering

Build better healthcare together

Maple’s purpose is to meet the world’s healthcare needs. We’re Canada’s leading on-demand healthcare platform, connecting patients with Canadian-licensed doctors, nurse practitioners and specialists. Today, we’re proud that over 8 million patients and 7,000 businesses and government partners have access to same-day, proactive and ongoing care. We enable people to take control of their health and push the boundaries of what’s possible every day.

Bold minds. Big impact. A career at Maple is about making an impact. We empower bold thinking, surround you with an inspiring team and are driven by a motivating purpose. Here, you’ll do work that changes lives—including your own.

As we grow, expand into new products, and prepare for scale, the engineers building Maple's products need a foundation that lets them move fast, safely, and autonomously. We’re looking for a Director, Platform Engineering to build that foundation — and lead the team behind it. That’s where you come in.

In this role, you’ll stand up a new team whose customer is every other engineer ’ll own the developer experience end to end: CI/CD, deployment automation, observability, AI-assisted development tooling, test infrastructure, and the developer‑facing infrastructure layer. This is a chance to define a platform mandate from scratch, partner directly with the VP of Engineering and CTO, and shape how Maple's engineering team builds software as we scale.

The work you do here will compound — every hour your team saves a product engineer is an hour that goes back into the patient and provider experience.

• Own the platform engineering team's mandate end-to-end: developer environment, CI/CD and deployment pipelines, test infrastructure and quality tooling, framework and dependency health, AI tooling for engineers, and the AI feature tooling stack
• Serve Maple's product engineering squads as your primary customer — publish a platform roadmap, run developer surveys, and make prioritization calls based on developer friction data
• Drive engineering metrics in partnership with the VP of Engineering — stand up the tooling to measure developer experience, define the quantitative baselines, and set the roadmap to move them
• Hire, coach, and grow a small team of engineers, and set the operating model, rituals, and career expectations for the team
• Partner across Engineering, Business Technology, Security, Data, and Product to lead change — from shifting the org from manual to continuous deployment, to raising the bar on quality, observability, and incident response
• Stay hands‑on where it matters: architecture reviews, prototyping, and unblocking your direct reports — while making sure the platform team stays a thin, high‑leverage layer rather than an over‑engineered one
• Translate platform investment into business outcomes for non‑technical executive leaders and connect the team's roadmap to Maple's growth priorities

In your first 90 days, you’ll have published a clear operating model and quarterly roadmap, and launched a baseline developer experience survey with a live metrics dashboard. You’ll have built the hiring plan paired with roles and responsibilities for any open positions, and shipped a first handful of quick wins for the Product Engineering squads.

In the following 12–18 months, you’ll have moved Maple to continuous deployment on both backend and frontend, established a framework upgrade cadence that keeps the stack healthy, and matured E2E test infrastructure that runs on every PR. You’ll have formalized incident management and an on‑call rotation, matured our agentic engineering tooling, and put an AI evaluation harness in place. DORA metrics will trend into the "elite" range, developer experience survey scores will be measurably up, and the PR cycle time and code review burden will be measurably down — with the data to prove it.

• 5+ years of people leadership experience in engineering, including 2+ years building or leading a platform or developer experience team
• Director‑level operating experience — you've owned a multi‑domain technical roadmap and…