Job Description & Details
This is a heavy-duty integration gig focused on legacy enterprise data transformation, specifically leveraging IBM Sterling Transformation Extender. If you enjoy untangling messy data pipes and keeping B2B integrations running smoothly, this 6 to 12-month contract in Hartford will keep you busy from day one.
What You'll Actually Be Doing
You'll be spending most of your time designing, writing, and debugging IBM ITX maps to handle heavy volumes of EDI transactions. You're not just writing code in a silo; you'll be actively hooking ITX into IBM Sterling File Gateway, B2B Integrator, ACE/IIB, and IBM MQ. Expect to field urgent production issues, troubleshoot failing transformations, and parse everything from rigid X12 and EDIFACT standards to messy fixed-length flat files and pipe-delimited data.
The Core Tech Stack
You absolutely must know IBM Sterling Transformation Extender (ITX) inside and out, as you'll be building complex type trees and maps without much hand-holding. Alongside ITX, you need solid fluency in EDI protocols like X12 and EDIFACT, plus experience dealing with flat files, CSVs, and XML/XSD structures. The ecosystem relies heavily on IBM middleware like B2BI, SFG, and MQ, so having familiarity with those surrounding tools will make or break your ability to ship integrations successfully here.
Interview Expectations
Expect them to throw a real-world scenario at you, such as: "Walk me through how you would troubleshoot a map failing silently in production due to an unexpected delimiter change in an incoming X12 file." The hiring manager wants to see a methodical approach to error handling, type tree adjustments, and log analysis rather than just guessing. They might also ask how you handle large message volumes without blowing out memory in ITX, looking specifically for your optimization and performance-tuning strategies.
Application Advice
Make sure your resume doesn't just list ITX as a buzzword, but explicitly highlights your experience building maps for EDI X12, EDIFACT, XML, and fixed-length files. Ensure acronyms like SFG, B2BI, ACE/IIB, and MQ are prominently featured in your project descriptions so the ATS immediately catches your enterprise middleware background. Tailor your summary to emphasize production support and end-to-end integration workflows, as they need someone who can hit the ground running fully onsite.