Integration Development Lead

Position Overview

Owns the technical delivery of the integration build. Converts the architecture and design patterns defined by the Design Lead into an executable build plan, coding standards, and delivery cadence. Leads the Integration Designer and the three Integration Engineers day-to-day, ensuring consistent implementation, code quality, and adherence to the design blueprint. Acts as the technical escalation point during build and testing.

Key Responsibilities

· Translate architecture patterns into detailed low-level designs and reusable Camel route/component templates

· Define coding standards, branching strategy, CI/CD pipeline approach, and environment promotion process (dev → test → UAT → prod)

· Plan and sequence the build backlog across HIP-side (Camel/Kafka/3Scale) and Azure-side (Service Bus/Logic Apps/Fabric/D365) work streams

· Lead sprint planning, technical stand-ups, and code/design reviews for the engineering team

· Own build-phase technical risk and issue resolution; escalate architecture-impacting issues to the Design Lead

· Ensure error handling, retry/dead-letter, idempotency, and logging/monitoring standards are consistently implemented across services

· Coordinate integration testing strategy with QA (contract testing, end-to-end testing across Kafka/Service Bus boundaries)

· Manage technical onboarding of engineers and ensure knowledge transfer/documentation of built components

· Support performance tuning and defect triage during SIT/UAT and early production support

Mandatory Skills / Experience Required

· 8+ years in integration development, with 3+ years in a technical lead/delivery lead capacity

· Strong hands-on background in Apache Camel (DSL - Java or XML), Spring Boot, and microservices deployment patterns on OpenShift/Red Hat

· Practical experience building and operating Kafka producers/consumers, including schema evolution and error/DLQ handling

· Experience exposing/managing APIs via 3Scale (policies, API contracts, security) Hands-on or strong working exposure to Azure Service Bus (queues/topics), Logic Apps (workflows/connectors), and ideally Dynamics 365/Dataverse integration

· Solid understanding of CI/CD tooling (Jenkins/GitLab/Azure DevOps), containerization (Docker/OpenShift), and Git-based workflows

· Experience leading a cross-functional engineering team (3–6 engineers) through a full delivery lifecycle

· Strong debugging/performance-tuning skills across distributed, event-driven systems

Additional Requirement

· Experience with Microsoft Fabric (Data Pipelines/Event streams) is a differentiator given the target platform

· Red Hat OpenShift and Spring certifications are useful but not essential if hands-on experience is strong

· This person needs to be equally comfortable in design conversations and in the code - expect them to do design reviews and occasionally pair on complex routes

· Should be able to act as a stand-in for the Design Lead on day-to-day design clarifications