Implementing automated test coverage using various tools, mainly: AWS, Postman, Jmeter, k6, REST, Docker, etc... Implementing E2E frameworks using Java, Spring, Python, JS/TS with Playwright, Cypress, WebdriverIO, Selenium, Appium. Integrating with Rally, Jira, TestRail. CI/CD Github, Gitlab, AWS.Testing apps on virtual and physical devices using tools like Vysor, Appium, Detox, Espresso, XCUnit, Kotlin, Charles, Intellij Idea, XCode.

Primarily testing mobile apps on emulators and real devices. Building automated support for regressions and UI testing using WebdriverIO framework, Appium, Android and iOS tools. Using the usual tools for this type of testing and tracking - Charles, Postman, Testrail, Jira/Confluence.

Playwright, Node, React, NextJS, Jest, Github, AWS, GraphQL, Postgres, Python (Locust), Atlassian tools. Testing React, GraphQL, Postgres apps to support real estate agents.

Blackhawk Network aquired Cashstar in 2017. Selenium + Python, BrowserStack, AWS, and Jenkins for E2E and UI test development and implementation. WebdriverIO, NodeJS, Typescript for api and smaller E2E tests for internal projects. Several roles during tenure including testing and automating tests for consumer sites, Architecture system QA, Commercial Risk QA and Scrum Master, middleware QA. Testing Django/React consumer sites and supporting ecommerce systems.

I supported the Classic platform for a year before switching over to cover support on the newer fleet tools. Classic was a Coldfusion application that provided a front end view to client data. It was almost 15 years old when i inherited it. In addition to supporting front end changes, there was often a great deal of work in the Oracle database packages and script maintenance on the servers. I made enhancements and built out some new functionality over two release cycles before changing projects. I was charged with implementing the analytics code on classic as part of a cross team effort to improve our coverage.Working on the Distributor/NP projects put me in closer contact with customer support on a day to day basis. On this platform troubleshooting was on a much larger scale as our customers were fuel companies, not small fleet customers. The development work on this project was handled by a dev team, so most of the code i wrote or removed was related to bugs in behavior for specific brand edits.We were on call for support for a set of applications as the first triage. We often had to work with customer reps to troubleshoot customer issues regarding billing and data reporting. In addition to regular duties I was involved in facilitating application support needs as we built out a new remote datacenter. In addition to testing I was the point person for triaging support issues in my team area for this project.