CVS Health (client) Logistics Open Systems teamSupporting Warehouse Management applications such as Lucas, Exacta and WMS among others by taking ownership of deploying updates and patches to existing builds as well as implementing new server builds in Windows and Linux environments across the different Distribution Center sites.

Citibank (client) Treasury Investment Management System team• Monitoring and overseeing batch processes related to TIMS and resolving Prod related issues by analyzing Autosys and shell script logs. Working together with L2 teams to close incidents in SNOW.• Personally responsible of doing all UAT deployments for Dev teams during my shift. This required Change Request creation in Service Now and requesting approvals for promotion of different types of objects such as: scripts, code packages, database procedures, Autosys JILs, among others.• Data extracts/imports across environments upon request from other teams in Oracle SQL Developer. Delete, update, insert data into tables, modify sequences, handle constraint issues, etc. • File feeding setup in Linux systems for Dev and BA teams testing purposes. Transferring files via sftp, compressing with gzip, handling file permissions, manually triggering shell scripts, etc.• Manual execution of Autosys jobs in lower environments for testing purposes.

Nike (client) @ Nike World Headquarters• Resolution of AutoSys related issues like: job failures, chase alarms, job permissions, unresponsive agents, high latency in scheduler machine, connectivity issues with job host servers, WCC slowness, etc.• System Administration of AutoSys system tools such as: Workload Automation (formerly WCC), EEM, Workload Automation iXp, Automic Automation Intelligence (formerly JAWS).• Use of Service Now for handling tickets such as Incidents, Tasks, Change Requests, etc.• Batch solutions for functional teams as part of the Advanced AutoSys and Batch Coordinators team.• Implementation of new batch processes through Autosysweb’s jobdoc (inhouse web-based tool). Impact Analysis of new jobs and changes to existing jobs, scheduling and dependency constraints, etc.• Server OS patching of all Autosys servers across all environments: Prod, Release, Dev and SUP through Rundeck and other automated shell scripts put in place by our team.• AutoSys agent installations on Windows servers. Setting up log folders with the right permissions and testing communications between the job host server and the AutoSys scheduler. • Virtual machines definition and repointing to different servers after migrations. • Ramp down and ramp up for batch processes during cloud migrations and monthly releases.• Representation of 2 different teams at business meetings: Automation Operations team (as the tech-lead) and the Batch Coordinators team.• Maintenance of documentation on the wiki/confluence page. • Research about batch history execution and timelines through Splunk for reporting purposes and trend analysis. Setup of new alerts and simple dashboards for other teams in Splunk using Autosys’ output logs.

Florida Medicaid project• C Programming: code implementation and patching of the system’s processes through COs (change orders). Use of object-oriented programming methodologies. Eclipse and Notepad ++ IDEs. GNU compiler, GDB debugger.• AutoSys: solid knowledge of the JIL interface. Job execution, maintenance, scripting and handling. • On Call: 2 weeks every 6-8 weeks of “On Call SE” duties (1 primary, 1 secondary). Duties include addressing system failures and program crashes, checking the daily cycles to ensure their successful completion and any issues that may arise throughout the week. Often times working overtime and overnight in order to debug system failures, under pressure and against the clock as several processes needed to finish by a certain time. Writing tasks for cycle monitors on the fly to rerun the failed processes, re-promote programs, etc.• Oracle SQL: used to access the system's database and research data. Programs in C contain embedded SQL cursors and queries for data processing.• UNIX: system runs on UNIX machines. Daily use of shell commands to access and navigate the various testing environments and one Production environment.• Documentation: design, implementation and unit test documents for every CO worked on. Walkthroughs with other SEs for implementation/promotion approvals. Use of (.diff) files for comparison between old and new code.

Computing instructor/professor at several community centers, public institutions; teaching students basic computer operation and programs such as: Microsoft Visio, Excel, PowerPoint and Word.