Lead Infrastructure Engineer - MQ Series

JPMorganChase•Plano, TX

About The Position

Assume a vital position as a key member of a high-performing team that delivers infrastructure and performance excellence. Your role will be instrumental in shaping the future at one of the world's largest and most influential companies. As a Lead Infrastructure Engineer at JPMorganChase within the Corporate Sector – Enterprise Technology, you apply deep knowledge of software, applications, and technical processes within the infrastructure engineering discipline. Continue to evolve your technical and cross-functional knowledge outside of your aligned domain of expertise.

Requirements

5+ years of experience or equivalent expertise troubleshooting, resolving, and maintaining information technology services
Deep knowledge of one or more areas of infrastructure engineering such as hardware, networking terminology, databases, storage engineering, deployment practices, integration, automation, scaling, resilience, or performance assessments
Deep knowledge of one specific infrastructure technology and scripting languages (e.g., Scripting, Python, etc.)
Drives to continue to develop technical and cross-functional knowledge outside of the product
Deep knowledge of cloud infrastructure and multiple cloud technologies with the ability to operate in and migrate across public and private clouds
Experience executing on processes in scope of the Information Technology Infrastructure Library (ITIL) framework
Demonstrated, hands-on experience operating middleware in enterprise production environments, including IBM MQ administration and incident response in secure environments.
Strong problem determination skills, structured troubleshooting approach, and ability to perform under time pressure while maintaining operational discipline.
Working knowledge of Unix and/or Windows system administration, including process, filesystem, certificate stores, and basic networking fundamentals relevant to MQ connectivity.
Strong written and verbal communication skills with the ability to coordinate across distributed teams and manage customer expectations.

Nice To Haves

Working knowledge in one or more general purpose programming languages preferred Python and/or Java and/or automation scripting
Practical experience with public cloud

Responsibilities

Applies technical expertise and problem-solving methodologies to projects of moderate scope
Drives a workstream or project consisting of one or more infrastructure engineering technologies
Works with other platforms to architect and implement changes required to resolve issues and modernize the organization and its technology processes
Executes creative solutions for the design, development, and technical troubleshooting for problems of moderate complexity
Strongly considers upstream/downstream data and systems or technical implications and advises on mitigation actions
Operate and support IBM MQ environments across development, testing, and production, ensuring service availability, stability, and compliance with internal standards.
Support resilience objectives via disaster recovery planning, sustained resilience coordination, and testing/validation activities.
Apply reliability engineering practices: define and improve service health indicators, operational thresholds, and actionable alerting to reduce noise and improve time-to-detect/time-to-recover.
Maintain clear operational runbooks, standards, and controls that enable consistent execution across a geographically distributed operations model.
Reduce toil through automation, including scripted remediation, self-service operational workflows, and repeatable change execution (e.g., certificate lifecycle, configuration validation, routine health checks).
Institutionalize post-incident learning: contribute to blameless reviews, ensure corrective actions are tracked to closure, and verify effectiveness through measurable outcome improvements.
Provide technical guidance and responsive support to application teams integrating with MQ, including connection patterns, security constraints, and operational best practices.