We provide IT Staff Augmentation Services!

Test Engineer Resume

4.00/5 (Submit Your Rating)

SUMMARY:

Highly skilled, dependable, savvy Quality Assurance Engineer with 10+ years of experience testing software, hardware, websites and mobile apps. Communicates well, good team member with a great attitude.

SKILL:

Software Development Life Cycle, Defect: tracking software programs, Test Case Management software, Comprehension of constantly changing environments and testing needs, Understanding the needs of end - users, Web page testing, Testing with multiple Internet browsers, Some XML and HTML, UNIX/Linux, Hardware testing (mobile devices, computers, DVRs, printers), Android Operating System and SDK

PROFESSIONAL EXPERIENCE:

Confidential

Test Engineer

Responsibilities:

  • Member of Upgrade Test Team
  • Inspecting data after Confidential upgrade

Confidential

Test Analyst

Responsibilities:

  • Working on Alexa Deals Team
  • Setting up deals for Alexa
  • Testing “Golden Utterances” on pre-release and Production
  • Creating keyword whitelists and blacklists using Amazon’s tools
  • Creating data cards for products using Amazon’s tools
  • Verifying deals start/end at the expected date & time
  • Revising deals before, during and after their expected start times

Confidential

QA Engineer

Responsibilities:

  • Testing Hangouts for Android
  • Worked with various Android devices and Android versions from ICS - Android O
  • Owned various features in the product - such as attachments, Peer to peer messaging, Android Wear & Android Auto among others. Generalist on the rest of the product
  • Used ADB and Confidential in-house tools for OS and application install
  • Wrote bugs and test cases for the product features
  • Did Accessibility testing for Hangouts as part of release testing

Confidential

QA Engineer

Responsibilities:

  • Creating Insurance Quotes for Corn & Soybeans using Web Browsers & Mobile application
  • Tested Android and iOS application for Growers
  • Tested Climate Basic and did CLU testing
  • Used Jira and Pivotal Tracker as bug - reporting websites
  • Used ADB to test Android issues and install the app being tested
  • Used XCode for iOS testing
  • Used iTunes to see user logs

Confidential, Seattle, WA

QA Engineer

Responsibilities:

  • Tester for Confidential, setup app for test, managed and created test reports using templates created in our Wiki
  • Tested Confidential website using multiple web browsers
  • Tested Confidential application
  • Managed test devices from various OEMs
  • Downloaded and updated ROM for mobile devices. Maintained a backlog of OEM ROMs for the team
  • Prepared devices for handoff to devs & other QAE
  • Managed inventory and device checkouts - Labeled each device with a scanable tag
  • Used ADB as a tool for testing devices and updating hardware
  • Used Jira for bug reporting
  • Used Testopia for test case management
  • Used Scrumworks for task management
  • Used VirtualBox for Virtual Machines

Confidential, Kirkland, WA

Software Test Engineer

Responsibilities:

  • Sole tester for the Portal Team, working closely with developers and marketing
  • Testing MOXI.com website
  • Tested Moxi iPhone application
  • Tested RMA Procedure Turn - Key solution
  • Did eCommerce and functionality testing
  • Testing web-based internal tools
  • Writing defects in Bugzilla
  • Test cases updated and written in DevTest (an in-house application)
  • Wrote Test Summaries as appropriate
  • Tested using multiple browsers/operating systems on PC & Macintosh
  • Focus is on quick turnaround in testing and validation
  • Suggested solutions to issues when appropriate
  • Also testing Confidential DVR solution when needed

Confidential, Redmond, WA

Senior Software Test Engineer

Responsibilities:

  • Tested MSN America homepage (Canadian English & French)
  • Wrote bug reports in Product Studio
  • Wrote Test Plan for future Venezuela & Peru testing project
  • Created bug tracking spreadsheet for release of Canada project
  • Did editorial fixes via Confidential ’s “Bedrock” file management system
  • Worked in Scrum-style development

Tested using browsers: IE7, IE6, IE8 (beta), Firefox 2.0 & 3.0.4 Safari, Opera, Netscape Navigator, Flock, Mosaic

Operating systems: Windows XP, Vista

Confidential, Kirkland, WA

QA Engineer

Responsibilities:

  • Tested Moxi all-in-one Digital Media Recorders:
  • Transport Control Bar - Live & Recorded TV
  • Channel Tuning
  • DVR - Recorded TV
  • SAP/Language
  • New Menu UI
  • Front Panel functionality
  • Usage Tracking
  • Photos
  • Flip Bar
  • Ticker
  • Remote
  • Assisted in Stability Lab testing check out by running automated scripts and observing results.
  • Acted as a generalist for the entire product and wrote bug reports across all areas as necessary.
  • Wrote clear and concise bug reports using Bugzilla.
  • Updated and wrote new test cases
  • Directly affected testing by pushing for more accurate specification documents.
  • Made use of UNIX-skills navigating through file system and installing releases.

Confidential, Seattle, WA

Quality Engineer

Responsibilities:

  • Tested FlipStart UMPC, specific features and associated software.
  • Tested FlipStart.com website for functionality and content
  • Tested FlipStart.com e - Commerce website for functionality and content
  • Tested peripheral, driver and supporting software for the FlipStart computer
  • Wrote clear, concise defect reports using Test Track Pro
  • Wrote brief test summaries at conclusion of test passes
  • Tested Service Pack 1 release of FlipStart software
  • Tested with a large number of browsers and messengers
  • Internet Explorer 6 & 7
  • Mozilla Firefox 1.5 & 2.0
  • Opera 9.2.1
  • Netscape Navigator, Browser 8.1
  • Apple Safari, Beta 3.0
  • Mosaic 3.0
  • Windows Live Messenger 8.1
  • AIM 6.0
  • Yahoo Messenger 8.1
  • Skype 3.1
  • Trillian 3.1

Confidential, Seattle, WA

Software Test Engineer

Responsibilities:

  • Tested Screen3 application. Confidential ’s application for mobile devices takes RSS feeds and turns them into channels on the wireless device.
  • Our job was to test the server, but using the client was part of validating server operation
  • Tested Screen3 Server AdminUI
  • Tested Screen3 Channel Feed Validation Tool. The Validation Tool verified that RSS feeds conformed to Screen3’s requirements and would display any problems encountered in the feed
  • Edited HTML, XML and XHTML to create test channels
  • Wrote test one-liners (test case ideas)
  • Wrote test cases - updated existing test cases where appropriate
  • Wrote clear and concise defect reports in Confidential ’s defect database
  • Worked with developers to drive defects to their termination, either getting them fixed or closing as won’t fix
  • Tested Screen3 Version 2 & 3 using the following tools:
  • UNIX
  • Toad
  • Putty

We'd love your feedback!