We provide IT Staff Augmentation Services!

Software Qa Test Engineer Resume

3.00/5 (Submit Your Rating)

CaliforniA

SUMMARY

  • Thinking tester experienced with analyzing complex cloud - based systems in highly dynamic world class teams - usually working on blue sky projects that require a risk, security, and a systems modeling focus.
  • I worked in one of the first analyst teams for Google Maps Local Business Data at Google (Mountain View, USA) and got a wonderful introduction to ongoing learning and love of tech
  • I love working with a team that finds value in my experience and appreciates love for learning and adapting in new technologies.

AREAS OF EXPERTISE

  • Systems & Analytical Thinking
  • Domain Testing, Claim Testing, User Testing
  • Risk Testing, Flow Testing, Defining workflows
  • Security Testing, Penetration Testing
  • Load Testing (Minimal)
  • Product Specialist
  • Exploratory, Black & White Testing
  • Functional and Nonfunctional Testing
  • Root Cause Analysis
  • API Testing
  • Automation Testing (Basic/Editing Script etc.)
  • Test strategy & planning

TECHNICAL SKILLS

  • JIRA, SOAPUI NG, RESTful APIs, PostMan, ZAP, OWASP 10, Basic Python Scripting, Command Line Interfaces, PyCharm, SourceTree, Robot Framework, Selenium WebDriver, Selenium2Library, ChromeDriver, Browser Developer Tools, Apiary, Atlassian's Confluence, ngrok (webhooks).

PROFESSIONAL EXPERIENCE

Software QA Test Engineer

Confidential

Responsibilities:

  • Gaining an in-depth knowledge of a large complex system that was constantly changing hence little time to document those changes.
  • Understanding its complex flows. The impact of the integration of multiple APIs (about 50 APIs, half of which had a lot of parameter combinations) and needed to work cohesively together without conflict.
  • The look and feel (UI/UX) was critical for the user journey/experience.
  • We dealt with masses of data (more than we knew what to do with) as the collection and processing of data was critical for User Analytics, App Logging, Error Logging, and API Logs.
  • The Mobile app and Middleware development teams were dependent on our product being stable, they were under pressure from external clients and put that pressure on us to deliver for them.

Test Approaches & Techniques: Exploratory Testing, with a focus on the logic and structure of our code to simulate performance and quality validation for new releases. My day to day tasks involved bug reporting, resolution, UI testing, and HTTP REST API endpoint testing. I also created test cases for the development of test automation using the Robot Framework + Request Libraries for API testing. For UI testing I used the Robot Framework + Selenium2Librarv. Furthermore, I explored security testing with OWASP 10, ZAP, SOAPUI NG, as well as Detectify. I also worked with Continuous Integration; i.e. edited Python scripts when required and triggered automation scripts on-demand.

Tools & Languages : Basic Python Scripting, review pull requests on GitHub, JIRA, PostMan, SourceTree, Robot Framework, PyCharm, Apiary (API Documentation), OWASP 10, ZAP, SOAPUI NG (API security testing), Detectify (security scan for mobile applications).

Quality Analyst

Confidential, California

Responsibilities:

  • I evaluated web references and queries against Google's infancy-stage Knowledge Graph repository with the goal of matching user specified criteria to correctly reconcile Geo features and points of interest. Correct matching had direct impact on Local Data, Street View, Imagery, Base Maps and Search results. I reported instances of data errors and collaborated with internal teams to improve our Maps data sourcing and Google Search quality. I also resolved bugs dealing with data reconciliation and validated reports for engineering's action.
  • Debugging local databases in a sandbox environment to identify root cause.
  • Implemented positive changes to better match queries with temporary data while providing more clean and consistent results.
  • Separating "data issues" from bugs which can cause regressions. Identify engineering opportunities to add unit tests. "Data issues" equals that which causes Google indexers to fail or provide different results from what is expected by a user.
  • My knowledge working with Google Maps expanded over time hence I worked with different teams across Google whose interest dealt with Maps issues specifically. These could be localization, engineering, product management, country specialists, indexing, search, matching, business analysts, ads, account managers, and high profile internal escalations.

Tools & Technology: Google's internal software and in-house extensions were proprietary and not industry available. However; the testing approaches followed risk-based analysis.

Quality Analyst

Confidential, California

Responsibilities:

  • I provided Triage and Engineering instances where we could improve product loopholes by beta testing and improving internal tools used for debugging Maps, Local, and data analysis. I identified critical engineering bugs to prioritize. I used debugging via JavaScript consoles, scripts, and in-house extensions (tools/plug-ins).
  • The product I worked on was Google My Business, but the initial focus was testing the Local Data Layer. I f ocused on data analysis by debugging how errors sourcing Google Maps occurred and modified incorrect user or 3rd party directory generated content. I also debugged Places (business) listings to diagnose bugs to help improve sourcing of Google Maps and Google Places.
  • I was part of a brand new team of 7 analysts working on a completely new area. We took total ownership of how we would work and test the product; e.g. decided the work flows, prioritization, defined our resources, access and who we needed to work with and what we needed to learn.

IT Resident

Confidential, South San Francisco, California

Responsibilities:

  • I worked on scheduling software updates to 10,000+ employees to increase security for log-ins ensuring critical tools and processes were up to date.
  • I performed hands-on demos and troubleshooting for Apple's software and latest hardware. My proximity to the headquarters meant I also participated on company launches & expos, and helped try out new roles which influenced and created Apple positions worldwide.

We'd love your feedback!