Location: REMOTE / Toronto, Ontario
This job allows you to work remotely.
PARTNER IMPLEMENTATION LEAD. Remote within Canada, occasional travel to partner sites. Reports to Head of Implementation. $130,000 to $160,000 CAD plus equity.
ABOUT THE COMPANY. Our client is a Canadian embedded insurance platform. Banks, telecoms, fintechs, neobanks and consumer brands use them to put insurance directly inside the products their customers already use, rather than sending those customers off to a broker. What wins them deals is time to market: building this in-house means years of carrier negotiation, licensing and compliance groundwork, while through this platform a partner can be live in about a quarter. They hold the carrier relationships, run a modern API-driven platform built to be worked by both engineers and AI agents, and carry SOC 2 Type 2. The business is growing quickly and moving into the US market, and the implementation function is being built out to keep pace.
THE ROLE. You will own partner projects end to end, from requirements through launch and into the first thirty days in production. This is a job about ownership and communication. You know what it takes to move something from an idea to a shipped product, and you are fluent in how software actually gets built. You can follow how a solution fits together, ask engineers questions worth answering, and explain the trade-offs to a partner who is not technical. Curiosity matters here more than any single credential. Over time you become the person who knows more about your projects than anyone on either side.
You are the constant across the life of a project. Alongside you sit a technical and product owner holding the vision, an engineering team building against it, product and design shaping the flows, and a solutioning function holding the early partner context. You carry the project the whole way, so the partner deals with one person who knows their history rather than a chain of handoffs. This is as much an internal job as an external one: keeping your own teams aligned and unblocked is what makes the partner-facing half work.
WHAT YOU WILL OWN. Lead partner projects from requirements through launch, accountable for timeline, scope and outcome. Take a directional solution and sharpen it into something engineering can build. Run the delivery mechanics so status is never guesswork. Map dependencies across every party and keep them visible. Carry the KPIs agreed at solutioning into the build and make them measurable from day one. Be the named contact for your partners. Set expectations with senior people on both sides. Keep partners, insurers and third-party providers working from one shared view. Hold every party to what they signed up for and escalate early. When scope moves, name it and put the decision in front of whoever should make it. Own readiness for go-live: configuration, access, support model, monitoring and escalation. Stay accountable through the first thirty days live, then hand over to the account team.
WHY IT IS WORTH A CONVERSATION. Implementation is being built into a centre of excellence and you would join early enough to shape it. The partner list is genuinely enterprise, major banks, national telecoms and well-known consumer brands, at a company of under thirty people, so you get the logos without the layers. Remote-first in practice, flexible hours, nothing tracked. In exchange there are real spikes around a partner go-live.
Must Have Skills:
Five or more years delivering technical projects for external clients or partners: functional consulting, B2B SaaS implementation, or product and project management in a product company or development shop. Delivery must have been for external clients, not internal programmes.
Owned a full delivery lifecycle, discovery and requirements through go-live and post-launch support.
Strong communication, with the persistence and warmth to hold a partner to a date and still be welcome on the next call.
Senior stakeholder management across both legacy institutions and digital-first companies.
Real grounding in the software development lifecycle: knows where things break and what a realistic timeline looks like.
Comfort with technical integrations. Reads API documentation, follows data across systems, holds their own with engineers. Six or seven out of ten technically, not eight.
Track record of becoming the go-to person on what they deliver.
Translates business requirements into something engineering can act on.
AI-first way of working, using AI as a working thought partner and verifying output. Anything at or below consumer chat use is a fail. There is a practical exercise in the process.
Comfort with ambiguity and the judgement to propose a direction rather than wait for one.
Serious planning discipline across a multi-party plan, with accurate status on demand.
Runs several projects at once and prioritises between them.
Highly organised, arrives with a proposed plan rather than open questions.
Shortcut, Jira or Linear, plus Slack, Google Workspace, Figma, and AI tooling such as Claude, Cursor or Lovable.
Nice to Have Skills:
Insurance familiarity, especially creditor insurance, payment protection or other regulated financial products.
French or Spanish, written and verbal.
Prototyping ability: mapping a user flow and building something clickable to align stakeholders.
Hands-on development experience, or enough time near a codebase to reason about implementation trade-offs.
Product ownership: specification writing, backlog management, scope calls.
SQL, or general comfort getting their own data out.
Shipped into large regulated institutions without letting the pace collapse.
Digital consultancy or product studio background, with one move already made into a startup or scale-up.
Multi-party integration experience across a client, a vendor and an internal team.
