Karen Cornelio Email & Phone Number

Seattle, Washington, United States

Greater Seattle Area

Hired to elevate quality practices, with the primary objective to provide clarity to the organization on quality metrics. Completed work as sole QA engineer on greenfield project that launched successfully and delivered every 2-4 weeks. Inserted myself in Pull Request process to catch bugs before code was merged out of feature/fix branches – reducing bugs in develop branch by 99% and affording a confident, rapid, painless production deployment.Explored frameworks & strategy for QA on brand new mobile app. Also have experience testing on OTT teams as needed.

Greater Seattle Area

One of the things I most enjoyed in this role is that due to the extremely complex architecture, my time with the company, and my own determination, I was able to completely grasp the many data pipelines, and help others in all departments. I truly loved being a manager of talented people, helping them grow their careers and solve daily challenges, and I also loved that I was able to always remain a key individual contributor. For my last 6 months at the company, I was solely responsible for all QA on all core products through several releases. I was able to handle this workload by fully taking advantage of existing/abandoned automation, fixing it up for a CD type of development environment, and bringing the test automation to a level of quality and confidence for all stakeholders.Working at ProQuest gave me many opportunities to support and collaborate with a vast amount of groups including offsite teams, stakeholders in other business units, and stakeholders in completely different companies.Some projects that are noteworthy include full-picture QA on database migrations/upgrades, after full production outages, and on infrastructure updates (such as network switches, data center move, etc). Additionally, I was on 2 large greenfield projects that made it into production and are still in use today.

As a contractor, I performed web UI blackbox and whitebox testing in an agile environment.

This was an exciting opportunity for me as the company was still quite small, but already successful. I was hired to establish a QA process where none existed, which included hiring, tool selection, process development, and test strategy.I entered at a time when the dev team was refactoring existing code and automating some functionality that was manual behind the scenes. The company offers luxury handbags for rent, so the inventory was constantly changing depending on what was out on rental, and the website needed to reflect that. Another interesting aspect was managing the vast amounts of images. We met an aggressive twice-weekly release schedule. I recognized the need for the developers to be focused 100% on development (better quality code!) so I took on the release work, resolving merge conflicts, building, and deploying .As things began to gel, I hired an additional QA Engineer, and managed him. I shifted focus a bit more to administering development, test, and staging environments, and generating metrics to communicate project quality and test coverage. I also continued to write and perform tests, both manual and automated.

As a contractor, this mid-level position involved testing a highly scalable, multi-tiered web application. Tests were mainly manual due to the nature of the product, but some automation was created where possible.My responsibilities included development of test plans and test cases, unit testing, integration and end-to-end testing, stress & performance testing, defect tracking and development of software for automated testing.

As a contractor, I provided manual QA for Rhapsody Client embedded on various personal music devices.

My time here was a significant period of growth and development over which I progressed in my career. In the time when there were so few training opportunities, I was able to use my own resources and skills that ultimately led me to QA Team Lead.I then moved into the Build Engineering team and handled Configuration Management, Version Control, Engineering Services, selecting a new bug tracking system, and developed (scripted) a system for delivering automatic metrics.I advanced to an Engineer (development) role, where I developed portions of a web app in ASP.After being trained in Java, I moved back into the QA group as an SDET for an API. Our small team wrote our own test framework, as well as the tests themselves, all in Java.

I coded various front ends and demos, optimized for viewing in a PDA (personal digital assistant), using lots of XML, XSLT, and XPath.