Java Application Support

1. Willing to work in shifts to provide rotational 24/7 shift application support duties as mentioned below.

2. Has experience or knowledge on Incident and Problem management.

3. Health check and monitoring production system and job scheduling to ensure SLA is meet.

4. Troubleshoot and solve production issues related to performance and reliability throughout the software stack.

5. Proactively identify bottlenecks in the system and work to resolve these issues before they become a problem.

6. Continuous improvement of the system, e.g. job automation, performance tuning.

7. Should be able to identify and fix the bugs.

8. At least 5-7 years of hands-on experience on troubleshooting the applications run on full stack preferably in Java, Spring-boot, Microservices.

9. At least 5-7 years of working experience, preferably in Banking or Anti money laundering.

10. At least 5-7 years of working experience in production support in banking applications running on Windows and Unix environments.

11. Should have strong hold on SQL server/Oracle databases and able to write/debug the SQL programs.

12. Good knowledge in Linux/Unix/Windows environments and scripting.

13. Hands on experience with monitoring tools like Grafana has added advantage.

14. Should be open to learn and adapt to new technologies.

15. Knowledge on GIT Bitbucket and Jenkins has added advantage.

16. Knowledge on Actimize/Hadoop/AML support experiences has added advantage.

17. Investment banking background has added advantage

18. L2 Production support experiences must be 5 years above and must be the current/last role.

The following skills :-

• SQL query optimisation, including how to check if a query needs optimization, understanding SQL database locking DB locks (sp_locks), and interpreting query plans.

• The importance of analyzing show plans, logical IO, table scans, and the use of indexes, how the optimizer selects query plans and the impact of removing cache and recalculating indexes.

• role of indexes in query performance, including the need to ensure index columns are used correctly in queries.

• Use of Unix commands (iostat) and coordination with the storage team.

• Network latency troubleshooting was mentioned, with ping tests used to identify round-trip delays and timeouts (e.g., 100 ms latency).

Timing

1. Shift Timing

a. Morning shift 6am to 3pm

b. General shift 9am to 6pm.

c. Afternoon shift 2pm to 11pm

d. Night shift 10pm to 7am.

2. Need to support including night shift, weekends and public holidays