Drimva

JPMorgan Chase

Technology Support III - Quality Engineering, ISO 20022

Tampa, FL · Full-time · Posted Oct 19, 2026

Experience
3+ years in IT troubleshooting, resolution, and maintenance, or equivalent expertise; 3+ years in QA/testing or technology delivery.

About the job

Supports production application flows for high-value payments by maintaining operational stability, coordinating testing, and resolving incidents involving ISO 20022 message processing.

What you'll do

  • Maintain systems and production environments, monitor for anomalies, and resolve or escalate issues.
  • Plan testing with stakeholders, track defects through resolution, and present results for release readiness.
  • Use authorized AI capabilities and observability tools to support incident triage, trend analysis, and validated remediation.

What they ask for

  • 3+ years of experience or equivalent expertise troubleshooting, resolving, and maintaining IT services; 3+ years of applied experience in QA/testing or technology delivery.
  • Banking or financial services experience and working knowledge of payments processing and ISO 20022 formats, including pacs.008, pacs.009, pacs.004, pain.001, pain.013, and camt.056.
  • Demonstrated experience using enterprise-authorized AI in production support workflows, validating recommendations, and handling sensitive data appropriately.
  • Knowledge of applications or infrastructure in large-scale on-premises and public-cloud environments; experience with observability and monitoring; exposure to ITIL processes.

Nice to have

  • Test automation and QA tooling, including Selenium, Cucumber, Java, or Python; familiarity with data engineering and data-quality testing.
  • Working knowledge of JIRA, qTest, Confluence, or SharePoint; basic to intermediate SQL skills.

Tools

ISO 20022, pacs.008, pacs.009, pacs.004, pain.001, pain.013, camt.056, Selenium

AI focus

Uses enterprise-authorized AI to assist incident triage, analyze operational trends, and support remediation, with human validation and attention to data sensitivity, security, and escalation expectations.

Model-written summary · the original posting is authoritative

First seen Oct 28, 2026 · Last verified Nov 5, 2026 (UTC)