Support Engineers MiddlewareWebSphere

Support Engineers

Richardson TX and Chicago 3 days Hybrid Must be local

Visa: Any except H1B and CPT

Duration: Long term

Job Description:

• We are looking for support engineers with a minimum starting 56 years of total experience with at least 3 of those years in support with some software/middleware development experience as well.
• Must have the ability to triage troubleshoot determine root cause and get the right people involved to support a complex middleware communication system comprised of many pieces.
• Communication and team skills are required and the candidate must be capable of properly documenting and leading incident bridge calls with internal and external clients and technical teams.
• Daytoday activities include handling usual incidents reports and notifications and establishing a call bridge to investigate/remedy issues.
• Alerts may come in as emails with limited logs to be examined which are used to troubleshoot and determine root causes remedies and mitigation plans.
• Postincident analysis is performed as to why a service may completely or partially fail. Maintenance tasks include certificate creation/renewals security scanning and evaluation.
• This position includes oncall support rotation with flexible work arrangements.
• The candidate will be a selfdriven and selfdirected individual capable of selflearning with handson training.
• This environment can be challenging to learn and maintain its an ACTIVEACTIVE environment between two data centers across different regions.
• With 6 billion transactions per month 2000 APIs currently being supported and over 200 clients internal/external services are supported and built for internal and external clients/vendors with sometimes many integration layers within.

This current environment presently uses the IBM middleware tech stack.

• DataPower
• ACE (IIB)
• MQ
• WebSphere
• APIC on the cloud
• OpenShift onprem cloud
• Monitoring: Splunk Instana Grafana

Skills/Knowledge:

• Some F5 knowledge
• Some Global/Local Traffic Manager
• REST
• Unix with bash network/process tools
• Security protocol(s)
• Basic CI/CD

Including the support and maintenance aspects above there is a future initiatives roadmap to move to alternative/newer technologies:

• KONG API
• Redis
• OpenShift containers
• Microservices (Spring Boot)