At Philips Oral Healthcare I was responsible for ensuring the health and safety of our customers by verifying the quality of the firmware on multiple Sonicare Brush Handle releases. I worked directly with the Embedded Firmware Engineering team to capture requirements and create test plans and test procedures to verify that each of those requirements was being met. I was also responsible for managing a small team of outsourced testers located in Portugal. I oversaw scheduling and assigning work for the team as well as answering any questions they had and reviewing all their work. As a team we used Azure DevOps TFS for bug tracking and sprint planning, IBM Rational DOOORS for Requirements and Test Procedure management, and Windchill for Software BOM tracking.

: As the Test Engineering Manager for a product development company of over 150 people, my team and I were responsible for all firmware, software, mobile, reliability, and environmental testing of multiple hardware projects across the entire company. While at Synapse I moved from contract tester, to full time lead, to running the test team. My time leading the department was split between hiring, managing, and training a small team of test engineers with mixed experience levels. I was also responsible for estimating work for sales opportunities, managing the bug database, creating templates for test cases and plans, overseeing internal test projects, while also being directly responsible for testing client projects. As part of my testing of battery powered IoT devices I created a method of estimating battery life based on up to date current measurements, state diagrams, and client use cases.

As a Software Test Engineer on the Disney Technology Solutions and Services team I worked on an agile team creating test cases and plans based on wireframes and system requirements. These plans would then be used by the developers to build the application which I would then test. I used Fiddler and the Chrome developer tools to verify the content management system used by much of Disney and its affiliates. Bugs were tracked in Jira, which we also used for our sprint planning. Test cases and plans where all stored in Confluence and I was responsible for building and keeping my project pages up to date.

As the SQA Lead for the Nike Fuelband I worked closely with Electrical Engineering, Mechanical Engineering, and the Software Engineering teams to create test cases based on Nike’s requirements. I was responsible for testing the firmware on multiple Nike products. I created tests to verify power usage on multiple devices using a lab power supply, a mulitmeter, and LabView . I managed a small team of contract testers both on site and remotely. I met regularly with the client and my direct counterpart at Nike to discuss status and ongoing work. I also fought hard for a true SCRUM process, and stepped in to act as a SCRUM master for a separate team when I was needed.

As the sole member of QA in a small telematics start up I handled the testing of our 4 different product lines. I created load tests for our web portal using Selenium and Browsermob which revealed serious issues. I created and ran test cases and test plans for our driver application, in-display application, and 2 separate web applications. I also managed bugzilla, and created separate groups to allow us to provide outside partners access to a limited selection of the bug database. I interviewed applicants for permanent positions as well as participating directly in the selection of third party development teams based on their responses to our RFQ.

DUTIES: As QA Tester working in an agile environment I created test plans and test cases for web and mobile projects. I created automated tests using Selenium, and was responsible for doing my own builds using NetBeans, Maven and Tomcat. I verified the site functionality across multiple browsers including Internet Explorer, Firefox, and Chrome. I worked directly with a third party developer to insure the quality and functionality of our mobile app on both the iPhone and Android operating systems.

DUTIES: As a Senior QA Engineer working on a short term contract for a multi-million dollar web site I created a test plan along with functional and use cases for a quick release project. I was able to assure a high level of software quality, in a project that experienced ever increasing scope creep and changing release dates. Working directly with the dev team and an SDET, I created a strategy that enabled us to maintain a high level of confidence in a rushed release of previously untested code. I verified the site functionality across multiple browsers including Internet Explorer 7, 8, 9; Firefox 3 and 4; Chrome 10; and Safari.

DUTIES: As a Field Test Engineer working on the Whispernet team I was responsible for testing the Kindle’s network performance around the world on both 2G and 3G networks using GSM, CDMA, WCDMA, EDGE, GPRS, and HSDPA technologies. Working directly with Sprint, AT&T, Vodafone, and their respective roaming partners, I helped track down connection and performance issues in the field. While at Amazon.com I worked on multiple revisions of the Kindle using changing cellular modems and technology. When I was not in the field I acted as a support technician in charge of trouble shooting customer reported network issues.

DUTIES: As a Test Engineer working on the WhitePages re-brand team I wrote test cases based on an ever changing specification document. Working in an agile environment I tested the look and feel of the newly re-branded web site in Internet Explorer 6, 7 and Firefox. I assisted in pushing the latest builds to the QA servers. I aided in running full site regression passes.

DUTIES: As a Senior Test Engineer on the Seattle Regional Fare Payment project I maintained the Windows and Linux based hardware in the Regional Test Bed, provided support for five separate transit agency’s test teams, as well as technical support for on site problems related to our hardware and software. I was responsible for running Perl scripts through a Cygwin shell to install and update all devices in the test lab including handheld Psions, as well as installing and commissioning Dell servers and desktops in the field. In between those duties I ran regression and functional testing of the software and hardware in the test lab.

