Joash Mungray

Experience

• 

  Derivco

  Mar 2014 - now

  Key achievements:Technical:- Developed a framework which achieves 100% automated testing using CI/CD pipelines for a B2B API which averages 350m+ monthly hits. - Developed 100% automated testing for a B2B integration layer for 30+ regulated markets which runs in a CI/CD pipeline and supports 50+ different businesses with varying use cases. - Implemented tests using Cypress, Selenium and Nightwatch in Azure Devops and GitHub build and release pipelines ensuring comprehensive test coverage on every release. - Built a test environment CI/CD pipeline to provision and set up test environments - 24 hours saved per run. - Built test automation solutions for Android apps, iOS apps and mobile web apps. - Saved 90 hours per test cycle using Appium based solution on the Android operating systemManagement:- Managed a team of 40 contractors to accelerate delivery by migrating 60 products off a legacy framework within 10 months. - Conducted 20+ technical interviews for QA and automation based roles - Provided technical and behavioral guidance to a handful of candidates which enabled them to get promoted Show less This was a double promotion obtained at Derivco, I specialize in mobile software testing across Android (Android - Java) iOS (Swift) and Windows mobile (Windows 8, 8.1 and 10) native hybrid applications, with higher focus on Android Native testing and black-box software test automation. As a Lead Quality Analyst (LQA) there are small, yet significant, differences between the QA and LQA roles. The LQA is more experienced, has a strong technical testing background and higher product domain knowledge than a QA. It follows that a LQA is expected to perform their duties with less supervision and greater behavioural proficiency (autonomy) than a QA, and also to provide leadership, assistance and guidance to the QA. How this increased knowledge and responsibility is used makes the role different. The LQA holds more responsibility and accountability than a QA and is more likely to be chosen to lead advanced and complex projects. Show less The QA is responsible for the planning, execution and completion of software testing and the related and relevant activities (including the creation and maintenance of checklists and documentation) which enable software testing project “sign-offs” to occur. In this description, these functions are collectively referred to as "testing". As a special mention, a subset of testing, specifically the identification and logging of defects is seen as a critical task for the QA. To accomplish testing, the QA is familiar with the methods of testing, various testing types (their application) and the technologies used, such as the network, environments, browsers and operating systems. The QA is also familiar with the products to be tested and the test tools related to these products. Behaviorally the QA has the ability to manage their time effectively, is focused on task completion and asks for more work when required. As the QA works primarily in a team environment, they are required to work well within a team and occasionally fulfill leadership functions, such as 2nd in charge (2IC) and/or Test Lead roles. This implies a level of resource management capability and responsibility. The QA is familiar with the standards, processes, methods and best practices followed in the execution of their duties. Show less

  • Software Development Engineer in Test - Level 2

    Aug 2023 - now

  • Software Development Engineer in Test - Level 1

    Feb 2022 - Jul 2023

  • Software Quality Engineer

    Dec 2019 - Feb 2022

  • Lead Quality Analyst 2

    Aug 2016 - Dec 2019

  • Lead Quality Analyst 1

    Jun 2015 - Jul 2016

  • Quality Analyst

    Mar 2014 - May 2015