Sr Director, Commercial Product Management

FIS•Jacksonville, FL

1d•$187,270 - $318,360

About The Position

Sits within a newly acquired startup building an AI-enabled, autonomous banking platform for Tier-1 financial institutions within the banking group. The Sr Director, Commercial Product Management role is the single-threaded product owner for Enterprise Customer — one trusted record of every person, organization, relationship, identifier, and consent the bank needs to serve customers, deployable standalone against any third-party core. Requires deep customer-master, identity, and consent expertise, an engineering foundation, and end-to-end ownership of what we build and why. The component is a natural first move in bank modernization and is deployable standalone. This is not a program- or delivery-management role: client-program orchestration sits with the Forward Deployed team, and engineering owns architecture and implementation.

Requirements

Deep, hands-on expertise owning a customer master, party/identity service, CIF modernization, KYC/onboarding platform, or MDM program — with personal ownership of the data model and integration pattern.
Working command of party and relationship modeling, beneficial ownership and corporate hierarchies, identity resolution, consent and agreement versioning, tax certification (W-9, W-8, CRS), ISO 20022-aligned identifiers, and privacy-law erasure.
Practical exposure to coexistence beside a legacy core (external-ID mapping, events replacing nightly extracts, parallel running) and multi-jurisdiction configuration. Strongly preferred: deploying a customer master standalone in front of a third-party core.
4+ years owning a technical product or platform end to end, including at least one taken personally through launch, adoption, and iteration.
Engineering background or equivalent hands-on record: typically 3+ years building, shipping, and operating production software — not coordinating its delivery.
Fluent in APIs, event-driven and distributed systems, data and state modeling, reliability, security, and observability; reads architecture diagrams without a translator.
Strong ownership mindset — owns outcomes, not tasks; a product owner who ships, not a requirements librarian. High agency; writes the playbook when none exists.
Technically credible and commercially grounded — earns trust with senior engineers, bank onboarding, KYC, and customer-operations leaders, data and privacy officers, and financial-crime teams, and executives. Clear writer: turns complex rules into decisions that are hard to misinterpret.
AI-native — uses analytics, telemetry, and AI-assisted workflows as the default operating mode for discovery, prototyping, documentation, and decisions, not a side experiment.

Nice To Haves

Deploying a customer master standalone in front of a third-party core.

Responsibilities

Own the direction: Define which party, relationship, agreement, and contact-point capabilities to prioritize, which jurisdictions and identifier types are configured first, and how the standalone-against-any-core motion is packaged.
Own non-discretionary change: KYC, beneficial-ownership, tax-certification (W-9, W-8 series, CRS), and privacy (GDPR erasure and equivalents) requirements.
Keep the roadmap on track and define success: Duplicate-party rate, KYC done once versus per-system, onboarding lead time, UBO query latency, migration parity, standalone deployments live.
Serve as the internal product authority on how banks master parties, resolve identity, model relationships and beneficial ownership, record consent and agreements, and maintain contact points across product silos.
Join client working sessions to define what to build — whiteboard the actual onboarding, KYC, and customer-maintenance flows, expose missing controls and duplicate-record risk, and identify the minimum viable reusable capability.
Convert recurring client and field signal into configurable types, relationship rules, and jurisdiction packs — not bank-specific schema changes; countersign any client commitment that binds the roadmap before it is promised.
Push back on clients and internal experts with evidence; document decisions so they stay made.
Define party, relationship, agreement, and contact-point APIs, domain events, the classified type system, identifier and tax certification models, and acceptance criteria.
Own the boundaries: Product contracts with Ledger, Reg & Compliance, Orchestration, Servicing, Data, Command Center, and the third-party cores and CRMs the component sits in front of.
This role owns what, why, priority, and acceptance criteria; engineering owns architecture, implementation, and estimates.