Product Owner

Canada
Remote
Posted Oct 15, 2026
1 position

Opens LinkedIn

Employment type: Contract
Experience level: Mid-level · 2+ years
Posting language: English
Working hours: 40 hours per week
Seniority: Associate
Application method: Direct apply is available

Job summary

Serve as the primary liaison for requirements gathering across enterprise teams supporting the Passage and Manchester integration initiatives. Document and maintain integration requirements, system mappings, business rules, user stories, acceptance criteria, process flows, and design artifacts for Engineering.

Job details

Title: Product Owner Location: Remote The Product Owner will support the Passage and Manchester integration initiatives. This role would serve as the primary liaison for requirements gathering across Enterprise teams supporting Student Data Base (SDB), the system of record for student lifecycle and enrollment data; Partner Data Management (PDM), which manages program catalog and program configuration data; Salesforce; Databricks, Partner Integrations; and other organizational teams involved in the Passage and Manchester initiatives. Key responsibilities would include: Partnering with stakeholders across SDB (Student Data Base), PDM (Partner Data Management),Databricks , Salesforce, and Engineering to gather, document, and validate integration and data requirements. Understanding and documenting system schemas, including required versus optional fields, field definitions, mappings, business rules, and data transformations between systems. Identifying gaps, inconsistencies, and open questions between source system capabilities and downstream data requirements. Creating and maintaining user stories, requirements, acceptance criteria, process flows, Lucid diagrams, and Confluence documentation to provide Engineering with clear and actionable requirements. Keeping requirements, mappings, and design artifacts organized and up to date as integration designs evolve.

What you’ll do

Requirements

The role requires partnering with stakeholders across student data, partner data management, Databricks, Salesforce, and Engineering to gather, document, and validate integration and data requirements. It also requires understanding system schemas, identifying gaps and inconsistencies, and keeping requirements and design documentation current as integration designs evolve.