Will AI Steal My Job? · Role analysis

QA / Test
Engineer

O*NET 15-1253.00 ESCO: Software testers
Changing

QA and test engineers ensure software works correctly, performs reliably, and meets specified requirements before release. They design test plans, write automated and manual test cases, execute regression testing, report defects, and work with developers to verify fixes — acting as the quality gate between development and production.

Task Map

TaskAI impactWhy
Write automated test scripts 🔴 High exposure AI coding tools generate test scripts from function signatures and requirements rapidly. Writing standard Selenium, Cypress, or Playwright tests is heavily AI-accelerated — this was one of QA's most time-consuming tasks.
Execute regression test suites 🔴 High exposure Regression testing runs automatically in CI/CD pipelines. The manual execution of test suites that defined traditional QA work is now almost entirely automated in modern development environments.
Design test plans and test coverage strategies 🟡 Changing AI can suggest test scenarios from requirements documents, but deciding what risk areas to prioritise, what edge cases matter in context, and what to leave untested requires professional judgment about the product and user behaviour.
Investigate and reproduce reported bugs 🟡 Changing AI can analyse bug reports and suggest reproduction steps, but tracking down intermittent bugs in complex systems — understanding the conditions that trigger them — often requires systematic investigation and intuition.
Perform exploratory and usability testing 🟢 Safe Exploratory testing — using the software as a real user would, noticing what feels wrong, unexpected, or confusing — requires human intuition about user experience that automated tools cannot replicate.
Write bug reports and communicate with developers 🟡 Changing AI drafts clear bug reports well, but the QA engineer who understands developer workflow, builds rapport with the team, and advocates effectively for quality standards provides relationship value beyond report writing.
Review requirements for testability and completeness 🟡 Changing Identifying ambiguous, contradictory, or untestable requirements before development starts saves significant rework. This analytical work — reading between the lines of product specs — requires experienced professional judgment.
Set up and maintain CI/CD test infrastructure 🟡 Changing AI assists significantly with pipeline configuration, but designing a reliable, fast test infrastructure that integrates with complex deployment environments requires both DevOps and QA expertise.

What Stays Human

What to Do Next

  1. Develop strong automation engineering skills, not just test scripting. QA engineers who can build robust test frameworks, integrate them into CI/CD pipelines, and maintain them at scale are doing software engineering work that commands developer-level salaries. ISTQB Advanced Test Automation Engineer plus hands-on experience with Playwright or Cypress and cloud testing platforms is a strong foundation.
  2. Move towards performance engineering, security testing, or accessibility testing — specialisms where automated tools assist but cannot replace human expertise. Performance testers who can design load tests and interpret results in business terms, or security testers who can find application vulnerabilities, are in consistent demand across the industry.
  3. Build skills in AI system testing and evaluation. Testing LLM-based applications — evaluating whether AI outputs are accurate, safe, and aligned with requirements — is a genuinely new specialism that applies QA thinking to a domain where traditional automated testing doesn't work. QA engineers who understand prompt engineering and AI evaluation are at the frontier of the field.
Sources: O*NET Online (onetonline.org) · ESCO (esco.ec.europa.eu) · All task data cross-referenced against O*NET occupation profiles. This analysis uses task-level exposure, not occupation-level prediction.