SuperAPI AI Directory

hr-qa

General & other

View repository

Updated 10-16 05:45

About this skill

HR QA

Comprehensive Quality Assurance and Software Testing knowledge for HR and recruiters — from understanding modern QA workflows and automation testing to evaluating QA candidates, interpreting QA portfolios, and improving technical hiring decisions.

Supported tasks

  • Explaining QA and software testing concepts for non-technical recruiters
  • Understanding modern QA ecosystems and testing workflows
  • Screening QA and automation candidates effectively
  • Evaluating QA portfolios and GitHub profiles
  • Creating QA interview questions and hiring scorecards
  • Comparing Manual QA, Automation QA, SDET, and Quality Engineering roles
  • Understanding test automation and CI/CD integration
  • Identifying QA seniority levels and skill expectations
  • Understanding software quality, reliability, and release workflows
  • Writing QA job descriptions and hiring requirements
  • Explaining QA terminology used by engineers
  • Understanding QA collaboration with developers, DevOps, product, and design teams

What QA means in 2026

Modern QA is no longer:

  • "just manual testing"
  • "clicking buttons"
  • "testing after development is done"

In 2026, software quality increasingly includes:

  • automation testing
  • CI/CD integration
  • API testing
  • performance testing
  • AI-assisted testing
  • quality engineering
  • reliability engineering
  • production quality monitoring

Modern QA teams are becoming more engineering-focused, especially in automation-heavy environments.

QA ecosystem (2026)

Manual testing

  • Exploratory testing
  • Regression testing
  • Smoke testing
  • UAT (User Acceptance Testing)
  • Cross-browser testing
  • Mobile testing

Automation testing

  • Playwright
  • Cypress
  • Selenium
  • Appium

Playwright has become one of the dominant modern automation frameworks due to:

  • cross-browser support
  • TypeScript integration
  • built-in test runner
  • better stability compared to older Selenium-heavy setups.

API testing

  • Postman
  • Bruno
  • Insomnia
  • REST Assured

Performance testing

  • k6
  • JMeter
  • Gatling

Testing concepts

  • Unit testing
  • Integration testing
  • E2E testing
  • Contract testing
  • Visual regression testing
  • Accessibility testing

CI/CD and DevOps integration

  • GitHub Actions
  • Jenkins
  • GitLab CI
  • Docker

AI-assisted testing

  • AI-generated test cases
  • Self-healing tests
  • AI-assisted debugging
  • AI-generated automation scripts
  • Agentic testing workflows

AI-assisted testing is rapidly becoming part of modern QA workflows.

Types of QA roles

Manual QA Engineer

Focuses on:

  • exploratory testing
  • business validation
  • edge-case discovery
  • usability testing
  • release verification

QA Automation Engineer

Focuses on:

  • automated UI testing
  • API automation
  • regression suites
  • CI/CD integration
  • automation maintenance

SDET (Software Development Engineer in Test)

Focuses on:

  • automation frameworks
  • testing infrastructure
  • developer tooling
  • scalable test systems
  • engineering-heavy quality systems

Many companies use "SDET" and "QA Automation Engineer" interchangeably, but SDET roles often require stronger software engineering fundamentals and infrastructure ownership.

Quality Engineer

Focuses on:

  • end-to-end quality strategy
  • release confidence
  • process quality
  • observability
  • quality governance

Key prompts

QA fundamentals

  1. "Explain QA, SDET, and Quality Engineering in simple terms for [non-technical sourcers]."
  2. "What does a [QA Automation Engineer] actually do day to day in [startup vs enterprise environments]?"
  3. "What is the difference between [Manual QA, Automation QA, and SDET] roles?"
  4. "Why is early software testing and quality strategy important for [accelerating shipping speed]?"
  5. "What QA skills are most important for [e-commerce vs heavy cloud-native applications] in 2026?"

QA automation and tooling

  1. "What is the difference between [Playwright, Cypress, and Selenium] from a candidate screening perspective?"
  2. "Why are many modern QA teams migrating from [Selenium] to [Playwright]?"
  3. "What test automation tools and frameworks are common in [SaaS start-ups]?"
  4. "What QA automation trends should recruiters understand when hiring in [2026]?"
  5. "What test runner and assertions libraries should recruiters recognize on [SDET resumes]?"