DUTIES: As the only Quality Assurance Engineer on the project, I was fully responsible for the complete testing of a major beer company’s web site. Working with a small group of developers and business analysts in an agile environment we were able to use DotNetNuke to build a 53 page web site including content management system, flash beer carousel, data driven tables, search functionality and feedback forms. In a four week period I wrote and executed over 1300 test cases on Internet Explorer 6, 7, and 8, as well as Firefox, Safari, and Opera. The project was date driven in order to match the official announcement of the company’s merger. Working many long days and weekends we were able to deliverer the project on time and with all the features the client had requested.

DUTIES: As the Software Test Lead at a small web application development studio it was my job to oversee the manual and automated testing of multiple .net projects in an agile environment. As the most experienced member of the QA team I was also given responsibility for resource management, mentorship, weekly one on ones with junior members of the QA department, interviewing potential hires, and attending management meetings, as well as establishing QA processes and methodologies. While I was the QA Lead the company adopted the Scrum model for a majority of our projects. It was my job to fit Blackbox testing into what was designed as a predominantly Development centric process. In this capacity I also was responsible for creating training for the QA department on the use of Target Process which the company had purchased for project management, bug tracking, and test case management. Of course being a small company it was also my job to be directly responsible for the testing of multiple projects from start to finish.

DUTIES: As a Software Test Engineer and Test Lead at Qualifacts my job involved the creation and assigning of test cases and test matrices, for the manual testing of .Net based medical billing/scheduling/tracking software. I was responsible for assigning other testers their daily tasks as well as for planning the overall test strategy for the product. I was in charge of cross communication with the development team, and making sure that all bugs where being dealt with in a timely and correct manner. I used Segue’s SilkCentral Testmanager to create and run test passes. My main job was to test the functionality, UI, and data manipulation of over twelve hundred different screens within the product.

DUTIES: During my time as an STE 2 with Studio RX, I wrote over 100,000 test cases based on ever changing design documentation for Fable, ran milestone acceptance tests, and ran both directed ad-hoc and my own test cases. As an STE 2 my duties included the filing and tracking of bugs, the upkeep of test cases in my areas, and the review of all design documentation related to Fable. I also provided additional testing for other projects, including Voodoo Vince, and Impossible Creatures. Then as an STE 2 on the eLearning localization test team I worked with an out-sourced overseas test team to ensure the quality of Flash based training software. As a localization tester I used Virtual PC to run build verification, CD gold checks, test the engine, setup, content, and compatibility over all versions of Win9x and Win2K in multiple languages and with various versions of Internet Explorer. I was directly responsible for all titles in my languages, and worked closely with the project manager to insure the highest quality of software possible within the given schedule.

DUTIES: As a full time tester at the Zone.com my responsibilities included the writing of test strategies, test cases, exit criteria. My duties included the verification of web based games and web integration of game clients, as well as testing web infrastructure, and new initiatives. I was directly responsible for multiple projects over the full product cycle. I attended code, and spec review meetings. I was responsible for creating test plans and milestone criteria for my products and for setting up review meetings with dev. and pm. I was in charge of all bugs in my projects and worked directly with pm and dev. to produce schedules.

DUTIES: As the engineering QA lead, I built a small but effective test team using inexperienced testers and very limited resources. When I arrived QA was mostly an after thought with bugs being tracked in e-mail, no test cases, no plans, and only ad hoc testing being performed. Within months my team and I had built up test plans, cases, hardware and content test sweeps, build verification tests, performance and stress tests, instituted proper bug writing and tracking, and generally took a rag tag department and whipped it into a solid testing machine. My duties included but were not limited to, writing test plans, writing and reviewing test cases, overseeing all testing related to WildTangent's core technology, preparing bug reports and testing status reports, attending bug triage and tactical meetings, holding one-on-one meetings with my reports, and molding a group of green horns into monster testers.

DUTIES: Coordinate the certification process between Ravisent, major OEMs (i.e. Dell, Compaq, Gateway...) and Microsoft's Windows Hardware Quality Labs (WHQL) in respect to Motion Video. Make sure the engineering team understands and is following current WHQL SDK requirements. Write and execute test plans based on WHQL test kit and known bugs. Complete submission paperwork for all systems going to WHQL. Work directly with WHQL test engineers to solve any possible problems during testing. Find and write bugs. Update and track bug database. Act as a liaison between Ravisent and Microsoft. Plan and test both hardware and software DVD solutions on Windows 95, 98, 2000, and NT 4. Troubleshoot and repair any problematic systems before they get to Microsoft.

DUTIES: Working with the Windows Driver Model team, my job was to plan and test all elements of running DVD on both Windows 98 & NT 5. Find, report, and track bugs using Raid 3.1. Install and troubleshoot various DVD decoder and video cards on multiple systems. Run regression testing on beta builds and private drivers. Work directly with programmers and hardware representatives.