QA Engineer - Intermediate; SP- IT Process Automation
Oregon, Ogle County, Illinois, 61061, USA
Listed on 2026-02-03
-
Software Development
QA Engineer - Intermediate (SP6) - IT Process Automation
Listing reference:
Listing status: Online
Apply by: 28 September 2025
Position summaryJob category: Informatics
Location: International
Contract: Permanent
EE position: No
IntroductionThe QA Engineer (Intermediate) assists and facilitates the planning stage with all agile team members. The QA Engineer (Intermediate) works closely with the agile team to create test plans, manage test activities, and monitor quality deliverables. The role helps meet deadlines by breaking up the development process into attainable testing goals and relaying any issues back to the development and product teams.
Agile Testing applies the principles of agile development to the practice of testing. Although traditional development has used a big-bang, deferred testing approach, agile testing develops and tests systems in small increments, often developing tests before writing the code, Story, or Feature. Quality is built in from the beginning. Agile testing is a collaborative, team-oriented process.
- Help monitor performance and uncover system vulnerabilities through tools and bug-tracking systems
- Conduct testing activities, whether manual or automated QA testing, during appropriate development stages to eliminate bugs and flaws
- Work with Software Engineers, Automation Engineers, and other stakeholders to troubleshoot testing failures and bugs
- Code, script, and configure automated tests
- Discover bugs and failures within the software
- Identify, isolate, and track bugs throughout testing
- Identify any potential problems that users might encounter
- Perform manual and automated testing
- Review requirements, specifications, and technical design documents to provide timely and meaningful feedback
- Perform thorough regression testing when bugs are resolved
- Set the QA process objectives to ensure that the result leads to the fulfilment of all product requirements
- Plan testing activities according to the objectives and create a strategy based on schedule and other project specifics
- Communicate with the Scrum Master, Product Owner, and other stakeholders about QA activities and progress
- Develop standards and procedures to determine product quality and release readiness
- Design and build tools and processes to verify requirements for failures and bugs
- Document the testing results and analyze the errors to identify their root cause
- Unit and component tests to confirm that the system works as intended; tests are written to run before and after code changes. This is the home of Test-Driven Development (TDD) in software.
- Functional tests (user acceptance tests) for stories, features, and capabilities to validate that they work as the Product Owner (or Customer/User) intended. Feature-level and capability-level acceptance tests confirm the aggregate behaviour of many user stories. Teams automate these tests using Behaviour-Driven Development (BDD) techniques wherever possible and use manual ones only when there is no other choice.
- System-level acceptance tests to validate the behaviour of the complete system meets usability and functionality requirements, including scenarios often encountered during system use. These may include exploratory tests, user acceptance tests, scenario-based tests, and final usability tests. They are often manual and the final system validation before delivery to the end-user.
- Contains system qualities testing to verify the system meets its Non-functional Requirements (NFRs), often supported by a suite of automated testing tools (such as load and performance) designed for this purpose. Since changes can affect NFR conformance, these must be run continuously or as practical.
Minimum
- ABachelorof Scienceor Master 'sdegreein
Computer Science, Engineering, or a related subject - Arelevant Software Quality Assurance Certificationwillbeanadded advantage
Ideal
- Master’sDegreein Computer Scienceor Software Engineering
Minimum
- 2 years of banking experience
- 4 years of relevant software quality assurance experience
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).