Remoteria
RemoteriaBook a 15-min intro call
500+ successful placements4.9 ★ (50+ reviews)30-day replacement guarantee

Job description template

QA Tester Job Description Template (2026)

A free, copy-ready QA Tester job description covering responsibilities, must-have skills, tools, seniority variants, and KPIs. Written for hiring managers, not for SEO filler.

Hire a pre-vetted qa tester

Key facts

Role
QA Tester
Reports to
Reports to the QA Lead or Engineering Manager
Must-have skills
8 items
Seniority tiers
Junior / Mid / Senior
KPIs defined
6 metrics
Starting price (offshore)
$1600/month

Role summary

A QA Tester owns product quality end to end: writing structured test plans against PRDs, running exploratory and regression sessions across browsers and devices, maintaining a Playwright or Cypress automation suite, filing reproducible defects with video capture, and signing off releases with a written summary of coverage. Partners with engineering on CI test integration and with product on acceptance criteria before a single line is written.

Responsibilities

Must-have skills

  • • 3+ years of QA experience on production web or mobile apps for US or European clients.
  • • Hands-on automation in Playwright 1.40+ or Cypress 13+ with Page Object Model or fixture-based patterns.
  • • API testing with Postman/Newman or a code-based tool (REST-assured, Karate, supertest) in CI.
  • • Fluency in test case design techniques: equivalence partitioning, boundary value analysis, decision tables, state transition.
  • • Defect lifecycle management in Jira or Linear with a clear severity vs priority distinction.
  • • Working knowledge of CI pipelines (GitHub Actions, CircleCI, GitLab CI) for test integration.
  • • WCAG 2.1 AA accessibility audit skills with axe, keyboard testing, and at least one screen reader.
  • • Strong written English for bug reports, test plans, and release notes.

Nice-to-have skills

  • • Performance testing with k6, JMeter, or Locust for load and stress scenarios.
  • • Visual regression experience with Percy, Chromatic, Applitools, or Playwright snapshots.
  • • Mobile automation with Appium, Maestro, or Detox.
  • • ISTQB Foundation or Advanced certification.
  • • Security testing awareness (OWASP Top 10, Burp Suite basics).

Tools and technology

Reporting structure

Reports to the QA Lead or Engineering Manager. Partners daily with engineers on triage and CI test health, with product managers on acceptance criteria review, with designers on accessibility and interaction-level details, and with customer support on reproducing escaped defects.

Seniority variants

How responsibilities shift across junior, mid, and senior levels.

junior

1-2 years

  • • Execute scripted test cases from existing test plans and file reproducible bugs.
  • • Run cross-browser manual testing on the defined matrix.
  • • Write basic Playwright or Cypress tests for simple flows under review.
  • • Learn severity/priority rubric and apply consistently.

mid

3-5 years

  • • Own the test plan for a feature area from PRD review to release sign-off.
  • • Maintain and extend the Playwright/Cypress suite including flaky test remediation.
  • • Drive daily bug triage with engineering and escalate blockers.
  • • Partner with product on acceptance criteria and risk-based testing prioritization.

senior

6+ years

  • • Set test strategy: automation pyramid shape, tooling choices, CI gating policy, release criteria.
  • • Own the regression suite architecture and keep the suite under 15 minutes on CI.
  • • Run accessibility audits and lead remediation conversations with engineering.
  • • Mentor junior testers, run the QA hiring loop, and represent QA in architecture reviews.

Success metrics (KPIs)

Full JD (copy-ready)

Paste this into your ATS or careers page. Edit the company name and any bracketed placeholders.

# QA Tester — Job Description

## Role summary
A QA Tester owns product quality end to end: writing structured test plans against PRDs, running exploratory and regression sessions across browsers and devices, maintaining a Playwright or Cypress automation suite, filing reproducible defects with video capture, and signing off releases with a written summary of coverage. Partners with engineering on CI test integration and with product on acceptance criteria before a single line is written.

## Responsibilities
- Author test plans and test cases in TestRail, Xray, or Qase mapped to requirements, covering happy path, edge cases, error states, and negative paths.
- Review PRDs and Figma specs before dev starts and flag missing acceptance criteria and ambiguous behaviors.
- Run exploratory charter-based sessions on new features with session notes, timebox, and follow-up scripted tests.
- Build and maintain Playwright or Cypress end-to-end suites for critical flows (signup, checkout, auth, payments) with stable selectors and retry policies.
- Write API contract tests in Postman/Newman, Karate, or REST-assured and wire them into the CI pipeline on every PR.
- File reproducible Jira or Linear defects with numbered repro steps, expected vs actual, video capture (Loom/Jira Capture), console logs, and Charles Proxy traces.
- Assign severity (S1-S4) and priority (P0-P3) using a written rubric; drive daily bug triage with engineering.
- Run cross-browser testing via BrowserStack or Sauce Labs on the defined matrix (Chrome, Safari, Firefox, Edge — latest 2 versions).
- Run mobile testing on real devices plus Xcode Simulator and Android Emulator against a documented device matrix.
- Audit new screens against WCAG 2.1 AA using axe DevTools, Accessibility Insights, keyboard-only walkthroughs, and screen reader passes (VoiceOver, NVDA, TalkBack).
- Tune out flaky tests through better selectors (data-testid), test isolation, network mocking, and explicit waits; keep suite flake rate under 2%.
- Sign off releases with a written release report covering what was tested, what was skipped and why, and known issues.

