L2 Technical Support Leader (Integration & Middleware)

Job Description: Strategic Technical Leadership - End-to-End Traceability: Lead the team in tracing transaction flows from the API Gateway (API Connect) through the Enterprise Service Bus (ACE) to the backend Microservices (Spring Boot). - Root Cause Analysis (RCA): Spearhead deep-dive investigations into middleware failures, such as message losses in MQ, synchronization errors in ACE, or JVM crashes in Spring Boot. - Platform Governance: Oversee the stability of integration components running on Red Hat OpenShift, ensuring optimal resource (CPU/Memory) allocation and pod scaling. - Security Enforcement: Manage and troubleshoot security protocols, including Mutual TLS (mTLS), OAuth2, and JWE/JWS within the integration layer. Detailed Technical Responsibilities A. IBM Cloud Pak for Integration (CP4I) - App Connect Enterprise (ACE): Troubleshoot message flows, ESQL logic errors, and adapter connectivity issues (SAP, Database, File). - IBM MQ: Manage queue managers, resolve channel retries, and investigate dead-letter queues or message persistence issues. - API Connect: Resolve issues related to API definitions, security policies, and Gateway (DataPower) latency. B. Backend Microservices (Spring Boot) - Performance Tuning: Analyze JVM thread dumps and heap dumps to resolve memory leaks or high CPU utilization in microservices. - Connectivity Debugging: Troubleshoot Spring Boot integration with databases (JPA/Hibernate) and external messaging systems (JMS/Kafka). - Log Aggregation: Utilize ELK/Splunk to correlate logs across multiple microservices to identify points of failure in a distributed architecture. Technical Skill Set - Integration Platforms: Mastery of IBM CP4I (specifically ACE, MQ, and API Connect). - Development Frameworks: Advanced knowledge of Java and Spring Boot (Spring Integration, Spring Cloud). - Containerization: Expert-level proficiency in Red Hat OpenShift and Kubernetes. - Protocols & Standards: Expert understanding of REST, SOAP, JSON, XML, AMQP, and MQTT. - Monitoring Tools: Hands-on experience with IBM Instana, Dynatrace, or Prometheus/Grafana. At DXC Technology, we believe strong connections and community are key to our success. Our work model prioritizes in-person collaboration while offering flexibility to support wellbeing, productivity, individual work styles, and life circumstances. We’re committed to fostering an inclusive environment where everyone can thrive. Recruitment fraud is a scheme in which fictitious job opportunities are offered to job seekers typically through online services, such as false websites, or through unsolicited emails claiming to be from the company. These emails may request recipients to provide personal information or to make payments as part of their illegitimate recruiting process. DXC does not make offers of employment via social media networks and DXC never asks for any money or payments from applicants at any point in the recruitment process, nor ask a job seeker to purchase IT or other equipment on our behalf. More information on employment scams is available here.

Strategic Technical Leadership responsibilities include end-to-end traceability across API Gateway, Enterprise Service Bus, and backend microservices; root cause analysis for middleware failures; platform governance of Red Hat OpenShift; and security enforcement (mutual TLS, OAuth2, JWE/JWS) within the integration layer. Detailed technical responsibilities cover IBM Cloud Pak for Integration (ACE, MQ, API Connect), troubleshooting App Connect Enterprise, MQ queue management, API Connect security/policy issues, and backend microservices performance tuning (JVM, memory, CPU); connectivity debugging with databases (JPA/Hibernate) and messaging systems (JMS/Kafka); and log correlation using ELK/Splunk. The role requires mastery of IBM CP4I components (ACE, MQ, API Connect), advanced Java and Spring Boot (Spring Integration, Spring Cloud), expert OpenShift and Kubernetes containerization, deep understanding of REST, SOAP, JSON, XML, AMQP, MQTT, and hands-on monitoring with IBM Instana, Dynatrace, or Prometheus/Grafana.

Strategic Technical Leadership: Lead the team in tracing transaction flows from the API Gateway (API Connect) through the Enterprise Service Bus (ACE) to the backend Microservices (Spring Boot). Spearhead deep-dive investigations into middleware failures, such as message losses in MQ, synchronization errors in ACE, or JVM crashes in Spring Boot. Platform Governance: Oversee the stability of integration components running on Red Hat OpenShift, ensuring optimal resource (CPU/Memory) allocation and pod scaling. Security Enforcement: Manage and troubleshoot security protocols, including Mutual TLS (mTLS), OAuth2, and JWE/JWS within the integration layer. Detailed Technical Responsibilities A. IBM Cloud Pak for Integration (CP4I): App Connect Enterprise (ACE): Troubleshoot message flows, ESQL logic errors, and adapter connectivity issues (SAP, Database, File). IBM MQ: Manage queue managers, resolve channel retries, and investigate dead-letter queues or message persistence issues. API Connect: Resolve issues related to API definitions, security policies, and Gateway (DataPower) latency. B. Backend Microservices (Spring Boot): Performance Tuning: Analyze JVM thread dumps and heap dumps to resolve memory leaks or high CPU utilization in microservices. Connectivity Debugging: Troubleshoot Spring Boot integration with databases (JPA/Hibernate) and external messaging systems (JMS/Kafka). Log Aggregation: Utilize ELK/Splunk to correlate logs across multiple microservices to identify points of failure in a distributed architecture.