SUMMARY

• Ten Plus years of work experience in IT industry.
• Areas of Expertise include Business Intelligence, ETL Tool Ab Initio, Unix Shell scripting and Oracle Database.
• Extensively worked on AbInitio Conduct - It, Multi file system, Meta Programming, conditional Components, Partitioning and Departitioning components. Knowledge of Continuous flow components.
• My main area of experience has been project delivery of various sizes. I have worked in the domain of Financial services, Insurance, Retail, Banking and Life science & Healthcare.
• Good Knowledge of Data Warehousing Concepts.
• Ability to understand and resolve Data warehouse issues.
• Exposure to ETL Tool Informatica, Teradata.

TECHNICAL SKILLS

ETL Tool: Ab-Initio GDE 3.2/3.0/1.14/1.13/1.11 Co-operating System 3.2/2.15/2.14/2.13/2.11 , Informatica

Operating Systems: Windows 2000/NT/XP, HP UNIX, UNIX (Solaris), AIX.

Programming Languages: UNIX Korn Shell Scripting, SQL, PL/SQL

Source code control: Ab Initio Repository (EME)

Database: Oracle, Teradata, DB2

Scheduling Tool: TWS, Autosys

PROFESSIONAL EXPERIENCE

Confidential

ETL Developer

Responsibilities:

• Analysis of Requirement and functionality and prepare the Mapping document in design phase.
• Work with source teams to get the data and load the data into the COMRAD system.
• Worked on Citi’s Annual Risk Assessment Reporting which involved building a centralized and automated system for collection of data from multiple sources. This will assist the Risk Assessment Team to analyze the data and complete the Risk assessments in a precise and efficient way.
• Designed the graphs based on the transformations and mappings provided in the requirement.
• Designed the generic graph to load the data from different regions. Extensively used metaprogramming techniques.
• Code Automation and Scheduling the jobs using AUTOSYS.
• Prepared the technical design document.
• Preparation of Test Cases and Unit Testing of the graphs.
• ETL troubleshooting (Problem Determination/Resolution). Problem solving ability to provide time critical production fixes without impacting the financial data integrity.

Confidential

ETL Developer

Responsibilities:

• Work with the global/Regional business owners to understand the requirement and get a BRD walk through.
• Design & Development of end-to-end ETL applications,
• Work with Front end(Reporting) teams to understand their data display capability.
• Developing generic solutions to handle ever growing need of data processing from multiple sources.
• Designing graphs based on the transformations and mappings provided in the requirement and load data into the tables.
• Estimation and Design for the systems to be enhanced/ developed following standard models
• Strong working knowledge of Data Warehousing techniques and Concepts experience including ETL processes, Star Schema/Snowflake Schema.
• Scheduling the jobs using AUTOSYS.
• Preparation of Test Cases and Unit Testing of the graphs.
• ETL troubleshooting (Problem Determination/Resolution). Problem solving ability to provide time critical production fixes without impacting the financial data integrity.

Confidential

ETL Developer

Responsibilities:

• Project co-ordination with the business users for requirement analysis.
• Design & Development of end-to-end ETL applications,
• Designing graphs based on the transformations and mappings provided in the requirement and load data into the tables.
• Automation of the Jobs execution after creation of Webforms.
• ETL performance tuning, ETL design consulting, ETL Code Migration.
• Creation of wrapper scripts to execute the process from the backend.
• Preparation of Test Cases and Unit Testing of the graphs.
• Code Review of the Project to verify whether it abides to the Kaiser standard.
• Submission of quarterly Mandatory secondary Payer Report to Centre of Medicare services (CMS).
• Use of different Ab Initio components and different functions.
• Unit Testing the Graphs once development is complete.
• ETL troubleshooting (Problem Determination/Resolution). Problem solving ability to provide time critical production fixes without impacting the financial data integrity.

Confidential

ETL Developer

Responsibilities:

• Estimation of work and prepare project plan, Low level design and detailed design documents in order to get a clear understanding of the design flow.
• Developed Ab Initio Graphs, plan> It and wrapper scripts.
• Designed and developed the code for Data Migration from one database to another.
• Involved in manual testing and unit testing to check whether the data in both the databases is in sync.
• Participated and took effective role in Knowledge sharing and meetings with the client.
• Perform ETL software upgrades, ETL source code control management.
• Use of IQMS for quality purpose to log the defects, track them and fix them.
• ETL troubleshooting (Problem determination/ Resolution).
• Ab Initio code migration using .SAV package once Testing is complete.
• Ab Initio performance tuning techniques to enhance the performance of the Ab Initio graphs.
• Successfully deployed the graphs from the Development Repository to Testing Repository and Production Repository.

Confidential

ETL Developer

Responsibilities:

• Understanding the complete business flow.
• Communication with the Client on regular basis for requirement gathering and analysis.
• Designing graphs and mappings through Ab Initio in order to Import and export the data using transformations.
• Design, Planning & Development of end-to-end ETL applications, Work distribution among team members
• Involved in UNIX shell scripting.
• Designing graphs for Data Migration from one module to another.
• Data Modelling, Data Warehouse/ Data Mart Design.
• Preparation of low level design and high level design.
• Creation and modification of new and existing database objects and the corresponding loading scripts as per the requirements.
• Used .SAV package to migrate the Ab Initio code from dev server to prod server.

Confidential

ETL Developer

Responsibilities:

• Understanding the existing business model and customer requirements.
• Providing support and enhancing the applications.
• Implementation of the application changes.
• Designed and developed the Codes for maintaining the Databases for various Entities and Procedures that had the entire complex Business Logic.
• Worked on improving the performance of Ab Initio graphs by using various Ab Initio performance technique’s like using lookups instead of Joins.
• Validations of the codes to ensure the changes are compatible to business rules. This helped the system testing and E2E testing in a smoother way. Giving regular updates in scrum calls and Client calls. Also arranging calls to discuss the issues with the E2E team and probable resolution for that in a quick time. This had made the delivery in a much smoother way.
• Used IQMS for quality purpose to log the defects, track them and fix them.
• Created wrapper scripts to run the graphs.
• Used CVS for version controlling.
• Created Test plans and Test scripts for manual testing.
• Involved in code migration to production server.
• Monitored the job and resolved the CRs.

Confidential

ETL Developer

Responsibilities:

• Understanding the existing business model and customer requirements.
• Worked in the Update Module, as a part of the Update team.
• Involved in creation of best practice document for Ab Initio.
• Worked as an ETL Developer, understood the client requirements and translated it into codes.
• Involved in the preparation of High Level documents.
• Designing ETL activity graphs through Ab Initio & Teradata Utilities. Used most of the AI components.
• Updating DMLs and XFRs to the existing Graphs according to the customer requirement.
• Ab Initio performance tuning techniques to enhance the performance of the Ab Initio graphs.
• Preparation of Test Plans, Test cases and Test scenarios for Unit Testing once development is complete.
• Used EME for check in & check out graphs and version controlling.
• Running scripts of Ab Initio graphs in UNIX environment.
• Created and tested TERADATA and UNIX scripts.
• Involved in code migration to production server.