Director of Product — Ecosystem

Job description

Caseware is one of Canada's original Fintech companies, having led the global audit and accounting software industry for over 30 years, with more than 500,000 users across 130 countries and available in 16 different languages. While you might not have heard of us (yet) over 36,000 accounting and audit professionals list Caseware as a skill on their LinkedIn profiles! The Director of Product, Ecosystem leads Caseware’s third-party ecosystem strategy and owns the roadmap for the ecosystem product surface — the requirements for interoperability capabilities, connectors, marketplace, and developer tooling through which third parties connect to Caseware. As Director of Product, Ecosystem, you will understand the technology solution landscape and the priority of partnerships and integrations with technology vendors, own the build, buy, or partner framework applied to ecosystem capability decisions, and design the partner program that governs intake, certification, and the marketplace. You will lead on ecosystem strategy, on the interoperability requirements and integration workflows Caseware supports, on the marketplace, and on the third-party developer experience. The role reports to the VP, Product — Enterprise Solutions & Ecosystem. ❗This is a Full-time permanent position ❗This is a new position 📍Location: This is a hybrid role requiring the successful candidate to work 3 days a week in our Toronto office, located at 351 King St E, Suite 1100, Toronto, ON. ### What you will be doing: Third-Party Ecosystem Strategy - Lead Caseware’s third-party ecosystem strategy and keep it current as the market moves. - Understand the technology solution landscape and the determine the priority of partnerships and integrations across customer integration use cases and third-party technology integrations - Bring the evidence behind those decisions: firm technology-stack data, customer demand signals, and competitive position. - Set out the strategy for senior leadership and the trade-offs within it. Ecosystem Product Surface - Own the roadmap for the ecosystem product surface – inclusive of interoperability capabilities, integrations, connectors, marketplace, and developer tooling. - Identify and communicate delivery risks against the roadmap. - Own the marketplace as a product surface, including how partners and their capabilities are presented and discovered. - Decide what enters the ecosystem surface and what is deprecated. Build, Buy, or Partner Framework - Own the build, buy, or partner framework and apply it to ecosystem capability decisions. - Maintain the classification that determines whether a capability is built, acquired, or partnered. - Produce the analysis and recommendation behind each decision, including the case for the option not taken. - Take recommendations through to a decision with senior leadership, working with corporate development and finance where the answer is to acquire or invest. Interoperability Requirements and Integration Workflows - Lead the understanding of what interoperability capabilities customers and partners need and translate it into product requirements – inclusive of Agentic Interoperability - Define the integration workflows Caseware supports, and the technical standards an integration must meet. - Manage integrations as products, with defined adoption targets, quality expectations, and support models. - Recruit and run design partners to validate integrations before general availability. Third-Party Developer Experience - Lead on the experience of third parties building against Caseware, and inform the product requirements for the APIs, SDKs, documentation, and tooling they use. - Define what self-service onboarding looks like for a partner or customer developer. - Advocate for the platform capabilities the ecosystem surface depends on, including security, performance, and extensibility. Partner Program Design - Design the partner program, covering intake, evaluation, certification, and the marketplace. - Set the bar a partner must meet to be certified, and the criteria applied at intake. - Define partner onboarding and enablement so partners can integrate at scale - Define the operating model for the program, including governance, tooling, and reporting cadence. Working with Engineering - Partner with engineering on interoperability requirements, technical standards, and sequencing. - Provide the customer and market context behind each requirement, not only the requirement. - Surface trade-offs and constraints that affect roadmap commitments, and agree the path through them. Commercial Collaboration - Provide the product and technical position into partner contracting and negotiation. - Contribute to the ecosystem monetisation model, including marketplace, referral, and revenue-share approaches. - Work with Legal on NDAs, term sheets, and the technical terms of partnership agreements. Go-to-Market and Customer Enablement - Work alongside Sales, Support, and Marketing on go-to-market for ecosystem capabilities.