Banking Platform Architect

Key

Responsibilities: Own the architecture of the Fiserv/Finxact platform ecosystem: product-factory model, data model, parameterization limits, ledger/GL structure and Fiserv-native capabilities (payments rails, cards/lending). Define how the Fiserv/Finxact platforms expose and consume APIs, setting integration contracts and standards at the boundary between Finxact and the rest of the ecosystem. Serve as the technical authority on Finxact's operating model, what is achievable via configuration vs. code, and the Fiserv vendor roadmap - ensuring core decisions are defensible before a regulator. Produce and maintain versioned Architecture Decision Records (ADRs) and current platform documentation - examination evidence expected by OCC / FFIEC . Embed platform-level security, resilience and data-governance controls (RBAC / segregation of duties, encryption, audit trails, multi-region resiliency) aligned with InfoSec. Act as the technical counterpart to Fiserv/Finxact and partners, validating solution architecture, configuration approach and delivery model against our reference architecture. Partner with the Core Banking Engineering Lead, Config Specialists (Core/Deposits, Payments, Cards & Lending), Integrations and Release & Quality to ensure the platform architecture is buildable and audit-ready. Requirements 15+ years of experience in IT. 8+ years in platform / solution architecture, including modern core banking in a U.S. banking context. MUST HAVE Deep, hands-on knowledge of the Fiserv ecosystem Finxact experience is strongly preferred (data model, parameterization, APIs, Config-as-Code). Strong command of API-led / event-driven integration patterns and secure, high-volume data flows on AWS (API Gateway; Lambda / EventBridge / Kafka a plus). Understanding of U.S. payments rails (Fedwire, ACH, RTP, FedNow), OFAC screening, cards and lending on a core platform. Rigorous documentation discipline (ADRs, HLDs, data-flow maps); comfortable in a regulated, audit-driven environment. Nice to have MuleSoft (or equivalent iPaaS / API management) experience. At least one prior U.S. regulatory examination experience Bachelor’s degree in Information Technology or related field.