We are seeking a QA Engineer with a strong manual testing mindset who has some experience with automation testing and takes ownership of product quality and user experience. This role focuses on thoughtful, risk‑based testing, clear communication, and collaboration.

You’ll work closely with engineering and product teams to ensure features are fit for purpose, reliable, and releasable, while contributing to continuous improvement of our QA approach. This role would sit embedded into one of our Development teams.

Key Responsibilities: 

• Own manual testing for assigned features from refinement to release
• Design and execute meaningful test scenarios, not just scripted cases
• Perform functional, regression, exploratory, and integration testing
• Validate requirements and acceptance criteria
• Identify risk, edge cases, and user‑impacting defects early
• Provide clear go/no‑go quality assessments for releases
• Raise clear, actionable defects with strong reproduction steps
• Assess severity, priority, and customer impact
• Work closely with developers to support root‑cause analysis
• Retest fixes thoroughly and verify acceptance
• Engage actively in backlog refinement, planning, and retros
• Challenge unclear or incomplete requirements constructively
• Communicate quality status, risks, and confidence clearly
• Contribute ideas to improve QA practices and consistency
• Support regression and release testing activities
• Work in a hybrid model (approx. 2 days currently onsite at Solihull Blythe Valley)

Requirements

• Strong manual testing experience in Agile environments
• Experience with at least one automation tool or framework (e.g. Playwright, Cypress, Selenium)
• Solid understanding of testing principles and techniques
• Ability to test across browsers, devices, and environments
• Experience with defect tracking tools (e.g. Jira, Azure DevOps)
• API testing basics (e.g. Postman)
• Comfortable validating data (basic SQL or equivalent)
• Familiarity with version control (Git) is a plus
• Thinks like a user, not just a tester
• Focuses on risk and impact, not box‑ticking
• Cares deeply about shipped quality
• Shift left experience in the development cycle
•