POSITION SUMMARY

Senior Control M Developer & Data Engineer

RESPONSIBILITIES

Senior Control M Developer & Data Engineer

·       Data migration and optimize legacy orchestration workflows from Tidal to Control-M, improving efficiency and reducing manual intervention.

·       Monitor, research, analyze, and report problems to programmer or developer

·       Day to day administration of Control-M/EM Server and its components, production batch schedules and ensure continuity of business services.

·       Create new jobs in Control-M on Windows

·       Support the Control M Admin Team for Migrating the jobs

·       Manually create Control M jobs with the same functionality

·       Build and manage job flows, calendar requirements and scheduling criteria.

·       Passing parameters to Control-M job, creating job dependencies and alerts as per application team and business requirement.

·       Creating and Scheduling jobs on the Control-M tool in both Distributed and Mainframe Environment (Test and Production)

·       Develop automated testing scripts using Shell and Python to validate Control-M job functionality and dependencies across various environments (Test, QA, Production).

·       Implement Shell/Python scripts for automated deployment of Control-M job definitions and smart folders, ensuring consistent and error-free migrations between environments.

·       Using the Reporting Facility to create reports

·       Maintaining the shift turnover, which includes the current and the pending information from one shift to another.

·       Write Shell scripts to simulate various Control-M job failure scenarios during testing, ensuring robust error handling and alerting mechanisms were in place.

·       Support migration initiatives preparing for Helix Control-M adoption, including workflow analysis, automation standards, and SaaS-readiness validation.

·       Conduct proof-of-concept testing for Helix Control-M cloud integration with AWS-hosted workloads.

·       Support Agile ceremonies, embedding with teams to align batch workflows with business requirements.

·       Used Service Now for all scheduling requests for Production, Incidents, and Problem