MQ Exit Developer

Location: Dallas, TX (75019) — Onsite, Full-time

About the role

We are seeking a highly skilled MQ Exit Developer with strong C programming expertise to maintain custom IBM MQ exits that extend and enhance the enterprise messaging platform. This role focuses on advanced MQ capabilities including security exits, API exits, and message exits to support authentication, authorization, transformation, and observability requirements across distributed and hybrid environments. The ideal candidate will have deep experience with low-level C development, strong understanding of IBM MQ internals, and the ability to deliver thread-safe, high-performance code integrated with enterprise security and operational standards.

Responsibilities

• MQ Exit Maintenance: Maintain existing IBM MQ channel exits, API exits, and message exits using C; ensure all exit implementations are thread-safe and optimized for multi-threaded MQ environments; integrate exit logic with external systems (e.g., LDAP, REST APIs) where required.
• Operational Support & Modernization: Provide L3 support for MQ exit-related issues in production environments; partner with platform and application teams to reduce reliance on exits by evaluating native MQ features; simplify and modernize legacy exit implementations; support migration initiatives.
• Documentation & Governance: Maintain detailed design documentation, code standards, and runbooks; ensure proper lifecycle management of exit code (versioning, deployment, rollback).

Requirements

• Expert-level C programming skills with a focus on low-level, high-performance development
• Deep experience designing, building, and maintaining IBM MQ exits (channel exits, API exits, message exits, security exits)
• Strong understanding of IBM MQ internals and multi-threaded MQ environments
• Proven ability to write thread-safe, optimized C code for high-throughput messaging systems
• Experience integrating MQ exits with external systems such as LDAP and REST APIs
• Familiarity with authentication, authorization, message transformation, and observability patterns in enterprise messaging
• Experience providing L3 production support for MQ exit-related issues
• Ability to evaluate native MQ features to reduce custom exit dependencies
• Strong documentation practices: design docs, code standards, runbooks, and versioned deployment/rollback procedures