QA candidate screening

  1. "How can I evaluate a QA candidate's [analytical and bug-hunting depth] without being highly technical?"
  2. "What are common red flags when screening [QA Automation vs Manual QA] candidates?"
  3. "What should I look for in a QA candidate's [GitHub repository, test suite portfolio, or bug reports]?"
  4. "How do I distinguish between [Junior, Middle, Senior, and Staff] QA engineers?"
  5. "Create a technical screening scorecard and interview questions for a [Senior SDET] role."

QA workflows and quality engineering

  1. "How do QA engineers collaborate with [developers, designers, and DevOps teams]?"
  2. "What does [CI/CD pipeline test integration] mean, and how does it prevent release blockages?"
  3. "What testing workflows (for example, shift-left testing) are common in [modern agile product teams]?"
  4. "How do QA teams prevent critical regression bugs before [major production deployments]?"
  5. "What modern Quality Engineering and observability practices are becoming important in [2026]?"

QA terminology for HR

  1. "Explain [regression testing, smoke testing, E2E testing, and API testing] in simple terms for [new recruiters joining the team]."
  2. "What do QA engineers mean by [flaky tests and test environment drift]?"
  3. "What is test automation, and why do companies use it for [large scale-up products]?"
  4. "What is CI/CD and why is it highly critical for [continuous release QA]?"
  5. "Which QA terms are [core quality skills] versus [transient automation tools] that I should filter for on resumes?"

QA hiring insights

Junior QA Engineer

Common expectations:

  • Basic testing knowledge
  • Bug reporting skills
  • Manual testing workflows
  • Understanding of SDLC basics
  • Basic API and browser testing awareness

Mid-level QA Engineer

Common expectations:

  • Automation testing knowledge
  • API testing experience
  • CI/CD familiarity
  • Test planning and regression ownership
  • Cross-team collaboration

Senior QA Engineer

Common expectations:

  • Test architecture design
  • Automation framework expertise
  • Performance and reliability awareness
  • CI/CD pipeline integration
  • Mentoring experience
  • Quality strategy ownership

Staff / Lead QA Engineer

Common expectations:

  • Organization-wide quality leadership
  • Testing platform ownership
  • Engineering process optimization
  • Automation strategy
  • Collaboration with engineering leadership
  • Quality governance and release strategy

Important hiring realities

QA is increasingly engineering-heavy

Modern QA roles often require:

  • coding skills
  • automation frameworks
  • API testing
  • CI/CD understanding
  • infrastructure awareness

This is especially true for SDET and Automation QA roles.

Manual QA still matters

Despite AI and automation growth:

  • exploratory testing
  • business validation
  • edge-case discovery
  • usability feedback
  • human judgment

remain difficult to fully automate.

QA roles are evolving, not disappearing

Many engineering teams now expect:

  • developers to write tests
  • QA to focus more on strategy
  • automation-heavy workflows
  • quality ownership across teams

This creates overlap between QA, SDET, and software engineering roles.

Common HR misunderstandings

QA ≠ only manual testing

Modern QA often includes:

  • coding
  • automation
  • infrastructure
  • CI/CD
  • API testing
  • performance testing

Automation QA ≠ Senior QA automatically

A candidate may:

  • know Playwright basics
  • but still lack:
    • test strategy
    • system thinking
    • debugging depth
    • quality engineering maturity

More automation tools ≠ stronger QA engineer

Strong QA engineers usually demonstrate:

  • testing mindset
  • edge-case thinking
  • debugging ability
  • quality ownership
  • communication skills
  • engineering collaboration

rather than only tool lists.

Tips

  • Senior QA engineers and SDETs should be evaluated on their testing mindset, quality strategy, and release confidence rather than just tool lists or scripting speed.
  • Portfolios and resumes are most credible when they show custom automation frameworks (e.g. Playwright, Cypress) built from scratch and integrated into CI/CD pipelines, rather than generic course certificates.
  • Recruiters should clarify the exact type of QA required: Manual/Exploratory QA (focus on user journey and edge cases), Automation QA, or SDET (Software Development Engineer in Test - strong coding capability).
  • Modern Quality Engineering is highly collaborative; engineers must work closely with developers and product managers to inject testing early in the software lifecycle.
  • Avoid writing unrealistic job descriptions that expect one QA engineer to simultaneously master manual testing, deep automation architecture, DevOps, security penetration testing, and performance testing.