• Lead a QA team by implementing QA process, answering team member questions, informing team of tool or process changes, setting up meetings, and assigning tasks

• Work with Scrum Master and Development Leads to ensure Sprint goals are met, status reports are up to date, and that the teams are working together effectively

• Write test cases and execute both functional and regression tests in Zephyr for an Insurance application, and report issues to development or business

• Write and run Java based automated tests in GitLab and IntelliJ, and troubleshoot any errors

• Became an automation lead and helped onboard team members into the automation script writing initiative and enforce best practices

• Identify tickets for test automation candidates and analyze functionality changes that affect the automation framework

• Communicate with SmartBear/Zephyr representatives to report issues and recommend functional enhancements

• Migrated test site passwords into 1password, and provided team with directions on how to use the new tool

• Participated in an AWS Jam and received AWS Training Certificate of Completion

• Worked on high-visibility software projects, verified both front-end and back-end applications, and executed UI, functional, integration, and regression testing

• Wrote transparent test plans by mapping use cases to requirement/design documents and documenting test cases in Test Rail

• Verified mobile app functionality on Android and iOS test devices

• Tested new API’s and API changes using Postman and Swagger

• Deployed test applications using Google Kubernetes clusters and Git commands

• Troubleshot and identified cause of production issues by analyzing logs and session data

• Identified issues in developer’s code and provided input on implementation changes in GitHub

• Collaborated with quality engineering to identify functionality and use cases for Selenium test automation

• Logged bug tickets in Shortcut and worked with Product Managers to prioritize

• Created and updated test data in SQL database to aid in testing

• Tested multiple e-commerce website applications that required knowledge of ADA compliance, customer service tools, payment gateways, Google Tag Manager, and marketing platforms

• Executed UI, functional, integration, compatibility, and regression testing based on the scope

• Served as both QA and Project Manager for multiple INFOR-based WPF applications that were used by internal Customer Service department

• Designed the first functional specification document template for internal team use

• Worked with offshore team to begin first test automation project with Eclipse

• Utilized SQL queries and F12 Developer Tools to aid in testing

• Reported bugs and tracked projects using JIRA and BugHerd

• Worked with developers on both front-end and back-end teams to help identify and resolve issues by reviewing code as well as database content

• Gathered business requirements and use cases for multiple new software development projects and wrote the associated functional specification documents

• Organized meetings and presented progress and new functionalities to stakeholders

• Served as a Scrum Master of the test team; held the daily standup, sprint planning, sprint retrospective, and additionally represented the team in the scrum of scrums

• Received MVP award of SQA group in February of 2016

• Entered defects into Jira and VersionOne, wrote and run test cases using TestRail, and created/updated documents in Confluence

• Analyzed log files and event viewer to help troubleshoot issues

• Utilized emulators to simulate real world environments, and provided feedback for their improvement

• Gained knowledge of Windows Services, IIS Manager for web-based applications, and SQL Server Management Studio for database management

• Provided demos to the software group to present new functionality

• Presented test plans to Product Owners and managers

• Worked with Project Management to understand the customer’s expectations and acceptance criteria, as well as to help provide estimates on when testing could be complete