Technical Product Manager Principal - Ledger

ROLE SUMMARY

Sits within a newly acquired startup building an AI-enabled, autonomous banking platform for Tier-1 financial institutions within the banking group. The Product Manager is the single-threaded product owner for the Enterprise Ledger - the real-time, double-entry system of record for the whole bank, engineered to run live beside any product system and take over one capability at a time. Requires deep core-accounting and ledger expertise, an engineering foundation, and end-to-end ownership of what we build and why. The Ledger is the flagship component: every other component posts to it. This is not a programme- or delivery-management role: client-programme orchestration sits with the Forward Deployed team, and engineering owns architecture and implementation.

KEY RESPONSIBILITIES

Ledger Strategy & Roadmap

· Own the direction: Define the Ledger strategy and adoption sequencing, which balance and policy primitives to invest in, and what lives in the thin engine versus declarative policy.

· Own non-discretionary change: Emerging asset types, multi-asset scoping, card-authorisation hold rules, and audit and retention expectations.

· Keep the roadmap on track and define success: Posting latency and throughput, balance invariants held under failure, coexistence parity, reconciliation breaks, and safe rollout and rollback.

Ledger Domain & Client Leadership

· Be the SME: Serve as the internal product authority on how double-entry accounting, accounts and balances, holds and pending states, settlement, multicurrency and multi-asset ledgers, and GL integration work end to end in a bank.

· Problem-solve with clients: Join client working sessions to define what to build - whiteboard the actual posting and settlement lifecycle for a product, expose missing controls and edge cases, and identify the minimum viable reusable capability.

· Guard the platform: Convert recurring client and field signal into reusable balance types, policies, and primitives - not engine exceptions; countersign any client commitment that binds the roadmap before it is promised.

· Challenge constructively: Push back on clients and internal experts with evidence; document decisions so they stay made.

Technical Product Definition

· Write the contract: Define ledger APIs, events, account and balance models, transfer and instruction semantics, error semantics, and acceptance criteria.

· Sweat the semantics: Idempotent instructions, two-phase movement (post, pending, settle, void, increment, replace), hold timeouts, monotonic posted totals, replayable history, product-version sealing, safety gates and rollback.

· Own the boundaries: Product contracts with Orchestration, Customer, Reg & Compliance, Reconciliation, Data, Command Centre, Product & Pricing, and the incumbent cores.

· Respect the split: This role owns what, why, priority, and acceptance criteria; engineering owns architecture, implementation, and estimates.

REQUIRED EXPERIENCE & CAPABILITIES

Ledger & Core-Accounting Expertise

· Deep, hands-on expertise in a core-banking ledger, deposit or lending system of record, card-issuing ledger, or high-volume financial ledger - with personal ownership of how it posted, held, settled, and reconciled money.

· Working command of double-entry invariants, pending versus posted balances, authorisation holds and expiries, settlement and finality, value dating, reversals and corrections, period close, and GL mapping.

· Practical exposure to product configuration on a ledger (interest, fees, limits, overdraft, sweeps). Strongly preferred: coexistence or migration beside a legacy core; multi-currency or tokenised-asset ledgers.

Technical Foundation

· 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 modelling, reliability, security, and observability; reads architecture diagrams without a translator.

Operating Style

· 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 finance, treasury and operations leaders, core-banking experts, risk and audit 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.

IMPACT & SCOPE

· Direct impact on the system of record beneath every platform component, used by Tier-1 global institutions.

· High autonomy and accountability within a small, senior team, paired with a senior engineering lead.

· Work shipped directly to production at Tier-1 banking scale, where correctness is proven against formal invariants.

WHY THIS ROLE

This role offers the autonomy, ownership, and technical depth of a startup, combined with the scale, stability, and long-term impact of FIS. You will define how some of the world’s largest banks record every balance and every movement of money - and how they retire the legacy core beneath it, one portfolio at a time.

Privacy Statement

FIS is committed to protecting the privacy and security of all personal information that we process in order to provide services to our clients. For specific information on how FIS protects personal information online, please see the Online Privacy Notice.

Sourcing Model

Recruitment at FIS works primarily on a direct sourcing model; a relatively small portion of our hiring is through recruitment agencies. FIS does not accept resumes from recruitment agencies which are not on the preferred supplier list and is not responsible for any related fees for resumes submitted to job postings, our employees, or any other part of our company.