Sr Manager of Software Engineering - Resiliency Engineering

As a Senior Manager of Software Engineering at JPMorganChase within the Commercial and Investment Bank, Payments and Global Banking Technology organization you are an integral part of an agile team that works to enhance, build, and deliver trusted market-leading technology products in a secure, stable, and scalable way. 

Merchants rely on JPMorgan Payments to accept, process and settle their payments whenever their customers buy, and to keep doing so when something goes wrong behind the scenes. A merchant should never be able to tell that a region, a dependency or a release has failed.

You will lead the engineering that keeps that promise across our platforms. You will define what our resiliency standards mean in testable terms, ground the work in the real dependencies between applications, design the tests that prove a merchant's end-to-end journey keeps working, and build shared patterns that teams adopt. 

Job Responsibilities

• Defines what "done" means for each resiliency standard as testable engineering criteria, such as what counts as a proven region failover for a merchant journey, what a rollback must cover (code, feature flags, configuration and data), and what a canary must measure before traffic widens.
• Drives multi-region engineering across Merchant Services applications, including deployment and releases, automated failover and failback, and independent traffic switching.
• Maps dependencies across applications and merchant journeys, including event producer and consumer chains and shared services, and turns them into a delivery sequence that holds up technically.
• Reviews failover runbooks, dependency maps, release designs and observability plans with engineering leaders and architects, and judges whether dates, blockers and exception requests are technically sound.
• Designs region failover tests, game days, rollback drills and synthetic journey tests, and decides whether the results prove the standard across the whole merchant journey.
• Establishes reusable resiliency patterns with architects and platform engineering, covering failover, traffic switching, release safety, pipeline guardrails, synthetic journeys and edge telemetry.
• Leads the technical learning from resiliency failures in testing and production, making sure root causes are conclusive and fixes address the pattern rather than the single instance, working through the existing release management and problem management processes.
• Gives senior technology leaders a clear engineering view of what is proven, what is at risk and why, and the options.

Required Qualifications, Capabilities, and Skills

• Hands-on experience designing or running multi-region systems at scale on AWS, in both active-active and active-passive configurations, including messaging (Kafka or Amazon MSK), traffic routing (Amazon Route 53), containers (Amazon EKS or ECS) and databases.
• Strong understanding of microservices architecture, including design-time and runtime coupling, with the ability to assess how service boundaries and dependencies affect resiliency across complex platforms.
• Release engineering experience with canary and blue/green deployments, feature-flag control and automated rollback.
• Observability and site reliability engineering experience, including SLOs, synthetic monitoring, edge and real-user telemetry, and incident analysis.
• Experience leading resiliency testing, such as game days, chaos engineering or disaster recovery exercises, and the judgment to tell a real proof from a flawed one.
• Ability to influence senior engineering leaders and architects through technical argument, without direct authority.
• A track record of driving an engineering standard across many teams until they adopted it.

Preferred Qualifications, Capabilities, and Skills

• Experience in payments or another regulated industry.
• Hands-on experience with resiliency patterns such as dependency isolation and graceful degradation; retries, timeouts and circuit breakers; data replication, idempotency and reconciliation; and capacity headroom and load shedding during recovery.
• Experience leading root-cause analysis for complex incidents that span several teams.