Sr Software Engineer Resume
PROFESSIONAL SUMMARY:
- Having 4 years 6 months of experience in ETL/DWH testing, Cube Report Testing, BI Report Testing, Manual Testing
- Working on ETL testing, tested ETL Informatica mappings and other ETL processes (data Warehouse testing).
- Expertise in ETL testing /DWH testing.
- Good knowledge on Data warehouse concepts.
- Having good knowledge on BIGDATA.
- Good knowledge on SDLC, STLC, bug/defect life cycle.
- Worked on different domains like telecom, retail, health care.
- Proficiency in working on Cube report testing.
- Proficiency in working on Microstratagy Report End to End Testing.
- Skilled in writing SQL queries.
- Having knowledge in writing hive queries.
- Proficiency in working on Tidal scheduling tool and Oozie.
- Well versed with Informatica power center & ESP scheduler.
- Proficiency in working on HP ALM (test management tool).
- Excellent inter - personal, writing and oral communication skills.
- Proven ability to work with aggressive deadlines on multiple concurrent tasks.
- Prepared KT documents & giving KT sessions
- Experience in conducting peer reviews & walkthroughs
- Prepared RTM document to Trace the project work status.
- Done sanity checks after deploying in ST environment
- Assigning work within the team & tracking the work status
- Handled team size of 4
- Prepared test data.
- Sending DSR to onsite LO people.
CORE COMPETENCY:
UNIX Access Tool: Putty
ETL Tool: Informatica, ESP Scheduler
Operating Systems: Windows & UNIX
Database: Oracle.
Data Management Tools: Hue, Toad, SQL Developer, SQL Plus, SQL SERVER
Scheduling Tool: Tidal
Scripts: UNIX
Reporting Tool: IAM Analyzer(Cubes), Microstrategy
Data Migration Tool: Beyond Compare - 3
Test Management Tool: Quality center, HP-ALM, Jira
PROFESSIONAL EXPERIENCE:
Confidential
Environment: SQL SERVER-2014, Putty, Unix, Informatica, beyond compareHP-ALM, Jira
Sr Software Engineer
Responsibilities:
- Understanding & Reviewing (BRD & Mapping Documents).
- Attending walkthrough’s and understanding the requirements.
- Picking up the User stories from JIRA.
- Writing Tests Cases & reviewing internally.
- Getting approval from BA for Test cases after review.
- Sanity check done after deploying to SIT Region.
- Assigning work with in the Team.
- Checking the naming convention for received Source files.
- Checking the database tables before running the jobs.
- Running Informatica jobs through Unix.
- Checking the logs in Unix
- Validating the target tables with business requirements by writing SQL Queries
- Following up with development team to resolve the bug’s
- Every day Updating the daily work status in Standup call to SCRUM master.
- Logging defects in ALM
- Every day Involved in Defect call and getting ETA for defects
- Preparing RTM DOCUMENT to trace the defects based on ALM execution
- Interacting with the onsite Test lead for time lines.
- Traking the Project (sprint’s) status in JIRA
- Sending DSR to Onsite Test Lead.
Confidential
Environment: SQL SERVER-2014, Putty, UNIX, KF Clients, ESP Scheduler, HP - ALM, HUE, Oozie, Microstrategy
Sr. Test Engineer
Responsibilities:
- Understanding & Reviewing (BRD & Mapping Documents).
- Writing Executing & Reviewing Tests Cases.
- Sanity check done after deploying to SIT Region.
- Assigning work with in the team.
- Running files from KF client to INPUT TABLES.
- Running jobs in ESP scheduler to load data into TDW.
- Back Data Correction done if needed in TDW.
- Integration Testing has done for all components.
- Verifying the Populated data in target database from Source database.
- Data Imputation done through KF Extract to DI and checking the status in OOZIES.
- Checking table’s data in HIVE.
- Validation of data has done by writing Hive queries.
- Writing SQL Queries to validate data.
- Validating the Reports built from MSTR by writing SQL queries
- Following up with development team to resolve the bug’s
- Every day Involved in Defect call
- Preparing RTM DOCUMENT to trace the defects
- Tracking the work status in ALM & Sending DSR to onsite LO people.
Confidential
Environment: SQL SERVER-2014, Putty, UNIX, IAM Analyzer, HP -ALM
Sr. Test Engineer
Responsibilities:
- Understanding & Reviewing (BRD & Mapping Documents)
- Writing Executing & Reviewing Tests Cases
- Interacting with Onsite LO people and getting files
- Sanity check before triggering the cube build process.
- Triggering the cube by placing an event file in GLA path in (UNIX) and checking the status in ESP Scheduler.
- Building the cube in SQL SERVER.
- Structure validation done in IAM Analyzer
- Generated reports and done validations.
- Sending DSR to onsite LO people.
Confidential
Environment: Oracle, SQL Developer, Putty, UNIX scripts, Informatica, BeyondCompare, winscp, Green Shot, HP -ALM
Sr. Test Engineer
Responsibilities:
- Understanding & Reviewing (BRD & Mapping Documents)
- Writing Executing & Reviewing Tests Cases
- Preparing Test Data as per the requirement
- Assigning Work within the Team& Tracking the Work Status
- Checking Workflow entries in Meta Data tables
- Sanity Checks before running workflow.
- Running the Batch scripts based on Batch Id’s
- Running the read trigger file scripts based on Job Id’s
- Running the Audit scripts after loading data in particular batch
- Running Informatica workflows through UNIX Environment based on Job Id’s
- Checking status of workflow in Unix workflow logs (Param file, Log file, Log.bin File)
- Tracking the running status in Informatica monitor
- After running workflow checking the entries made in metadata tables
- Verifying the Populated data in target database from Source database
- Following up with development team to resolve the bug’s
- Every day Involved in Defect call
- Preparing RTM DOCUMENT to trace the defects
- Reporting daily testing status report to Onsite Test Lead
Confidential
Environment: Oracle, Informatica, Tidal, Toad, Quality Center, Cognos DashboardExcel Sheet
Test Engineer
Responsibilities:
- Understanding Functional Document
- Participating in Client Calls Promptly Raising Queries About Incomplete, Conflict & Testability Of User Requirements
- Test Execution Within the Agreed Timescale & Collate, Analyze and Record: Defects (Reporting Thru Qc
- Involved in Testing Data in Target Database After Running Work Flows
- Extensively written SQL to confirm the data transfer from source to target.
- Reporting Issues / Defects Using Quality Center Tool with Test Evidence Along with Steps To Reproduce.
- Re-Testing (Confirmation Testing) the Defect and the Impacted Tests after Defect Fix.
- Following up with development team to resolve the bugs.
- Uploading Test cases from Excel Sheet to HP Quality center
- Generating Reports and Testing in Cognos Dashboard
- Writing Test Cases to Generate Reports for Data Validation
- Reporting Daily Testing Status.
