IBM MQ Engineer - Linux (IIB/ACE Integration & App Support)

Who We Are

At Kyndryl, we run and reimagine the mission-critical technology systems that drive advantage for the world's leading businesses. We are at the heart of progress; with proven expertise and a continuous flow of AI-powered insight, enabling smarter decisions, faster innovation, and a lasting competitive edge. For our people-Kyndryls-that means doing purposeful work that powers human progress. Join us and experience a flexible, supportive environment where your well-being is prioritized and your potential can thrive.

The Role

Key Responsibilities

MQ Platform Engineering (Linux)

• Design and implement IBM MQ infrastructure on Linux, including multi‑environment topologies (DEV/UAT/PROD), HA patterns, security configurations, and standards/baselines.
• Install, configure, and patch IBM MQ; manage queue managers, listeners, channels, SVRCONN, authentication/authorization (CHLAUTH/MCAUSER), and TLS artifacts.
• Build automation (e.g., scripts/Ansible) for repeatable provisioning, configuration drift control, and routine admin tasks.

• Create and maintain queue managers, queues (local/remote/alias/model), topics, subscriptions, channel objects, dead‑letter handling, and naming conventions.
• Implement security for objects (authorities, TLS, cipher suites, key stores), and enforce standards for durability, persistence, and message sizes.

• Partner with IIB/ACE teams to design interfaces, message models, and connectivity (MQ/HTTP/JDBC).
• Ensure MQ configurations (channels/queues) align with IIB/ACE message flows, transactionality, and error‑handling patterns.
• Assist with deployment pipelines for BAR files/ACE applications and validate end‑to‑end message paths.

• Onboard and support application teams: requirements gathering, connectivity patterns, security (certs/keys), and non‑functional needs (throughput, latency, HA).
• Provide operational guidance, best practices, and runbooks; review and approve MQ change requests.

• Monitor queue depth, channel status, logs, and system resources; set thresholds/alerts and drive incident response.
• Perform advanced troubleshooting (AMQ error logs, MQ trace/FDC analysis), root cause analysis, and permanent fixes.
• Support performance tuning (buffer sizes, channel parameters, batch sizing, thread pools) and capacity planning.

• Maintain platform standards, configuration baselines, SOPs/runbooks, and application onboarding guides.
• Adhere to change control and audit requirements; participate in CABs with risk/impact analysis and back‑out plans.

• 12+ years administering IBM MQ on Linux in enterprise environments.
• Proven experience in MQ infrastructure design, installation, configuration, and automation.
• Hands‑on with queue manager creation and MQ objects (queues, channels, listeners, topics, subscriptions).
• Practical experience collaborating with IBM IIB/ACE teams to deliver message flows and integration solutions.
• Strong scripting abilities (e.g., shell/Python or Ansible) for automation and operational tooling.
• Solid troubleshooting skills across MQ logs, traces, connectivity/certificates, and application integration issues.
• Strong stakeholder communication; ability to support and guide application teams end‑to‑end.

• Experience with TLS/PKI on Linux (OpenSSL, key/cert management) for MQ endpoints.
• Familiarity with CI/CD for integration deployments (Git/Jenkins/Azure DevOps) and infrastructure as code.
• Exposure to monitoring/observability (e.g., Splunk, Prometheus/Grafana, Dynatrace) for MQ metrics and alerting.
• Knowledge of MQ clustering, HA/DR strategies (multi‑instance QMs, RDQM, Pacemaker), and containerized MQ (Docker/Kubernetes) or MQ Appliance.
• Working knowledge of IIB/ACE development artifacts (message flows, BARs, JCN/ESQL) to troubleshoot with developers.

• Ownership and execution focus; crisp documentation and change discipline.
• Strong analytical/problem‑solving skills; calm under pressure during incidents.
• Clear communication with App, Integration, Security, and Platform teams.
• Continuous improvement mindset with a bias toward automation.

• Platform reliability: High MQ availability; reduced incident volume and MTTR.
• Deployment quality: Low change failure rate; faster onboarding of applications to MQ/IIB/ACE.
• Performance: Improved throughput/latency and stable message processing under peak loads.
• Automation coverage: Reduced manual steps via scripts/Ansible; consistent environments.
• Compliance: Timely certificate rotations, patching, and clean audit outcomes.