Daniel Tovar Email & Phone Number

Cupertino, California, United States

Los Altos, Ca

- Part of a highly skilled QA team with purview of the entire Afero IoT platform including hardware, firmware, services, and apps. - Focused on testing firmware which runs on a variety of microcontroller platforms with differing feature sets and communicates via BLE and WiFi. - Lead testing efforts on WiFi connectivity, OTA firmware updates, and customer designed ‘profiles’ that were loaded onto Afero hardware.- Created and maintained test suites for all elements of the Afero platform.- Built and managed a library of mobile devices for BLE compatibility testing across mobile OSes and chipsets. - Lead tester of an OSX & Windows based WYSIWYG editor that allowed partners to both create the UI that would appear in app for their IoT device and define a ‘profile’ that would configure the Afero hardware to their specifications. - Tested multiple internal and external web services, including those that allowed partners to see reporting on customer devices. - Developed a hardware based test harness that was used to stress test Afero’s service.- Led numerous cross functional scrum meetings.

Cupertino, Ca

Seagate acquired Lyve Minds in August 2015 and my roles were the same as before.

Cupertino, Ca

- Part of the hardware/firmware QA team focused on an Android based personal backup solution with a hard drive and integral touch screen.- Created and maintained multiple test suites for the hardware/firmware side of the platform, this included the Android app that ran the Lyve Home user interface and service connectivity. - Due to my extensive experience testing HW/FW/Apps/Services/Etc. I was chosen to be a conduit between the hardware/firmware and services/apps QA teams. I relayed relevant info between the teams and suggested areas of focus for testing. - Helped define the supported image and movie formats on the Lyve platform, also created and maintained a library of test content to validate that support. - Was responsible for building a test library of SD cards and USB flash & disk drives, and creating a test suite for compatibility testing with the Lyve Home which had the capability to ingest content directly over USB.- Ran the ‘dogfood’ process and was responsible for collecting feedback from internal users of the product and ensuring bugs were filed and issues got in front of the right people.- As part of the larger QA team I was heavily involved in testing Lyve’s photo & video backup app on iOS, Android, OSX, and Windows along with testing Lyve’s cloud services.

Saratoga, Ca

- Was on the Channels QA team and was tasked with testing all applications that were published through the on-device store which are referred to by Roku as ‘channels’.- Created and maintained a certification checklist for third party developers to self-certify their channels before submission to Roku. I also was responsible for Roku’s internal channel related test cases. - Led testing efforts on hundreds of new channels and numerous updates to channels across four Roku platforms. Roku’s channel store was a fairly open platform where the channel submissions varied in scope and importance from local churches & news channels to heavy hitters like Netflix, Amazon, and Hulu.- For lower priority channels I was responsible for running a quick test pass to verify nothing violated the content or technical guidelines Roku partner developers had to follow.- In the case of more prominent partners I worked directly with their engineering teams to get their channels certified on the platform. This often involved changes to Roku’s OS for support which required coordinating the testing of these changes with the main Roku QA team.- I was responsible for publishing these channels to Roku’s channel store once they passed testing. This sometimes required coordinating publishing of the channel with service rolls on the partner’s side.- Responsible for testing and publishing Roku’s ‘Spotlight’ channel, which was a highly prominent channel on Roku’s main UI that was updated weekly to promote different channels.

Palo Alto, Ca

Danger was acquired by Microsoft in April 2008. Along with my previous responsibilities my role expanded to include:- Responsible for testing patches and workarounds on Java OS and Unix based services for customer data recovery efforts.- Created a test plan and led testing for an internal Windows Phone 7 application used by Danger’s Operations team.- Member of an Engineering team that recovered 98% of customer data after an infamous global database failure on the Danger Service.

Palo Alto, Ca

- Tested hundreds of third party apps and games to ensure they were free of bugs and conformed to Danger’s certification criteria. That included testing the behavior of the apps in relation to Danger’s database and server proxies.- Was lead tester on highly important apps for the platform such as Twitter & Facebook clients.- Helped to train and get up to speed a team of 30+ testers in India who over time handled the bulk of app testing. Worked day to day with this team by reviewing bugs, answering questions about odd use cases and directing efforts on complex apps.- Responsible for compiling detailed bug reports that were sent to developers and handled any questions developers had about my bugs.- Managed an internal wiki for the entire QA team, was responsible for keeping documentation up to date.- Created and maintained third party developer documentation such as certification checklists, network usage guidelines, and known issues lists for each new version of the Danger OS.- Responsible for creating and maintaining most of the test cases used for third party application and game testing, around 500 test cases covering 6 handsets in all. Listened to developer feedback and adjusted the test cases accordingly.- Responsible for verifying all apps and games were deployed correctly on Danger’s production marketplace before being launched. This included checking that all metadata (screenshots, descriptions, pricing, etc.) showed up correctly on the devices and that the DRM had been properly applied to each piece of content. At peak this involved weekly verification on 5 different operator marketplaces across multiple handset types.- As part of the larger QA team I filed bugs on and tested Danger’s core Java OS and Unix service releases, both during development and during regression phases where the whole team was needed to regress thousands of bugs.