## Must-have skills
- 3+ years of QA experience on production web or mobile apps for US or European clients.
- Hands-on automation in Playwright 1.40+ or Cypress 13+ with Page Object Model or fixture-based patterns.
- API testing with Postman/Newman or a code-based tool (REST-assured, Karate, supertest) in CI.
- Fluency in test case design techniques: equivalence partitioning, boundary value analysis, decision tables, state transition.
- Defect lifecycle management in Jira or Linear with a clear severity vs priority distinction.
- Working knowledge of CI pipelines (GitHub Actions, CircleCI, GitLab CI) for test integration.
- WCAG 2.1 AA accessibility audit skills with axe, keyboard testing, and at least one screen reader.
- Strong written English for bug reports, test plans, and release notes.

## Nice-to-have skills
- Performance testing with k6, JMeter, or Locust for load and stress scenarios.
- Visual regression experience with Percy, Chromatic, Applitools, or Playwright snapshots.
- Mobile automation with Appium, Maestro, or Detox.
- ISTQB Foundation or Advanced certification.
- Security testing awareness (OWASP Top 10, Burp Suite basics).

## Tools and technology
- Playwright 1.40+ / Cypress 13+
- TestRail / Xray / Qase
- Postman / Newman
- BrowserStack / Sauce Labs
- Jira / Linear
- Charles Proxy / Proxyman
- axe DevTools / Accessibility Insights
- GitHub Actions / CircleCI
- Appium / Maestro
- k6 / JMeter

## Reporting structure
Reports to the QA Lead or Engineering Manager. Partners daily with engineers on triage and CI test health, with product managers on acceptance criteria review, with designers on accessibility and interaction-level details, and with customer support on reproducing escaped defects.

## Success metrics (KPIs)
- Escaped defect rate (production P0/P1 bugs per release) trending down quarter over quarter.
- Automation suite runtime under 15 minutes on CI with flake rate below 2%.
- Critical path automation coverage above 90% on auth, checkout, and money-touching flows.
- Bug reopen rate below 10% — measures repro-quality of filed tickets.
- Release sign-off delivered within the SLA window (typically 4 hours) with written report.
- Zero WCAG 2.1 AA critical issues shipped to production on audited flows.

Frequently asked questions

What does a QA Tester do day-to-day?

A QA Tester owns product quality end to end: writing structured test plans against PRDs, running exploratory and regression sessions across browsers and devices, maintaining a Playwright or Cypress automation suite, filing reproducible defects with video capture, and signing off releases with a written summary of coverage. Partners with engineering on CI test integration and with product on acceptance criteria before a single line is written.

How many years of experience should a mid-level QA Tester have?

A mid-level QA Tester typically has 3-5 years of experience. At that level they should own the test plan for a feature area from prd review to release sign-off.

Which KPIs should I hold a QA Tester accountable to?

The most important KPIs for a QA Tester are: Escaped defect rate (production P0/P1 bugs per release) trending down quarter over quarter.; Automation suite runtime under 15 minutes on CI with flake rate below 2%.; Critical path automation coverage above 90% on auth, checkout, and money-touching flows.; Bug reopen rate below 10% — measures repro-quality of filed tickets..

Do they handle manual testing, automation, or both?

Both, but we match the split to your stage. Early-stage products where the UI changes weekly benefit from heavy manual and exploratory testing and light automation only on the truly stable flows like auth and billing. Mature products with a locked spec benefit from a large Playwright or Cypress suite covering critical paths plus targeted manual work on new features. We ask in the kickoff call what your current ratio is and match accordingly. A senior QA in our network typically runs 60 percent manual and 40 percent automation on mid-stage apps.

How do they decide what to automate versus test manually?

Stable, repeatable, and boring gets automated. Flaky, exploratory, or visually subjective stays manual. Standard framework is the test automation pyramid: automate unit and API-level tests aggressively, automate a thin layer of end-to-end tests on the critical money-touching paths (signup, checkout, auth), and leave the top of the pyramid for exploratory sessions run by a human. They will push back on automation targets that demand coverage percentages without explaining which flows actually matter.

Related

Written by Syed Ali

Founder, Remoteria

Syed Ali founded Remoteria after a decade building distributed teams across 4 continents. He has helped 500+ companies source, vet, onboard, and scale pre-vetted offshore talent in engineering, design, marketing, and operations.

  • • 10+ years building distributed remote teams
  • • 500+ successful offshore placements across US, UK, EU, and APAC
  • • Specialist in offshore vetting and cross-timezone team integration
Connect on LinkedIn

Last updated: April 12, 2026