Senior Technical Delivery Manager - Open Banking & ...

ob Title : Senior Technical Delivery Manager - Open Banking & Open Finance Location: Charlotte, NC or Raleigh, NC or Birmingham, AL or Memphis, TN Experience • 12-20 years of progressive experience in Banking / Financial Services technology • 6-10+ years owning delivery and architecture for large-scale digital banking or Open Banking programs Role Summary The Senior Technical Delivery Manager is the single-point owner accountable for both technical architecture and end-to-end delivery execution of Open Banking and Open Finance platforms. This role combines: • Architecture ownership (how the platform is designed, secured, and scaled), and • Delivery ownership (how the platform is built, released, governed, and operated). The role carries direct accountability for regulatory compliance, engineering outcomes, delivery predictability, platform stability, and stakeholder confidence. Core Accountability Areas 1. Architecture Ownership with Delivery Accountability • Own the target and transitional architecture for Open Banking platforms. • Translate regulatory and business requirements into actionable architecture and delivery plans. • Define and govern: • API standards, data contracts, and canonical models • Versioning, lifecycle management, and backward compatibility • Ensure architecture decisions are delivery-practical, cost-aware, and operable at scale. 2. End-to-End Delivery Leadership • Own full lifecycle delivery: design → build → test → release → operate. • Drive delivery using Agile / SAFe / Hybrid models, with accountability for: • Commitments vs outcomes • Cross-team dependencies • Release readiness and production sign-off • Actively remove delivery risks related to: • Architecture gaps • Security approvals • Regulatory dependencies • Ensure delivery predictability across Dev, QA, Prod, and DR environments. 3. Open Banking & Regulatory Execution • Lead delivery aligned to Open Banking / Open Finance regulations: • FDX (US) • PSD2 / PSD3 (EU) • Open Banking UK • Consumer Data Right (CDR) • Own implementation of: • Data Provider and Data Consumer capabilities • Consent capture, validation, renewal, and revocation flows • Ensure regulatory timelines are treated as delivery milestones, not theoretical targets. 4. Security-First Architecture & Compliance Delivery • Own security architecture AND its implementation, not just design. • Drive end-to-end adoption of: • OAuth 2.0 / OpenID Connect • mTLS, PKI, certificate rotation • Secure API gateways and identity controls • Serve as the primary interface to Risk, Compliance, and Audit. • Ensure architecture patterns pass real audit scrutiny, not just documentation reviews. 5. Platform Engineering & Modernization Execution • Own modernization from: • Legacy ESB / SOAP platforms • To API-first, microservices, and event-driven architectures • Ensure architecture modernization is sequenced with delivery, avoiding big-bang rewrites. • Oversee integration with: • Core banking platforms • Enterprise Data & Analytics platforms • External fintech and aggregator ecosystems • Balance technical debt reduction with delivery velocity. 6. Cloud, DevSecOps & Production Accountability • Own Open Banking platforms deployed on cloud (preferably Azure): • AKS / Kubernetes • API Management and ingress platforms • Drive DevSecOps adoption with: • CI/CD pipelines (Jenkins, GitHub, Bitbucket) • Infrastructure as Code (Terraform, Helm) • Be accountable for: • Non-functional requirements (performance, resilience, scalability) • Observability, alerting, and incident response • Own production stability - this role does not "throw over the wall." 7. Stakeholder, Vendor & Executive Management • Act as single throat to choke for Open Banking delivery and platform health. • Engage at executive level with: • CIO, DCIO, Enterprise Architecture leadership • Risk, Compliance, and Legal heads • Own vendor and partner delivery, ensuring: • Architecture alignment • Delivery accountability • Clear ownership boundaries • Communicate complex technical and delivery trade-offs in business-clear language. Required Experience & Capabilities Must-Have • Proven experience owning both architecture decisions and delivery outcomes • Deep exposure to Open Banking / Open Finance ecosystems • Strong background in: • API platforms and digital banking • Security, identity, and consent models • Demonstrated ability to lead under regulatory and production pressure Technical Depth (Hands-on or Strong Oversight) • APIs: REST, OpenAPI, JSON, API gateways • Architecture: Microservices, DDD, event-driven design • Security: OAuth2, OIDC, mTLS, PKI • Cloud: Azure (preferred), AWS, or GCP • Containers: Docker, Kubernetes • Observability: Splunk, Prometheus, Grafana, Dynatrace

Created: 2026-03-04