Enterprise Test & Quality Lead

Key Responsibilities

• Own the end-to-end test management lifecycle across Unit Testing, System Integration Testing, QA, UAT, regression testing, and release readiness.
• Define and drive a Quality Engineering strategy embedding automated testing across the SDLC including “shift-left” and “shift-right” practices.
• Define and maintain the overall test strategy, test plans, phase entry and exit criteria, acceptance thresholds, and defect management approach.
• Work and align with incumbent vendor to align QA to this overall strategy.
• Define and enforce automated quality gates within CI/CD pipelines.
• Carefully coordinate testing across multiple concurrent scrum teams, ensuring alignment of delivery schedules, dependencies, and release milestones.
• Define an environment strategy that enables parallel team execution, minimizes contention, and supports continuous testing.
• Ownership of Test Data Governance Framework
• Ensure adherence and support from DPO / IRM / Privacy
• Own the approach to Test Data Management, including data readiness, lineage, masking or obfuscation controls, and interim solutions required to support testing safely and effectively.
• Partner with QA leads to define test scenarios, test cases, regression coverage, and the appropriate level of automation, including use of tools such as Tosca to deliver ROI driven automation, decisions on what to automate and coverage targets.

KPI Management

• QA vendorSLA tracking
• Capability and skill matrix optimization
• Trend analysis of defect origin (code, data, environment, design) leading to systemic issue elimination

Key Interfaces

• This role will work closely with Development Leads, QA Leads, Product Owners, Business UAT representatives, Environment and Release Management teams, Data and Privacy stakeholders, and senior programme or technology leadership.

Success Measures

• Improved coordination and predictability across QA and UAT cycles including continuous validation and early user involvement.
• Reduction in defects caused by environment or data issues rather than true functional failures.
• Clear and consistently applied phase entry, exit, and acceptance criteria.
• Increased confidence in release readiness and reduced rework or defect recycling.
• Greater use of automation and regression coverage to support faster retest cycles.
• Stronger governance, visibility, and accountability for end-to-end testing outcomes.