Senior Quality Assurance Engineer Resume Example
Love this resume?Build Your Own Now
SENIOR QUALITY ASSURANCE ENGINEER
Career Overview
I want to use the skills I have that help clients use your companies software to have complete success from the first time to the last time. I have always thought "better the issue happens to us in testing than to the client".
I want to help save jobs, save time, save our clients and have my employer to thank for it.
Qualifications
| Quality assurance Application testing Writing test scripts Writing test plans Bug tracking Reporting defects Automated test cases Software development life cycle Maintaining test environments Manual testing CRM JIRA CRM Salesforce Quick Test Professional Unified Functional Testing SQL for reporting and queries HTML Error re-creation Agile test method Crystal reports VMWare Microsoft Office Microsoft Windows (Client/server) SOAPUI Computer Hardware Network Hardware EMR EHR Cisco VPN Checkpoint VPN Sonic Wall Intersystems Cache for reporting and queries Remote Desktop Terminal Services Active Directory RAID Cabling Network Topology Norton Ghost Microsoft Imaging (Windows 7) Backup Procedures Disaster Recovery Encryption Network security Server Migration ANSI Standards HIPAA Compliance DOS SOAPUI Time Management ADDITIONAL ABILITIES I have strong organizational skills. I have proven leadership ability. I have proven teaching skills. I am professional and courteous to both co-workers and customers. I have excellent skills in customer complaint resolution both face to face and on the phone. I hold a secret security clearance (inactive). |
Work Experience
Senior Quality Assurance Engineer
July 2003 to April 2015General Motors － Roswell , GAAn issue (error) or the need for new functionality (enhancement) was reported by one of our clients or found by me or another Netsmart associate. A ticket would be made using Salesforce (Support) or JIRA (Quality Assurance) containing as much detail as possible (screenshots, descriptions and all data that lead up to finding the issue). The priority of the ticket was decided and notated by the client, the support representative or project manager and on occasion my manager. The ticket would be assigned to a software developer for research and an update (patch/enhancement) would be made. The ticket would then be assigned to a senior developer for Senior Technical Review. The senior developer then assigned the ticket to me. I would read all the supporting documentation and work with the developer to verify my understanding of the issue and get their opinion about what needed testing peripherally. I would on occasion connect to the client using a secure VPN and check settings for re-creation purposes. There were registry settings, option settings, open or closed charges and other factors. I would then have to estimate the Level of Effort; how long it would take to bring the ticket to a complete close, having manually and later run through automated testing, pass and have registered, and then post the update to our company website. Next would be the Expected Release Date of the update. This was based on priority, backlog and the function that was being affected. I would write a complex, step by step test plan that would duplicate the issue. It would start with the product versions and the function the reporter was attempting when they discovered the issue. I would then duplicate the issue on my local machine by following my own test plan to verify accuracy (usually performed in a VMWare environment). I would create screenshots to illustrate the test plan and use fictional client data for HIPAA compliance. I would work closely with the developer, the support representative and occasionally the client to verify all my steps and the result. Then I would create a backup copy of the entire environment with the issue duplicated. I would then install the update using the product update option in the software or by command line in the database. When the install was complete I would check visibility of the update in the database and in the current server option of the product. I would check the spelling and the vocabulary the developer used for the name and the description of the update. I would check the tables and fields affected and/or any new tables for fields created by the update by visually checking and running queries against the tables using Crystal Reports. I would use my test plan to bring me to the back to the point of the issue. If the issue appeared resolved, I would take screenshots of the fixed issue and add them to the test plan. Check the tables again by refreshing my report and running the queries using the new data. I would then check other options that had any tie to the option with the issue to verify other issues were not created (manual testing). I took screenshots of those actions, but not necessarily add them to the test plan. I would keep them for myself since they did not have any direct reference to the original issue. I would again work closely with the support representative and the developer to verify the issue was resolved. If the update only fixed issues or stored data from the time of update install, I would verify with the developer that this was already being addressed. I would verify a new ticket was written to discuss if or how past entries would be corrected. I would then start the Automation software (It started with Hewlett Packard QTP, then later UFT). I would perform my test plan of the fixed option and the automation software would record my actions and turn them into a script. I would check the script for accuracy. When complete, I would send an e-mail to the staff advising this issue was being moved to the automated testing phase and change the ticket status to pending. I would put my test script in a specific folder on the network and move the unregistered version of the update to a specific folder on the network for the automation group. The process would usually take about 24 hours so I would finish the test plan and prepare the update release notes. The release notes gave all the particulars about the update (summary of the fix or enhancement, size, date created, created by and tested by). I would receive an e-mail back advising the script had been run (along with dozens of other scripts created by all the QA engineers for regression purposes). If no errors were created, I would mark the update as passed and send the ticket to the original developer who would register the update and assign the ticket back to me. The registration process added a list of updates that were required prior to installation (I would not need them during testing because my test area was always up to date prior to starting). I would list the required updates on the release notes, zip the registered update and the release notes together and post them on the company website for our client to install. The registered update would also be added to Netsmart's monthly and quarterly updates for customers. I would then close the ticket and assign it back to the original support representative to notify the client about the update. If the update did NOT fix the issue or if the update caused another issue, I would: Immediately document the result of the installed update. I would show the developer who made the update my findings. They would verify the update was not ready. I would send an e-mail to the group advising of the fail and to whom I was re-assigning the ticket. I would fail the update on the ticket and re-assign it to the developer who would then make other modifications. The process would start again until the update was complete, the issue fixed and passed through the proper workflow. On top of my normal workload: I instructed the interns and juniors about how to do ALL OF THE ABOVE. I wouldreceive all updates involving EDI. This would include billing, remittance, eligibility denials and any other EMR/EHR. I was sent to client sites to teach them how to use Avatar Electronic Data Interchange/Electronic Billing, Remittance, Eligibility, Denials and special reports. I spent weeks at client sites in Iowa, Pennsylvania, Upstate New York, Wyoming and West Virginia on special assignment. My first 5 years at Netsmart was assisting in its development. I would verify HIPAA compliance and I was the only QA engineer who knew how to create the electronic forms. I would work nights. I would work weekends. I would work holidays to keep the backlog to an absolute minimum. I was assigned to special projects for clients with special issues. I was assigned more than once to the Netsmart War Room. This was a room that contained the brightest and the best to handle a special needs client. Some clients needed customization added to the core product. Washington State was my special assignment. I had to keep a running copy of a single client completely up to date at all times to test the customization. New York State had special forms and billing requirements. It was my job to keep track of those as well.
July 2003 to April 2015General Motors － Roswell , GAAn issue (error) or the need for new functionality (enhancement) was reported by one of our clients or found by me or another Netsmart associate. A ticket would be made using Salesforce (Support) or JIRA (Quality Assurance) containing as much detail as possible (screenshots, descriptions and all data that lead up to finding the issue). The priority of the ticket was decided and notated by the client, the support representative or project manager and on occasion my manager. The ticket would be assigned to a software developer for research and an update (patch/enhancement) would be made. The ticket would then be assigned to a senior developer for Senior Technical Review. The senior developer then assigned the ticket to me. I would read all the supporting documentation and work with the developer to verify my understanding of the issue and get their opinion about what needed testing peripherally. I would on occasion connect to the client using a secure VPN and check settings for re-creation purposes. There were registry settings, option settings, open or closed charges and other factors. I would then have to estimate the Level of Effort; how long it would take to bring the ticket to a complete close, having manually and later run through automated testing, pass and have registered, and then post the update to our company website. Next would be the Expected Release Date of the update. This was based on priority, backlog and the function that was being affected. I would write a complex, step by step test plan that would duplicate the issue. It would start with the product versions and the function the reporter was attempting when they discovered the issue. I would then duplicate the issue on my local machine by following my own test plan to verify accuracy (usually performed in a VMWare environment). I would create screenshots to illustrate the test plan and use fictional client data for HIPAA compliance. I would work closely with the developer, the support representative and occasionally the client to verify all my steps and the result. Then I would create a backup copy of the entire environment with the issue duplicated. I would then install the update using the product update option in the software or by command line in the database. When the install was complete I would check visibility of the update in the database and in the current server option of the product. I would check the spelling and the vocabulary the developer used for the name and the description of the update. I would check the tables and fields affected and/or any new tables for fields created by the update by visually checking and running queries against the tables using Crystal Reports. I would use my test plan to bring me to the back to the point of the issue. If the issue appeared resolved, I would take screenshots of the fixed issue and add them to the test plan. Check the tables again by refreshing my report and running the queries using the new data. I would then check other options that had any tie to the option with the issue to verify other issues were not created (manual testing). I took screenshots of those actions, but not necessarily add them to the test plan. I would keep them for myself since they did not have any direct reference to the original issue. I would again work closely with the support representative and the developer to verify the issue was resolved. If the update only fixed issues or stored data from the time of update install, I would verify with the developer that this was already being addressed. I would verify a new ticket was written to discuss if or how past entries would be corrected. I would then start the Automation software (It started with Hewlett Packard QTP, then later UFT). I would perform my test plan of the fixed option and the automation software would record my actions and turn them into a script. I would check the script for accuracy. When complete, I would send an e-mail to the staff advising this issue was being moved to the automated testing phase and change the ticket status to pending. I would put my test script in a specific folder on the network and move the unregistered version of the update to a specific folder on the network for the automation group. The process would usually take about 24 hours so I would finish the test plan and prepare the update release notes. The release notes gave all the particulars about the update (summary of the fix or enhancement, size, date created, created by and tested by). I would receive an e-mail back advising the script had been run (along with dozens of other scripts created by all the QA engineers for regression purposes). If no errors were created, I would mark the update as passed and send the ticket to the original developer who would register the update and assign the ticket back to me. The registration process added a list of updates that were required prior to installation (I would not need them during testing because my test area was always up to date prior to starting). I would list the required updates on the release notes, zip the registered update and the release notes together and post them on the company website for our client to install. The registered update would also be added to Netsmart's monthly and quarterly updates for customers. I would then close the ticket and assign it back to the original support representative to notify the client about the update. If the update did NOT fix the issue or if the update caused another issue, I would: Immediately document the result of the installed update. I would show the developer who made the update my findings. They would verify the update was not ready. I would send an e-mail to the group advising of the fail and to whom I was re-assigning the ticket. I would fail the update on the ticket and re-assign it to the developer who would then make other modifications. The process would start again until the update was complete, the issue fixed and passed through the proper workflow. On top of my normal workload: I instructed the interns and juniors about how to do ALL OF THE ABOVE. I wouldreceive all updates involving EDI. This would include billing, remittance, eligibility denials and any other EMR/EHR. I was sent to client sites to teach them how to use Avatar Electronic Data Interchange/Electronic Billing, Remittance, Eligibility, Denials and special reports. I spent weeks at client sites in Iowa, Pennsylvania, Upstate New York, Wyoming and West Virginia on special assignment. My first 5 years at Netsmart was assisting in its development. I would verify HIPAA compliance and I was the only QA engineer who knew how to create the electronic forms. I would work nights. I would work weekends. I would work holidays to keep the backlog to an absolute minimum. I was assigned to special projects for clients with special issues. I was assigned more than once to the Netsmart War Room. This was a room that contained the brightest and the best to handle a special needs client. Some clients needed customization added to the core product. Washington State was my special assignment. I had to keep a running copy of a single client completely up to date at all times to test the customization. New York State had special forms and billing requirements. It was my job to keep track of those as well.
Customer Service/IT Intern
January 1988 to August 2002Worldcom, Inc － City , STATEThe company started out as Nationwide Cellular; a small re-seller of cellular phones. It was purchased by MCI sometime in the 1990's. MCI was then purchased by Worldcom. I started in an inbound call center handling customer calls. I took payments by phone, resolved disputes, handled cancellations and handled retentions to prevent cancellations. I handled low level 30 day delinquency issues, sometimes being forced to suspend customer service. I handled collisions. (Back in the analog phone days, a phone could be "cloned" fraudulently. We would set the phone to call us no matter what number the user called to advise and correct this). I assisted customers with rate plans, offered incentives of new equipment to raise their plans and to assist in retention. I later took a position as an intern in the IT department. The company moved from UNIX based dumb terminals to Microsoft PC's with Windows 98. I assisted in "ghosting" the PCs in a one week project. I then was responsible for changing the retail outlet computers to the new PCs and instructed the sales staff on how to use them. I would perform troubleshooting, virus removal, BSODs and any other Windows 98 related issues. I was promoted to IT representative in 2000 and was assigned a mentor (Rudolph Paetz). I was responsible for server maintenance, shown the proper IT notations and documentation. I replaced workstations and peripheral equipment. I replaced wall outlets and replaced cabling. I installed and re-installed UNIX client software and connected it to the server.
January 1988 to August 2002Worldcom, Inc － City , STATEThe company started out as Nationwide Cellular; a small re-seller of cellular phones. It was purchased by MCI sometime in the 1990's. MCI was then purchased by Worldcom. I started in an inbound call center handling customer calls. I took payments by phone, resolved disputes, handled cancellations and handled retentions to prevent cancellations. I handled low level 30 day delinquency issues, sometimes being forced to suspend customer service. I handled collisions. (Back in the analog phone days, a phone could be "cloned" fraudulently. We would set the phone to call us no matter what number the user called to advise and correct this). I assisted customers with rate plans, offered incentives of new equipment to raise their plans and to assist in retention. I later took a position as an intern in the IT department. The company moved from UNIX based dumb terminals to Microsoft PC's with Windows 98. I assisted in "ghosting" the PCs in a one week project. I then was responsible for changing the retail outlet computers to the new PCs and instructed the sales staff on how to use them. I would perform troubleshooting, virus removal, BSODs and any other Windows 98 related issues. I was promoted to IT representative in 2000 and was assigned a mentor (Rudolph Paetz). I was responsible for server maintenance, shown the proper IT notations and documentation. I replaced workstations and peripheral equipment. I replaced wall outlets and replaced cabling. I installed and re-installed UNIX client software and connected it to the server.
72E Mobile Combat Encrypted Communications Specialist Grade
November 1981 to November 1987United States Army Reserve Signal Corps － City , STATEI was responsible for running a message center in combat conditions. I ran a Mobile message center with 4 subordinates. Sent and received encrypted classified flash traffic. I and my subordinates sentried a Classified message center. The mobile unit was also in charge of 2 10KW generators for power. I was responsible for the upkeep and maintenance of the generators. I was a fully trained serving line combat infantryman.
November 1981 to November 1987United States Army Reserve Signal Corps － City , STATEI was responsible for running a message center in combat conditions. I ran a Mobile message center with 4 subordinates. Sent and received encrypted classified flash traffic. I and my subordinates sentried a Classified message center. The mobile unit was also in charge of 2 10KW generators for power. I was responsible for the upkeep and maintenance of the generators. I was a fully trained serving line combat infantryman.
Education and Training
Associates : programming, cyber SecurityAmerican Military University CharlestownAssociates Program American Military University Charlestown, WV - 2015 to Present Major in programming. Network systems. Minor in cyber Security. Currently enrolled. Expected graduation date 2016. Pre-requisites. Life experience credit requirements. English 101. Certifications
Certification : Public Speaking and Human Relations, 2003Computer Career Center Garden City － City, State, USComputer Career Center Garden City, NY 2002 to 2003 CompTIA A+. CompTIA Network+. Microsoft Certified Professional. Computer hardware. Network hardware. Basic input/output Services (binary). Microsoft Windows Server 2000/2003. Active Directory. Microsoft Exchange 2000. DOS. Certification in Public Speaking and Human Relations
GED : 1983United States Army Signal School Fort Gordon － City, State, USUnited States Army Signal School Fort Gordon, GA - 1982 to 1983 High School (GED)
1983Hicksville High School HicksvilleHicksville High School Hicksville, NY - 1983
Certifications
HIPAA Network+ Microsoft Certified Professional Certification in Public Speaking and Human Relations
Skills
Documentation, Maintenance, Microsoft Windows, Analog, Cabling, Cellular, Customer Service, Ghosting, Mentor, Payments, Pcs, Receptionist, Retail, Retail Marketing, Retail Sales, Sales, Sales Staff, The Sales, Unix, Windows 98, Workstations, Associate, Automated Testing, Billing, Clients, Crystal Reports, Database, Edi, Ehr, Electronic Billing, Electronic Data Interchange, Electronic Health Records, Emr, Engineer, Hipaa, Its, Project Manager, Qa, Quality Assurance, Remittance, Test Plan, Testing, Vmware, Vpn, Workflow, Flash, Generators, Active Directory, Comptia, Dos, Exchange, Exchange 2000, Microsoft Exchange, Ansi, Application Testing, Application Testing/programming, Cache, Cases, Checkpoint, Cisco, Client Relations, Client/server, Crm, Customer Relationship Management, Disaster Recovery, Encryption, Functional Testing, Ghost, Html, Imaging, Life Cycle, Microsoft Office, Microwave, Ms Office, Network Security, Organizational Skills, Quick Test, Raid, Server Migration, Software Development, Software Development Life Cycle, Sql, Structured Software, Teaching, Terminal Services, Test Cases, Test Plans, Test Scripts, Time Management, Training, Typing, Windows 7, Writing Test, Writing Test Plans, Credit, Cyber Security, Security
DISCLAIMER
Resumes, and other information uploaded or provided by the user, are considered User Content governed by our Terms & Conditions. As such, it is not owned by us, and it is the user who retains ownership over such content.
How this resume score could be improved?
Many factors go into creating a strong resume. Here are a few tweaks that could improve the score of this resume:
Resume Strength
- Completeness
- Formatting
- Word choice
- Length
- Measurable results
- Strong summary
- Typos
Resume Overview
School Attended
- American Military University Charlestown
- Computer Career Center Garden City
- United States Army Signal School Fort Gordon
- Hicksville High School Hicksville
Job Titles Held:
- Senior Quality Assurance Engineer
- Customer Service/IT Intern
- 72E Mobile Combat Encrypted Communications Specialist Grade
Degrees
- Associates : programming, cyber Security
Certification : Public Speaking and Human Relations , 2003
GED : 1983
1983
Similar Resumes
