Test Lead

The Test Lead will be the senior testing and quality engineering authority within the CLMi Engineering organisation. You will own and evolve the overall product testing strategy, establish appropriate standards and provide direction on testing practices across multiple engineering teams. Working closely with Engineering Managers, Lead Engineers, Principal Engineers, developers and testers, you will promote a culture in which quality is a shared engineering responsibility.

This is not a conventional people-management position. Your impact will come through technical credibility, strategic ownership, coaching and your ability to influence teams and senior stakeholders. You will maintain sufficient hands‑on involvement to understand current challenges, review testing approaches, investigate complex quality issues and ensure the strategy is delivering measurable improvements. Your objectives

• Own and evolve the CLMi product testing and quality engineering strategy.
• Promote a culture in which quality is shared across the engineering organisation.
• Improve the consistency, effectiveness and maturity of testing practices.
• Define appropriate testing standards, principles and governance.
• Establish the appropriate layering of testing across unit, integration, API, UI and end‑to‑end levels.
• Shape automation strategy and improve the reliability and maintainability of automated test suites.
• Embed risk‑based testing throughout planning, development and release activities.
• Improve testability, defect prevention and the use of meaningful quality metrics.
• Coach testers, developers and engineers in effective quality practices.
• Ensure release decisions are supported by appropriate quality evidence.

• Act as the recognised subject matter expert for software testing and quality engineering.
• Own, communicate and continuously improve the CLMi product testing strategy.
• Establish testing principles, standards and governance across engineering teams.
• Promote quality as an engineering‑wide responsibility rather than an activity owned exclusively by testers.
• Influence teams and senior stakeholders without relying on direct line‑management authority.
• Challenge testing practices that are ineffective, overly manual or difficult to sustain.
• Help teams balance delivery priorities against product, technical and operational risk.

• Define how testing should be distributed across unit, component, integration, API, UI and end‑to‑end layers.
• Encourage testing at the earliest practical stage of the software development lifecycle.
• Guide teams in their use of functional, exploratory and automated testing.
• Ensure testing remains proportionate to technical complexity, business criticality and delivery risk.
• Review the effectiveness of existing testing practices and lead improvement initiatives.
• Ensure appropriate quality evidence is available to support release decisions.

• Provide strategic direction for automated testing frameworks and implementation approaches.
• Promote reliable, maintainable and scalable test automation.
• Ensure appropriate integration and layering of automated testing in the CI/CD delivery pipeline.
• Improve automated feedback cycles and reduce unreliable or low‑value tests.
• Support the review of automation code, test architecture and engineering practices.
• Help teams determine which tests should run at different stages of the delivery pipeline.

• Provide direction on performance, load, stress, scalability and capacity testing.
• Promote security‑focused testing and validation practices.
• Encourage accessibility considerations throughout design, development and testing.
• Support effective test environment and test data…