Application Support Analyst Resume

OBJECTIVE

To work in a challenging and dynamic environment where I can apply my knowledge and experience to achieve the organizational and personal excellence.
Effectively use my skills and gained knowledge to perform my professional roles.

SUMMARY

Having 8 years of experience in multiple skill set with ETL tool - Ab Initio, Data Stage.
Team Player in Agile Methodology.
Ability to adapt quickly to new environments and technologies
Good problem solver gathering as much information as possible and let intuition, logic and innovative thinking drive the best solution. Working with others to find the best solution.
Had Proven team player who works well alone, with little or no super vision or as part of group.
An effective communicator with excellent interpersonal, logical thinking & analytical abilities.

TECHNICAL SKILLS

ETL Tool: Ab Initio, DataStage

Languages: SQL, Unix

Web Based Tools: ALM, Jira, Git

Database: Netezza, SQL server

BI Tool: Inquiry Framework

Scheduler: Operation Console, Ops Portal

FTP tool: Tectia file transfer, WinSCP.

Ticketing Tool: Service Now

Reporting Tool: Cognos Tester

PROFESSIONAL EXPERIENCE

Confidential

Application Support Analyst

Responsibilities:

Expertise in gathering functional requirements and providing work effort estimate.
Proactive monitoring loads in Production. Handling BAU requests and ensuring they are resolved within the agreed service level agreements (SLA).
Tested CR’s as part of enhancement and provided sign off on behalf of UAT environment so that implemented in Production release.
Responsible for generating various Reports on Daily, Weekly and in Monthly basis.
Resolving the failures occurring in Ab initio plans on time.
Perform all tests on production applications and prepare recovery procedures for all applications and provide upgrade to same.
Coordinate with various teams and raise support ticket for all issues, analyze root cause and assist in efficient resolution of all production processes.

Confidential

Test Analyst

Responsibilities:

Prepare the status report of testing activities.
Generating performance goals and test plans.
To check if testing is going hand in hand with the software development in all phases.
To check if the team has all the necessary resources to execute the testing activities.
Performance Testing: Interacting with business analysts and development team; discussing performance requirements and loading test strategies; generating performance goals and test plans; analysing user and business requirements and functional specs; using case documents to create test scenarios, and validating the integrity constraints

Confidential

Test Analyst

Responsibilities:

Work with developers, project managers and operations engineers to define, manage and execute milestone of each release.
Build and align the organization’s release Calendar, working closely with development managers.
Perform risk analysis, planning and approvals for late admissions into scheduled releases and for all changes not in a scheduled release
Create Key metrics and Identity opportunities to make tactical improvements to the release management process.
Tracking post go-live issues and performing statistical analysis.
To act as coordinator for the local release management team and the global team, Track status of releases, Provide guidance to local team members.
Manage activities between Release management and the following functions: change management, problem/Incident management and Q/A Testing.

Confidential

Developer, Test Analyst

Responsibilities:

Involved in the full life cycle of extracting the data from the Mainframe, different validations, and standardization steps before loading the customer data to the CIS
Involved in the whole life cycle in getting the data from Prod EME and making necessary changes accordingly to the parameter changes, using generic graphs, plans.
Involved in String testing done by the developer.
Prepared different plans and graphs as needed for the project.
Migrating the code to different Environments
String Testing at ETL end
Necessary JCL changes