About The Position

As a Senior Manager of Software Engineering within JPMorganChase’s Commercial and Investment Bank, Payments and Global Banking Technology organization, you will lead engineering work that helps merchants continue accepting, processing, and settling payments when regions, dependencies, or releases fail. You will define testable resiliency standards, ground the work in actual application dependencies, design tests that validate end-to-end merchant journeys, and establish shared engineering patterns for teams to adopt.

Requirements

  • Hands-on experience designing or running multi-region systems at scale on AWS in 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, and the effects of service boundaries and dependencies on 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 sound judgment in evaluating whether a test provides valid proof.
  • Ability to influence senior engineering leaders and architects through technical argument without direct authority.
  • Track record of driving an engineering standard across many teams until they adopted it.

Nice To Haves

  • 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 spanning several teams.

Responsibilities

  • Define testable engineering criteria for resiliency standards, including region failover, rollback coverage, and canary measurements.
  • Drive multi-region engineering across Merchant Services applications, including deployments and releases, automated failover and failback, and independent traffic switching.
  • Map dependencies across applications and merchant journeys, including event producer and consumer chains and shared services, and turn these maps into a technically sound delivery sequence.
  • Review failover runbooks, dependency maps, release designs, and observability plans with engineering leaders and architects; assess the technical soundness of dates, blockers, and exception requests.
  • Design region failover tests, game days, rollback drills, and synthetic journey tests, and determine whether results prove the standard across the end-to-end merchant journey.
  • Establish reusable resiliency patterns with architects and platform engineering for failover, traffic switching, release safety, pipeline guardrails, synthetic journeys, and edge telemetry.
  • Lead technical learning from resiliency failures in testing and production; ensure root causes are conclusive and fixes address recurring patterns through existing release management and problem management processes.
  • Communicate to senior technology leaders what is proven, what is at risk, why, and what options are available.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service