WORK EXPERIENCE:

Confidential

Senior Quality Engineer

Responsibilities:

• Working closely with Android Based Locked Software variant of the Confidential device from Nuu, testing and developing stability.
• Working on the Focus Test Group in the test team to do feature focused based testing on the software for defects as the features are being developed ahead of the main QA Team.
• Creating Test Tools from Batch and Python scripts for team use.
• Using TestTrack to enter defects and test cases for Confidential approval.
• Using Jira / Confluence / Bitbucket / SourceTree Atlassian tools for various tasks.
• Android Studio / Android Tools for tracking and testing basic automation code from the Automation team.

Confidential

Senior Quality Engineer

Responsibilities:

• Work closely with Engineers on the in - house Software Development Kit for Confidential and Set Top Boxes, as well as, various Platform SDK kits.
• Work on both the embedded Firmware and software on the devices for all set tops and Streamer solutions.
• Test compatibility for the VMS1100 (Verizon Media Server) now on the Market, Retrieving builds from the SVN servers.
• Test compatibility of the Mobility features on platforms such as, Android smart phones, Android Tablets, iOS/iPhone and iPads, Mac, Linux and Windows 7/8/10 on an in house proprietary application.
• Test all functionality and system requirements for the SDK framework alongside with the in-house security IPRM.
• Create and modify ALL test plans/setup documentation and procedures for all platforms.
• Create new test standards for upcoming projects with the newest methods of testing.
• Do a variety of testing based on needs from, Full cycle, Smoke Cycle, Sanity cycle, Regression Cycle of testing with custom reporting system based on team requirements for release.
• Testing Verizon based cloud service API’s with AWS performance tests pre-built by Verizon for use.

Systems Test Engineer

Responsibilities:

• Tested Android based devices in the process of launching.
• Responsible for multiple tasks that varied between the platforms tested. This included, system level testing, feature testing of all options on the devices, as well as, testing of first party applications.
• Tested various build sanities for upcoming releases in the software.
• Bug tracking and regression done on various levels using JIRA from build to application issues.
• Worked closely with developers and reporters to resolve issues and verify whether they still appeared on new releases.

Confidential

Test Technician / Stability QA Engineer

Responsibilities:

• Part of the Android Platform Test team / tested Confidential ’s first party chipsets for mobile devices.
• Primarily worked on the stability lab, flashing, executing and testing all mobile targets setup for the android platform through automation. Used Perl scripts with base Confidential and Confidential backgrounds enabled in the scripts.
• Maintained and managed the stability lab’s entire inventory of test equipment, including all the devices incoming and outgoing from other Android Platform Teams.
• Completed daily reports and filed CR’s and issues seen during long iteration tests.
• In charge of all the APT teams special requests such as ordering test equipment for repair or modifications through various in house repair groups.

Related Programs Used: QXDM, QPST, Perforce, CRMDB (Internal CR Database) Microsoft Word, Outlook, Messenger, Lauderbach Trace32, Notepad++, Confidential, Confidential, Logcat.

Confidential

Test Engineer

Responsibilities:

• Test engineer for Mercury Project, testing various pre-release handsets from various carriers and different platforms.
• Focused on the Bluetooth Environment and tested various Bluetooth profiles for both handset and PC.
• Collaborated with manufacturers in order to complete the Pre-CTIA and Pre-NAC test plans and requirements, making sure that all devices under test meet these requirements.

Confidential

Quality Assurance Systems Test Engineer

Responsibilities:

• Tested various JAVA and Confidential related mobile devices for Sprint and Verizon Wireless within their Test Central manual testing application and the newly implemented SLATE Automated testing suite.
• Wrote and issued Change Requests and issued bugs within the SLATE system through implementation.
• Reported and logged issues with the handset during testing using various testing software such as QXDM, QPST and RSD Tool/RSD Lite.
• Worked closely with phone leads to setup network (Spirent/Agilent Boxes) systems for specific network tests.
• As a side project, worked on the testing of the RSD Tool for Verizon, testing new Confidential handsets DLL and checking for compatibility with other Confidential handsets and features.
• Developed new test plans for smaller programs such as RSD tool and modifying older plans in test.

Confidential

QA Test Engineer

Responsibilities:

• Ensured that all mobile software applications utilizing Confidential ’s Binary Runtime Environment for Wireless ( Confidential ®) platform, received extensive and fair analysis.
• At the same time performed complete quality assurance testing and troubleshooting for the Music on Demand and Video on Demand suites for Verizon Wireless and made sure it met or exceeded the requirements set by Verizon.
• Updated OEM software upgrades and application specific updates through QPST and first party tools set by the handset manufacturers.
• Completed extensive test plans throughout each application and data reporting through JIRA.

Confidential

QA Test Engineer

Responsibilities:

• Ensured that all mobile software applications utilizing Confidential ’s Binary Runtime Environment for Wireless ( Confidential ®) platform, receive extensive and fair analysis while performing the Confidential certification process and quality assurance.
• In order to validate the applications Confidential status, determined if the software appropriately adhered to Confidential standards by reviewing and cross-referencing the applications specification documentation and evaluating the application itself. Found any current bugs and reported them.
• Worked in a fast-paced and constantly evolving environment and kept immaculate records of any errors or issues pertaining to the application and/or handset being considered for certification.
• Among the details to be inspected where the GUI’s functionality, handset interaction, data call handling, audio/visual characteristics, file system properties and overall application stability.

Confidential

Test Engineer

Responsibilities:

• Ensured that all mobile software applications utilizing Confidential ’s Binary Runtime Environment for Wireless platform, receive extensive and fair analysis while performing the Confidential certification process.
• In order to validate the applications Confidential status, determined if the software appropriately adhered to Confidential standards by reviewing and cross-referencing the applications specification documentation while evaluating the application itself.
• Maintaining a positive attitude and high productivity level while exposed to a fast-paced and constantly evolving environment enabled me to keep immaculate records of any errors or issues pertaining to the application and/or handset being considered for certification.
• Among the details to be inspected included, the GUI’s functionality, handset interaction, data call handling, audio/visual characteristics, file system properties and overall application stability.

Confidential

Game Test Analyst QA

Responsibilities:

• Tested such titles as, Confidential: Confidential, Confidential II and Confidential: Confidential games on the Confidential and PC platforms in the Quality Assurance Department.
• Wrote bugs/issues (problems in the game) along with daily reports and data entry on the Confidential bug database. Completed daily and weekly status reports to track the overall completion of the title during the testing process.

Confidential

Game Test Analyst QA

Responsibilities: T

• Tested various Confidential titles that were in production. Such titles include, MLB 2005 and ATV Offroad Fury 3. Analyzed and wrote up reports and “bugs” inside the game.
• Member of the Confidential ( Confidential ) Team and Online/Multiplayer department testing a very detailed test plan to make sure that the game was up to the Confidential requirements on all levels.