SAP QA Tester-local

Job: SAP QA Tester

Location: REMOTE / 1x/month onsite in DALLAS TX (LOCALS ONLY)

Term: 5+ months CT - through EOY with possible extension

Top Skills

• Experience in SAP and testing
• able to join project team and help hold vendors accountable to deliver on test planning and execution
• Want to be able to automate in the future -does need to be and automation engineer but have experience or exposure to automation
• Sr level
  

Job Description

We are implementing SAP S4 Hana as our new ERP system and integrating it with several existing apps. SAP will replace multiple ERPs and other software we use today. This is a multi-year program (we are about 1 year into it and will be completely rolled out to all locations by the end of 2027). Design and build are nearly complete. Test planning is in progress (defining the test cases, data needs, etc). Test execution will start mid-August. The first set of pilot locations will go live April 2025. Development is broken into about 8 workstreams, such as OTC, SCP, RTR, etc. Development and much of the testing is done by a 3rd party, with BFS IT and business driving the requirements, ensuring quality, etc.

Requirements

SR LEVEL SAP TESTER—must have experience with testing SAP and with qTEST

TOSCA Experience Preferred

MUST BE local to DALLAS willing to go on site 1x/month.

• What we are looking for is 2-3 people to work directly with the workstreams to provide coaching and oversight into testing.
• We want experts on SAP functions and experience designing and leading testing. While the workstreams have defined the test scenarios based on defined requirements, we want experts to review these, help us fill in any gaps we are missing, make sure we are focused on delivering a quality product.
• We do not want to completely depend on our 3rd party for these activities and learn too late that we have under tested and allowed issues to gest through to later testing phases and impact our project timeline or our business in production.
• They will need to be able to review our requirements (some of which may have been discussed or assumed but not fully documented) and ensure our testing is complete. They need to be strong enough to call out if we appear to be cutting corners, overlooking important things in testing, etc.
• We also need to be able to quickly adapt our manual testing to automated testing once code is stabilized, so they should have some knowledge on how to best approach testing in a way that makes it easily automatable in the future.
• They do not have to do the automation themselves, but need to make sure the test design allows us to easily transition to test automation in the future. Lastly, we are using Tricentis tools; qTest (Test Management), Tosca (Test Automation), NeoLoad (Performance Testing), so experience with these particular tools may be helpful.