Technical Manager

Senior Technical Delivery Manager – Open Banking & Open FinanceLocation: Charlotte, NC or Raleigh, NC or Birmingham, AL or Memphis, TNExperience • 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 programsRole SummaryThe 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), andDelivery 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 Areas1. Architecture Ownership with Delivery AccountabilityOwn 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 modelsVersioning, lifecycle management, and backward compatibilityEnsure architecture decisions are delivery-practical, cost-aware, and operable at scale.2. End-to-End Delivery LeadershipOwn full lifecycle delivery: design ? build ? test ? release ? operate.Drive delivery using Agile / SAFe / Hybrid models, with accountability for:Commitments vs outcomesCross-team dependenciesRelease readiness and production sign-offActively remove delivery risks related to:Architecture gapsSecurity approvalsRegulatory dependenciesEnsure delivery predictability across Dev, QA, Prod, and DR environments.3. Open Banking & Regulatory ExecutionLead delivery aligned to Open Banking / Open Finance regulations:FDX (US)PSD2 / PSD3 (EU)Open Banking UKConsumer Data Right (CDR)Own implementation of:Data Provider and Data Consumer capabilitiesConsent capture, validation, renewal, and revocation flowsEnsure regulatory timelines are treated as delivery milestones, not theoretical targets.4. Security-First Architecture & Compliance DeliveryOwn security architecture AND its implementation, not just design.Drive end-to-end adoption of:OAuth 2.0 / OpenID ConnectmTLS, PKI, certificate rotationSecure API gateways and identity controlsServe as the primary interface to Risk, Compliance, and Audit.Ensure architecture patterns pass real audit scrutiny, not just documentation reviews.5. Platform Engineering & Modernization ExecutionOwn modernization from:Legacy ESB / SOAP platformsTo API-first, microservices, and event-driven architecturesEnsure architecture modernization is sequenced with delivery, avoiding big-bang rewrites.Oversee integration with:Core banking platformsEnterprise Data & Analytics platformsExternal fintech and aggregator ecosystemsBalance technical debt reduction with delivery velocity.6. Cloud, DevSecOps & Production AccountabilityOwn Open Banking platforms deployed on cloud (preferably Azure):AKS / KubernetesAPI Management and ingress platformsDrive 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 responseOwn production stability — this role does not “throw over the wall.”7. Stakeholder, Vendor & Executive ManagementAct as single throat to choke for Open Banking delivery and platform health.Engage at executive level with:CIO, DCIO, Enterprise Architecture leadershipRisk, Compliance, and Legal headsOwn vendor and partner delivery, ensuring:Architecture alignmentDelivery accountabilityClear ownership boundariesCommunicate complex technical and delivery trade-offs in business-clear language.