SUMMARY:

• Dedicated, analytical and performance driven professional experienced in ETL and Mainframe technologies. I have 5.5 years of experience working with Healthcare and Financial clients viz., Aetna, Confidential, Confidential and Confidential . Extensively worked on COBOL, JCL, DB2, IMSDB, CICS, Fileaid, Endevor, Changeman, TSO, JobTrac, Control - M and Xpeditor, using SDLC 2.0 model, Waterfall and Agile methodologies. Additional skill set includes Informatica, Teradata, Cognos, Java, Selenium and Project management.
• I have extensively worked with JCL, COBOL and DB2 in Data warehouse projects.
• I also have good exposure to the ETL tool Informatica, to extract data from Teradata using maps.
• Dealing projects with a “Software Development Life Cycle” approach:
• Requirement Gathering Analysis Design Development Testing Implementation and Warranty Support has been systematically practiced in my projects.
• An effective communicator with good interpersonal skills.
• Experience in preparing Use Cases, Sequence diagrams, Activity diagrams,Class diagrams.
• Skilled at reviewing test cases and making sure they are in accordance with requirements and to assist the overall testing process by Change and Defect Management methods.
• Strong understanding of various SDLC methodologies such as Waterfall, Agile with hands on experience in both of them
• Good analytical skills in understanding the business process, the functional requirements and translating them to system requirement specifications.
• Attended various in-house soft skill and management development programs.
• Completed 6 months of intensive and coaching program at Infosys, India with overall CGPA of 4.5 out of 5
• Completed in Mainframe technology at Infosys, India
• Completed STAR at Infosys, India.
• 433 TS- Microsoft SQL SERVER 2008 Database Development .
• IBM certified database associate.
• Completed Infosys internal s, every semester, to keep up with the developments in Software industry
• Trained to have the GDM (Global Delivery model) perspective towards our projects
• Microsoft Certified Technology Specialist
• Oracle 9I and Advanced/Core Java programming

TECHNICAL SKILLS:

Databases: DB2, IMSDB

Platforms: Z/OS, Windows XP/2000, Windows 7

Mainframe Technologies: JCL, VSAM, Easytrieve

Online Transaction Processor: CICS, IMSDC

Special Utility Software: FileAid, File Manager, Xpeditor, SPUFI, Endevor

Schedulers: CA7, JobTrac, Control - M

Claims processing System: NASCO

File transfer methods: NDM (mf to mf),FTP (mf to other systems),SFT (Secured),XCOM

Client systems: Citrix, Clarity, SharePoint, IMR(Incident Management Request), CMR(Change Management Request), Manage Now, IM Plans

Environment: Client - Server (MainframesMVS/OS390)

Client regions: EMEA market, France, Italy markets

PROFESSIONAL EXPERIENCE:

Confidential

Sr. Programmer

Responsibilities:

• Work with team to do Impact Analysis, Unit Testing, providing support for System Integration testing and Implementation Activities
• Extensive calls with stakeholders of the change under concern
• Code programs to accomplish the change
• Coordinate with offshore to complete the construction of the code
• Responsible for creating SNOW requests to create packages and to promote components
• Raising incidents to direct the production job fixes
• Coordinate with Command Centre and Operations team to follow up on incidents raised for job fixes
• Developing Contingency projects
• Handle test and production defects
• Working on RTC and RDZ. Created APPBUILD scenarios (AER) for various user stories.
• Work closely with Scrum masters through all the phases of the project.
• Estimate effort for deliverables.
• Tracked defects in HP quality center and get in defect calls to discuss the optimal resolution

Confidential

Systems Analyst

Responsibilities:

• Work with team to do Impact Analysis, Unit Testing, providing support for System Integration testing and Implementation Activities
• Extensive calls with other vendors of Amex for this project to coordinate the precise responsibilities to be shared
• Code a program to identify the redundant programs in Jobtrac to exclude them from migrating to Control M
• Automate the insertion of the vital parameters in each job on Jobtrac to be interpreted by Control M
• Migrate a batch of 5000 dummy jobs in a mock batch execution and fix all the errors
• Responsible for the first set of jobs in live migration by maintaining an excel to monitor the migration, hold the jobs which fail, analyze them to take a call to either fix or reschedule that job in the next migration
• Led a team of two members of the team to handle subsequent migrations
• Warranty support to ensure that migrated jobs would not abend in Control M
• Responsible for monitoring the Incident management queue and flagging an abended job before the client support team flags it. Fix the issue according to the criticality to ensure that scores stay high
• Responsible for directing other system jobs to their respective queues. This involved clear understanding of other involved system and their footprint jobs
• Worked on managing clarity timesheets. Involved follow up with the erroneous time sheets from other folks, rectifying them and after a sign off it would be sent across on a weekly basis

Confidential

Systems Analyst

Responsibilities:

• One of the 3 members in the project who supported it till the last phase of the project
• Later Confidential projects were purchased by another vendor and I was actively involved in transitioning all the knowledge in great detail
• Received appreciation for a neat and professional transition of the knowledge to the new vendor
• Extensive documentation according to the CMMI standards was one of the key learning's in this project
• Classifying and taking a call on some of the unmarked jobs as HMO or PPO was very challenging. It involved in depth code study of the existing HMO and PPO jobs and all their possible variations
• Maintaining an excel sheet to perform extensive unit testing on the modified jobs
• Fix job failures which would abend due to Db2 bind issues as well
• Use QMF to extract the required data for appropriate analysis
• Learnt how to use IMS from other teams of Confidential since it was essential to understand if the job was failing due to what kind of data issue and thus make changes accordingly
• Create DB2 Packages and DCLGEN in a DCLGEN PDS for most DB2 tables to save overhead on the last minute creation of the copybooks. With the same name as table for the DCLGEN the coder merely needed to call the PDS with the member name in brackets. Later we automated the process of DCLGEN creation as well
• Resources were eventually released in short numbers according to the decaying work in this project as it was reaching completion and I was actively involved in routing the work distribution among the teammates, to my team lead
• Document all our Design and test documents in VSS for future internally
• Learnt how to handle situations where client would suggest modifications even after the requirements were frozen
• I was an active participant in the actual migration of jobs in batches
• I was involved in both development and testing
• Employed Informatica to create mapping.

Confidential

Systems Analyst

Responsibilities:

• Involved in analysis coding and testing and also maintaining the quality of the project in each phase
• SSCRs were challenging in the sense of their short delivery time, some having just 4 days to design, code and execute testing as well
• Managing time to complete these adhoc requests along with the actual work in hand was work that required adaptation
• SSCRs were numbered and I was responsible to keep a track to pile them in accordance for better understanding of the occurrence of these SSCRs and suggest a long term fix to my onsite who would then propose it to the client to make it a full-fledged project

Confidential

Systems Analyst

Responsibilities:

• Involved in analysis, coding and testing and also maintaining the quality of the project in each phase
• My first project ever was in a controlled environment called Aetna ODC where the system norms were different from my regular Infosys work stations
• Adhering to all the rules and following the standards as per the ODC norms took time
• Analyze job failures and fix them or escalate them
• Document all the fixes to save time on the repeated job failures