Senior QA Engineer Resume

SUMMARY:

Software test and management professional with extensive experience in all phases of the software development lifecycle (SDLC)
As Programmer/Analyst, Project Manager, System Tester, Test Technical Lead and Test Project Manager, exceptionally skilled in communication with all SDLC participants
Highly effective at reaching consensus on issues from all levels of management throughout the software development process
Especially adept at fitting project scope into schedule and budget
Specific experience in the area of system test audit, determining test effectiveness from a quality assurance perspective

BUSINESS PROFICIENCIES:

TECHNICAL PROFICIENCIES:

Languages: COBOL, MicroFocus COBOL, IBM JCL, Dbase III

Software Applications: Microsoft Office Suite/ LotusNotes

Hardware/Operating Systems: AS400, IBM PC/Microsoft Windows NT/98/7/XP

Software Tools: HP Application Lifecycle Management (ALM), Quizinator, MS Project, Mercury WinRunner and TestDirector

PROFESSIONAL EXPERIENCE:

Confidential

Senior QA Engineer

Responsibilities:

Contracted to Confidential End - to-end (E2E) flow-through network activation testing
Advise E2E test manager in areas such as configuration management, test analysis, etc.
Manual testing of applications in E2E environment (service order creation, provisioning, etc.)

Confidential, Denver, CO

Software Tester/Mainframe (AS400)

Responsibilities:

Contracted to Confidential for contract to Frontier Communications
Test Frontier systems for turnover to IBM
Testing includes service order creation and processing, provisioning and billing
Monthly releases; all testing completed on time

Confidential, Colorado Springs, CO

E2E Test Project Manager

Responsibilities:

Coordinate with systems engineers to determine systems required for testing and manage the build and connectivity of the test environment.
Coordinate with individual managers to ensure availability of testers for each system in the environment.
Determine order information required and oversee the creation of the input data.
Via screen shots/data dumps, oversee data accuracy through various systems in the environment.
Validate output invoice and obtain user signoff by means of formal invoice review.
Testing uncovered errors that would have caused the billing option to fail if released to production; production release delayed.
Priority PCR produced the necessary software changes and subsequent E2E testing proved successful.
The annual billing option was released to production on the new schedule and was error free.

Confidential, Denver, CO

Test Project Manager

Responsibilities:

Analyze requirements for testability and results verification.
Review, forecast and negotiate and budget requirements.
Create, coordinate and finalize Master, System, User Acceptance and Final Test Plans.
Solicit for, interview and hire a test team from available contracting companies and within budget constraints.
Manage test team and testing progress; respond appropriately to changing schedules and requirements.
Create and brief to upper management daily and weekly test status reports.
Manage defects through resolution.
Online search rewrite was released to production on schedule and within budget.
By the 90-day point in production, no errors had been reported.

Confidential, Denver, CO

E2E Test Manager and Technical Lead

Responsibilities:

Lead the interoperability, pre-production testing of an E2E environment consisting of all priority software applications/systems, both mainframe and midrange, within Confidential .
Administrative management of a 40+ member team consisting of employees and overseas consultants.
Analysis of all new and regression requirements for interoperability testing.
Ensure that planned test cases fulfill all requirements.
Lead testing via conference calls and, via screen shots/data dumps, oversee data accuracy through various systems in the environment.
Validate output bills and obtain user signoff by means of formal review.
Regular E2E testing uncovered a great many errors that would have caused production order processing to fall back on manual handling.
Because reliance on E2E testing became so heavy, I reorganized the testing into 2 teams on 2 separate conference calls.