| Start Date: | |
| Interview Types |
| Skills | MQ exit |
| Visa Types | Green Card, US Citiz.. |
JO Details | |
Client Name | DTCC (Depository Trust & Clearing Corporation) |
Job Title | MQ Exits Developer (C Programming) |
C/CTH/Perm + Duration | 6-12 months contract |
Start date & Location | Dallas, TX |
Onsite | Hybrid – 3 Days onsite |
$$ | $60/hour W2 MAX |
Laptop | Keep in mind vendor needs to provide candidate with a laptop or $2 needs to be added into the all-inclusive C2C rate to cover Vendor ordering from Smartsource |
Position Notes | |
Client Detail (What does the company do? Recent history? Website? Parent Company? Size of Company?) The Depository Trust & Clearing Corporation (DTCC) is a financial services company that provides clearing, settlement, custody, and risk management services for securities transactions. It acts as a central clearinghouse,
manages assets, reduces counterparty risk, facilitates trade reporting, and operates technology platforms for efficient processing. Its role is to ensure the smooth functioning of securities markets and enhance transparency in the financial system. Job Order (Why might someone want to work here?) Role Overview: 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. Key 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: o Reduce reliance on exits by evaluating native MQ features o 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 | |