About the role
Work Mode: Hybrid (2/3 Days Office) Design and build EDI transaction processing pipelines using Java and API-driven services to replace existing Edifecs-based workflows, deploying on Azure cloud services (Logic Apps, Azure Functions, Service Bus, API Management) where applicable. Re-platform X12 mapping, validation, and transformation rules from Edifecs specs/maps into target-platform schemas and custom Java code. Own end-to-end development for core healthcare transaction sets: 834 (Enrollment), 278 (Authorization), 270/271 (Eligibility), 835 (Remittance Advice), and 837 (Claims - institutional/professional/dental). Partner with QE to define test scenarios, synthetic EDI file generation, and automated validation for parity between legacy Edifecs output and new Azure pipelines. Apply AI/GenAI tooling (Copilot-style code assistance, LLM-based test case or mapping-rule generation) to speed up migration and reduce manual mapping effort. Troubleshoot transaction failures, envelope/segment errors, and companion-guide deviations across trading partners. Document mapping specifications, migration runbooks, and cutover/rollback plans for each transaction set. Collaborate with onshore/offshore teams, EDI business analysts, and clearinghouse/trading-partner contacts during parallel-run and go-live phases. 5+ years of strong software engineering experience building X12 EDI transaction processing solutions (834, 278, 270/271, 835, 837). Strong working knowledge of Edifecs components (XEngine, Transaction Manager, SpecBuilder, or similar) and experience migrating off a legacy EDI platform. Strong Java development skills for custom transformation, validation, and integration logic. Hands-on experience designing, building, and consuming APIs (REST/SOAP) for system integration and trading-partner connectivity. Strong SQL expertise, including complex queries and data stores for transaction logging, reconciliation, and audit trails. Strong troubleshooting skills for EDI envelope, segment, and business-rule level errors. Healthcare payer or clearinghouse domain experience, including HIPAA 5010 implementation guides, companion guides, and trading-partner onboarding. Exposure to AI-assisted development tools (GitHub Copilot or equivalent). Practical experience with Azure integration services: Logic Apps, Azure Functions, API Management, Service Bus/Event Grid, Azure Integration Account (X12 schemas/agreements). Proficiency in Python for scripting, automation, and custom transformation logic. Prior experience on an Edifecs-to-cloud (Azure/AWS) modernization project. Knowledge of Azure Health Data Services or FHIR. Exposure to CI/CD pipelines (Azure DevOps) for integration deployments.