Qa Analyst Test Engineer

Korey Schultz

Minneapolis/St. Paul and Suburbs Cell Phone Number: (952) -232-7385

https://www.linkedin.com/in/korey-schultz-b0b083240/ Email: **************@*****.***

Professional: QA Software Test Engineer:

Employment Objective:

I am pursuing an IT Quality Assurance Software Engineer position which will allow me to utilize over a decade of professional Information Technology expertise that includes experience in diverse application areas performing: Systems Software Analysis and Testing, Design, Development, Production Implementation, System Maintenance, and project co-ordination functions.

KEY AREAS OF EXPERTISE:

Finance - Medical Banking/Health Savings Products:

I created testing scenarios on multiple platforms: utilizing Integration, Quality, and Production environments to support business requirements for Group, Member, Agent, systems and portals for business Cloud Based connectivity. These areas focused around supporting employer Health Savings account products offered to their employees.

Functional Analysis and Testing:

I pride myself in having excellent ability to perform independent analysis of business requirements and develop effective solutions that satisfy customer end-to-end testing expectations.

Software Development and Testing:

I have extensive experience in Designing, Developing, Testing and Implementing a variety of business IT Software applications in a number of different development, operational, and industry environments.

Project Coordination:

I have proven ability to perform as a technical mentor; Training and Directing small to medium size project teams engaged in QA Planning and Testing of IT business software applications for client organizations.

Software Maintenance and Support:

Significant experience in performing day-to-day maintenance and support of existing applications in parallel with the analysis, testing, design, development and coordination activities for new applications.

PROFESSIONAL EXPERIENCE:

Allianz Life Insurance: Golden Valley, MN. (06/22 – 10/22)

Position: Senior Quality Assurance Analyst: Contract through Horizontal Talent.

Allianz Life Insurance Products:

Following Allianz Life Insurance Company BRD’s, (business rules documentation), as a Senior QA Analyst, I worked on a fast-paced QA team supporting Life Product. Life Product applications focused in an Agile structure, promising the scheduled delivery of semi-monthly sprints. These sprints encompassed around utilizing swim-lane testing environments, developed and structured, for each target release. While focusing around this Research, Evaluation, and Functional Testing of their new cloud-based systems, we worked hand-in-hand with the development teams within Accenture’s offshore venders. This ALIP 2.0 platform was managed through the Polarion Agile project management applications. Utilizing their new cloud-based ALIP 2.0 system, it was my responsibility as a senior QA Analyst to create new Life Product Insurance applications for customer policies with a Product Type of Universal Life for Navigator IUL.

These applications covered a variety of life insurance customer policy options such as Insured and Owner, Medical, Joint Owner, Contingent Owner, Beneficiaries, Policies, Premiums, Funds, Replacement, Transfers, Agents, Producers, and Producer Reports.

Polarion Applications, and End-to-End Functional Requirement Testing:

Utilizing Siemens Polarion ALM and Company BRD’s:

I used Siemens Polarion ALM as a collaboration tool between all Agile teams to collaborate and share project assets easily and securely. I had the functionality to control who can see and, who can change, my workflows and documentation.

I also used Polarion for:

Writing, Executing, and Documenting Test Cases for business approved User Stories.

Creating and Assigning Tasks through Polarion for UAT review.

Creating and Assigning Defect Tasks through Polarion for Development review.

Estimating Story Points for User Story business projects.

Create “PASS/FAIL” Test Scenarios.

Provide Acceptance and Validation Criteria.

Provide Test Case Descriptions.

Provide pre-conditions, Assumptions, and Test Data.

Link Test Cases to Requirements.

Provide Expected Results and Actual Results.

Record Status, Environments, and Defect tracking.

Suggest Regression and Automation expectations and recommendations.

Communicate timely with UAT.

Stella Resources; Eagan, MN / HealthEquity Inc: Draper, UT. (05/14 – 01/22)

Position: Testing Engineer: – Employee under sister company -- Further Inc.

Healthcare Finance, IT Medical Banking:

From 2014 to 2022, I worked at the Blue Cross Blue Shield campus in Eagan Mn as a Full Stack QA Test Engineer for a company called Further Inc. While at Further, our IT staff followed an Agile project management structure with my job focused on UI and API testing against their Healthcare business Core Systems and Portals. Utilizing SQL and our company’s UI, I created testing scenarios, and set up pertinent data, to test insurance claims and payments for customer HealthCare accounts on multiple platforms. These platforms included Integration, Stage, and Production environments to test business requirements. These requirements focused around supporting employer medical account products offered to their employees. My experience helped me become recognized by our leadership teams as a training liaison for new employees and contractors.

System and Testing Applications used over the past 8 years:

CONFLUENCE / KANBAN-ATLASSIAN:

Confluence was our companies complete documented Project Management system. I used Confluence daily, and became the author of, multiple project release pages documenting Test Plans and Strategies for the business and portal, GUI, and API applications related to release projects I was responsible for.

Confluence was also used to store all of our business Use Cases containing the Business Rules related to each project for each release.

JIRA:

I used Atlassian JIRA to work hand-in-hand with CONFLUENCE to Delegate Projects.

I used JIRA to Track, Debug, Communicate, and record Project Status.

As a QA Test Engineer, I worked closely with Developers to communicate ticket debugging strategies in order to recreate the issues identified by UAT. Developers could follow my re-creation in a lower environment and step their code, line by line, through any of the Business Rules that may have been breached.

AGILE:

