QA Lead

Our local direct client is seeking a talented QA Lead to join their team. This is a contract to hire opportunity and they have a hybrid office schedule.Please let us know if you would be a great fit!

• Creates and executes various testing documentation (including plans, conditions, and scripts) based on technical and user requirements:
• Writes and maintains test automation.
• Tests software to ensure proper operation and freedom from defects and/or system performance including scalability and load testing.
• Performs regression testing.
• Ensures adequate product testing, in accordance with established standards and requirements, prior to implementation.
• Maintains Test Script Library and/or performance test results.

• Identifies and resolves problems in areas of test development/management.
• Devises improvements to current procedures and develops models of possible future configurations.
• Exhibits expert business knowledge and leverages strong customer relationships.
• May have responsibility for performance and coaching of staff and may have a participatory role in decisions regarding talent selection, development, and performance management for direct reports.

• Provide mentoring, training and feedback to resources on the team.
• Review work output of assigned project and product resources.
• Establish cross-functional relationships with peer groups such as development, program management, product management, etc.
• Oversee and provide feedback on offshore delivery, working with onsite leads.
• Seen as the go-to QA person for your assigned value stream (end to end).
• Ability to communicate effectively with many levels across the organization.

• Expert understanding of QA processes, standards and templates. This means ability to complete QA deliverables and train others on the same.
• Understanding and ability to present QA strategy to product and project teams.
• Understanding available tools and usage to meet QA deliverables.
• Provide continuous improvement opportunities as found.
• Performance: ability to communicate and elicit Non Functional Requirements

• Attend PI and sprint planning/grooming sessions and perform requirement auditor function, ensuring user stories are testable based on the acceptance criteria.
• Provide resource/work estimation for projects from an end to end system view. This would feed into the overall project plan and is specific to centralized QA resources.
• Understanding of unit and component level testing and results. For some projects we may have the responsibility of performing the component level testing, for example for APIs. Ownership of the testing should be in the test plan.
• Ownership of the test plan from end to end from a system and project. This means the QA lead knows who is impacted by the work and who is responsible for the testing, collects the test plan for all involved and creates a “master test plan”. We may not be doing the testing within Centralized QA, but we know and document who is.
• Consulting with areas outside of Centralized to create test plans and test scenarios. (they do not own writing the test plan or test scenarios, they are available to assist with any questions, etc. Providing guidance.)
• Ownership and reporting of test status. The cadence and level of reporting may depend on the project. It could be daily, weekly, test sign off at various stages. This is end to end from a system and project perspective. This means the QA lead collects the status of testing for all impacted teams and understands it in order to speak to it, whether centralized QA is doing the testing or not and is able to report on status.
• Facilitation and ownership of Defect Review Board meeting. The way this is run and cadence depends on the project. This could be handled in daily standups or may need to be a formal daily, or weekly meeting.
• Ownership and reporting of defect status. The cadence and level of reporting may depend on the project. It could be daily, weekly, test sign off at various stages. This is end to end from a system and project perspective. This means the QA lead knows the status of outstanding defects for all impacted teams, regardless of ownership and is able to present status. Leads may need to track down owners to push for closure.
• Responsible for quality gates into/out of system integration testing and user acceptance testing phases. These need to be communicated and agreed to by the team and enforced by the QA lead.
• Responsible for test summary as part of go-no-go to UAT and Production.
• Understanding of UAT test plan, and responsible for ensuring proper creation and tracking of defects found in UAT. These should go through DRB.
• Understanding of Production issues and how they relate back to our test plans.
• Able to provide requirement traceability to test cases.
• Input to project timelines and verifying QA is tracking to plan.
• Provide risk analysis, management and escalation as necessary. This includes identification and communication of impact due to any deviations in delivery and resourcing.

• Provide data for input into monthly QA scorecard.
• Analyze defect leakage, provide root cause analysis and improvement plans.
• Understand and be able to produce tactical project and program metrics for value stream.