Product Manager

SS&C Technologies provides AI-powered technology and services for financial services and healthcare organizations. The company is seeking a Senior Product Manager to own the vision, roadmap, and delivery of its Enterprise Ontology Platform, align dependencies with the Foundational Data Platform, and translate business and regulatory needs into scalable product capabilities.

Responsibilities:

• Define the product strategy: translate business goals into a multi-year vision for the ontology platform, moving from initial build-out to a mature, self-service ecosystem
• Own the end-to-end product roadmap, balancing the delivery of immediate business wins (specific data source mappings) with long-term platform scalability (configurable rules engine, improved break-detection)
• Convert ambiguous or conflicting business needs into detailed product requirements, user stories, and acceptance criteria that a team of 5-6 engineers can execute against without significant back-and-forth
• Manage the backlog using a data-driven approach, weighing trade-offs between new feature development, technical debt, and production support
• Define and track success metrics for the platform (e.g., onboarding time for new sources, break resolution rates, mapping coverage) and use them to inform prioritization
• Serve as the primary point of contact between the ontology platform and the Foundational Data Platform team's engineering leadership. There is no dedicated product function on the foundational platform side today, so this role carries dual responsibility: representing the ontology platform's needs and helping shape/prioritize foundational platform capabilities on its behalf
• Proactively identify capability gaps between what the foundational data platform provides and what the ontology platform requires
• Lead build-vs-leverage analysis: decide whether a needed capability should be built bespoke within the ontology layer, or whether it makes more sense to advocate for a generic capability on the foundational platform for broader enterprise benefit, and drive that decision through to prioritization on whichever roadmap it lands on
• Given the absence of a counterpart PM on the foundational platform side, take ownership of articulating foundational platform requirements clearly enough for its engineering team to plan against, effectively acting as the voice of the business need on both sides of that boundary
• Track dependencies on the foundational data platform's roadmap and proactively flag risks to the ontology platform's own delivery timelines
• Ensure the platform provides a flexible, extensible framework for capturing and evolving ontology definitions (entities, relationships, attributes) that are defined and owned by the business teams themselves, not by product or engineering
• Understand business users' needs for managing mappings and rules, and work collaboratively with the Engineering Lead to shape the configuration workflow and interaction model, influencing design decisions through business context rather than owning UX design directly
• Design the workflow for how data breaks (discrepancies between source data and ontology) are surfaced, triaged, and resolved by business users
• Partner with Data Governance and Compliance teams to ensure the ontology capture framework and mapping processes align with enterprise data standards and regulatory expectations
• Act as the primary product-facing point of contact for business stakeholders across a variety of use cases, gathering requirements, understanding pain points, and setting expectations on delivery
• Facilitate alignment across business teams with differing definitions or requirements for the same underlying data concepts
• Communicate roadmap, trade-offs, and progress to business and senior stakeholders in terms they can act on
• Participate in technical design discussions as the product/business voice, and constructively challenge engineering approaches when needed, ensuring proposed solutions solve the underlying business problem
• Plan for and track dependencies on business teams for ontology definitions, mappings, and rules/breaks criteria, since these are inputs the business teams themselves own and must provide; proactively identify what is needed from each team, by when, and escalate when business-side input is at risk of slipping and blocking delivery
• Build these business-dependency timelines into the roadmap alongside engineering delivery timelines, so the platform's schedule reflects both engineering capacity and the pace at which business teams can define and validate their ontology inputs

Requirements:

• 5-8 years of Product Management experience, specifically within data-intensive platforms (e.g., MDM, Knowledge Graphs, Data Mesh, or Enterprise Data Warehousing)
• Deep understanding of data modeling concepts. While coding is not required, you should be comfortable discussing graph databases (RDF, SPARQL, Property Graphs), APIs, and ETL/ELT patterns with engineers
• Proven track record of managing a platform-on-platform dependency: experience working with a separate infrastructure/foundational team to enable a higher-level product
• Ability to navigate complex, messy data environments and synthesize a clean, canonical structure from conflicting source definitions
• Exceptional stakeholder management skills: able to communicate credibly with both a deep-technical engineering lead and non-technical business executives
• Familiarity with ontology standards (OWL, RDF) or experience building a Knowledge Graph
• Experience with metadata management tools or data cataloging software
• Experience in Financial Services or another highly regulated industry, where auditability and data correctness are non-negotiable, is strongly preferred
• Experience leading a team through the "0 to 1" phase of a product launch within a large corporate environment (a plus, not required)