You will decide what quality means on a project and then make it enforceable. That is less about writing many tests and more about writing the ones that fail when something is genuinely broken - and keeping the suite fast and trustworthy enough that nobody starts ignoring it.

What you ll do

- Own the test strategy on client projects: what is unit-tested, what is end-to-end, and what is not worth automating
- Build and maintain Playwright and Cypress suites that stay stable as the product changes
- Wire quality gates into CI so a regression blocks a merge instead of reaching a client
- Use AI to draft first-cut test cases from acceptance criteria, then edit them into tests worth keeping
- Triage flaky tests properly - a suite people ignore has negative value
- Run performance and accessibility checks as part of the pipeline, not as a pre-launch scramble

What we re looking for




- Three or more years in test automation, with suites you have owned through real product change
- Solid Playwright or Cypress, plus TypeScript or JavaScript
- API testing, test data management and CI integration
- The instinct to ask what a feature should do before asking how to test it

Nice to have Not required. Apply if the section above fits.
- Performance testing (k6, JMeter)
- Accessibility testing with axe
- Security testing basics - OWASP Top 10, dependency scanning

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 QA Automation Engineer (India)
🏢 ITLabz Technology
📍 India