I attended daily Agile Scrums to go over User Story project status and estimates. These daily meetings required the attendance of all Test Engineers, Developers, Business Analyst’s, Business Stakeholders, and Project Managers assigned to specific scheduled quarterly release activity outlined in Confluence.

SDLC/ALM;

SDLC and ALM were our companies Life Cycle Development and Management protocols. They worked hand-in-hand together although the main difference was SDLC is primarily focused on the development phase, where ALM reflects the entire application life cycle, from concept to maintenance through after the application has been developed.

MICROSOFT TEAMS / OFFICE SUITE:

Microsoft Teams and Microsoft Office were our interactive communication, meeting, email and documentation applications.

MySQL WORKBENCH:

I used MySQL Workbench as a visual database design tool to integrate SQL development, administration, database design, creation and maintenance into a single integrated development environment.

TOAD DATA POINT 5.0:

Toad Data Point 5.0 was an application I used for writing SQL Queries and Scripts to update, and test against, our company’s relational DB2 platforms. I used SQL to create live testing scenarios that reflect project driven Business Rule system modifications. Toad was our database management toolset from Quest Software for managing DB2 using SQL.

DBEAVER-SQL:

I used DBeaver as a SQL Query and Script communication tool used on our Integration, scrubbed, lower testing platform.

POSTMAN: REST-API:

I used Postman for our Cloud Based UI/API Testing along with Workspace. Postman/Workspace gave me a consolidated view of all the Postman elements as they are commonly used such as collections, environments, integrations, history, etc.

I also used Workspace to setup automated API testing in Postman for our system Smoke Testing.

READY API:

Ready API was used as an API Testing application to set up, test, and debug, Request/Response scenarios outlined within our companies Use Case business rules.

SoapUI by Smartbear:

I wrote SQL queries directly against the database to verify API tests responses and the validity of those responses.

Java:

I have 8 years of testing experience against Java programs and applications developed by our companies programming teams.

Aurora:

We utilized AWS and Aurora when we brought our companies Core Systems into the Cloud in 2017. Aurora was our new relational database, I tested against our companies’ Reporting systems and the transfer between DB2 and Aurora.

Professional Testing Experience:

Interactive Testing: I used interactive testing daily to Create, Update and Facilitate manual test scenarios against our company’s Business, and Portal Systems, to ensure UI and API’s were working as expected. These tests were then documented.

Regression Testing: I used regression testing to perform and determine code modifications did not break the updated application.

Sanity Testing: I used sanity testing to verify Break-fix bugs are fixed and that no further issues are introduced to the current system.

End to End Testing: End to end testing was our company’s standard protocol to make sure everything functions as expected after updates or bug fixes.

Acceptance Testing: I worked closely with (UAT) to ensure that the end-user (customers) can achieve the goals set in the business requirements.

Integration Testing: It was my responsibility to ensure that integrated systems meet and adhere to our company’s hardware and software environment requirements and that the entire system functions properly.

Accessibility Testing: We had to test to make sure our company’s end product ensured that our mobile and web apps are working and usable for all users regardless of any disability.

Black Box Testing: Black Box Testing was our method for testing software API functionality without the knowledge of the internal source code.

Load Testing: We used load testing against our software applications to review system behavers while being accessed by multiple users simultaneously.

Security Testing: We used security testing in an attempt to unveil any vulnerabilities within the system and to ensure that the software system and application are free from any threats or risks.

Other Responsibilities Included:

I was appointed by management to act as a liaison for on-board employee/contractor training, utilizing company testing procedures and methodologies in bringing new recruits up to speed with our Business, Portal, Batch, Mobile and Report systems.

I used Confluence to create test cases for applications under test in large projects, based on system requirements and technical design documentation, using automation to the fullest extent.

I worked closely with the business teams to specify and identify partner test data needs for the test cases to be performed, recommending cost, schedule, and efficiency techniques.

I worked hard in the re-creation of Performance and Analysis of test environment setup for the test cases to be performed.

I analysed test results and documented defects and issues using JIRA’s Incident Management Process.

I was a member of a rotating On-Call production support team.

I have completed annually, professional HIPAA, PHI, FRAUD & WASTE, and SECURITY training.

I worked with and helped generate metrics related to system quality.

I actively engaged with business stakeholders in the planning and collaboration of user acceptance test cases, as needed and requested.

I always adhered to the Companies methodology and test deliverables.

I used Beyond Compare to compare before and after results of upgrades that reflected on our company’s reporting systems.

CoreLink Administrative Solutions: Fargo, ND. (02/08 – 10/13)

Mainframe COBOL: Analyst/Developer III, – Employee.

Healthcare Insurance, IT:

From 2008 to 2013: While working at CoreLink, it was my responsibility to ensure proficiency within Analysis, Design, Development, Testing, Documentation, and Production Implementation of assigned new and existing applications by following all appropriate policies and procedures and, be held accountable for timely and accurate on-going production systems. I worked as an IT Analyst / Developer, specializing in the maintenance and support of existing, medical claim systems for Blue Cross Blue Shield of North Dakota, Wyoming, and Nebraska. I was part of a large “AGILE”, Stable Team, which used Business Intelligence, BI, data gathering and SDLC methodologies to work closely with customers to maintain software application up-dates based upon business specification requirements handed down through senior level managerial requests. These lines of business that I supported include, Professional and Institutional, Medical, Dental, and Vision claim processing and payment systems.

Education:

Mayville State University – ND

Bachelor Science, Computer Information Systems,

Minor: Mathematics

Honor Graduate: Magna Cum Laude

Contact this candidate