SUMMARY:

• Testing medical, travel, insurance, telecommunications, geological, banking, military, FDA and FAA applications, 911 emergency applications.
• Testing using Oracle databases, networks, web (Java), firmware, O/S installation (all Microsoft operating systems), GUI’s, telecommunications, protocols (T.25, X.25).
• Client/server testing, web based testing, audits, data conversion, communication protocols, load testing, process improvement, software auditing, customer support, and data mining.
• Telecommunications test lab manager, medical devices, telecommunications switches and servers. Client/servers on large database arrays, emergency telecommunications.
• Company Quality Assurance consultant for Software and Testing processes and audits. Have utilized the Capability Maturity Model (CMM) and Software Maturity Index (SMI) to upgrade companies testing procedures.
• Training in software quality techniques, C, telecommunications, lifecycles, UNIX, hardware testing, test auditing, security, management training, SQL, and HTML.

EXPERIENCE:

Confidential

Senior Software QA Engineer

Responsibilities:

• Established Agile QA methodology for a company with no methodology. Included defect reports, test cases, user advocacy, use of regression, functional, smoke, ad hoc testing, and release protocols.
• Responsible for testing a document translation application that included input documents, translated documents, translation bids, translation vendors, billing, and roles/rights.
• Wrote test plans, test cases, defect reports, and post morta.
• Defect tracking was performed on Microsoft TFS.
• Tested software updates, customer problems.
• M entored an employee with no QA experience.

Confidential

Senior Software QA Engineer

Responsibilities:

• Tested Avaya and Asterisk telecommunications and workstation software used for emergency call centers.
• Tested hardware and/or software updates, customer problems, proposed modifications in an Agile environment.
• Responsible for a test lab with Avaya and Asterisk telecommunication equipment, 25 workstations, SIP, CAMA trunks, call and workstation servers with clients, software and hardware configuration and updates.
• Wrote test plans, test cases, defect reports, post morta, and training documentation .
• Defect tracking was performed on SalesForce, which was moved to Microsoft TFS.

Confidential

Software QA Engineer

Responsibilities:

• Tested medical publications websites, consisting of over 40 publications databases and five search engines.
• Tested PayPerView and subscription access for websites.
• Payment types included PayPal, all major credit cards, checks, and cash.
• Wrote test plans and manual test cases on SeaView s TTP system.
• Defect tracking was also on TTP. Project planning, certification statements, and update statements were archived on SeaView s SCM system.
• Acceptance, regression, integration, and functional testing at a black and grey box level.

Confidential

Software QA Engineer

Responsibilities:

• Tested security for a series of hospital networks.
• Tested a wireless system for Baxter infusor pumps, ventilators, and GE and Phillips monitors.
• Performed verification and validation in a device test lab as well as onsite pilot testing at two regional hospitals.
• Tested throughput at various hospital divisions, in the Salt Lake area for the equipment mentioned above. I.e, bench tested the equipment, and, during alpha phase, tested the same equipment at the hospitals.
• Tested networking for Emergency Department and clinical documentation.
• Tested ADT networking and throughput.
• Wrote test plans and manual and automated test cases on Mercury s QTP/HP Quality Center.
• Defect tracking was also on QTP. Regression, integration, and functional testing were performed.

Confidential

Software QA Engineer

Responsibilities:

• Testing also included the OCRM telephony configuration tool, to confirm switch accuracy.
• Testing occurred on Win XP to UNIX for data file imports.
• Tested Confidential s OTRM toll free routing tool. Sonus switch configuration tool was used to confirm switch accuracy.
• Tested Confidential s LRM local resources manager routing tool with the same configuration tool.
• Wrote test cases on Rational s TestManager, defect tracking on ClearQuest, regression and functional testing in all functional areas (AcuRate, AcuRoute, AcuServe, AcuCDR, OTRM, and LRM).
• SQL was used to confirm correct database functionality.

Confidential

Software QA Engineer

Responsibilities:

• Tested the 2006 version of Confidential (Save and Restore)
• Testing occurred on VM software, Windows XP Pro English and Polish, using standalone and networked PC’s.
• Rewrote test cases, performed beta testing, install testing (iso and ESD), and regression testing
• Expanding Boeing’s aircraft to ground communication system through ground stations or satellite transfer.
• Testing was to include synchronous communication of aircraft and fuel problems, pilot communications, flight instructions, weather displays, and maps, scheduling and rerouting information
• Was lead Q/A person, wrote validation and verification test plans, was tasked to set up the test lab and track equipment.
• Project and position ended in May after three months.

Confidential, Boulder, CO

Senior Q/A Engineer

Responsibilities:

• FDA testing information from a drug database, which could be downloaded through a medical server (Medical Management Unit) to a series of Abbott infusion pumps.
• Front to back testing of the component system was tested, with emphasis on the communication between the server and the pumps.
• Wrote test plan and traceability matrix, with emphasis on the communication links from the server (MMU) to the infusion pumps.
• Testing corresponded to Abbott Laboratories standards, which reflected FDA Part 21, Part 820.

Confidential, Denver, CO

Senior Q/A Engineer

Responsibilities:

• Project consisted of conversion of five EBCDIC legacy system databases into Oracle based database.
• Data mining, conversion, and user acceptance testing performed.
• Rational was used as an automated, manual test, and bug recording platform for this project.
• Test scripts were written to check and record results on the client side of the project and record bugs whenever they occurred.
• Testing consisted of actual benefits cases, where converted data was checked against five legacy systems, through a Tuxedo 3270 cutthrough to the legacy data, and a Windows GUI application for the converted data. Data was chosen through data mining techniques from the legacy systems to the new database.
• Testing consisted of accessing the pertinent legacy systems, tracing the data through the data mining rules, and checking the results on the database, through the GUI access screens.
• Total number of allowable benefits could exceed one hundred.
• Performed test audits of data conversion cases, performed user acceptance testing of new, converted database from actual cases.

Confidential, Denver, CO

Q/A Engineer, Network Administrator

Responsibilities:

• Short term contracts as a Q/A Engineer, networking for various contract firms.
• Applications included light network maintenance and setup for offices, testing web based and UNIX applications, writing and testing test cases, installing Windows operating systems and application software.

Confidential, Denver, CO

Senior Q/A Engineer, Test Lead

Responsibilities:

• Tested mainframe client/PC server data, interfaces, and protocols on the third largest database in the world.
• Testing included pricing, rates, five search engines, new versions, regression testing, correct data presentation, for seven major airlines, all major car rental agencies, and all major hotel chains in the world.
• Database access used a series of TPF commands and search engines through a T.25 cutthrough.
• Hardware applications ranged from a hardwired terminal to database, to GUI and web based applications.
• Protocols were T.25, X.25, and TCP/IP, and were checked with a protocol sniffer.
• Responsible for installing all Microsoft Operating Systems and applications in both English and foreign language versions.
• Tested applications, including installs, on hardwired PC’s, cutthroughs, Internet, and host.
• Performed white box, gray box, and black box functional regressions, and protocol testing for hardwired, cutthrough, and web - based clients.
• Wrote automated scripts on Confidential ’s QA Director. Automated scripts were run, initially against server information, which was checked against the client information.
• Developed an archival library, with a unique filing system, for all application projects (i.e. managers’ project time lines, data for new recruits, and quality metrics).