QA automation engineer job description template (2026)
A complete QA automation engineer job description you can copy, covering test strategy, Playwright and Appium, CI pipelines, flaky tests and seniority levels.
By the Ryz Labs team · Updated October 2026
A QA automation engineer job description should say what the person is accountable for: writing test scripts, or owning test strategy and release confidence. The strongest candidates design a test pyramid, choose what not to automate, keep suites fast and trustworthy in CI and treat flaky tests as bugs. Say which surfaces need coverage (web, mobile, APIs), which framework you use or want to move to and how releases are gated today. The template below targets a senior QA automation engineer who owns automation strategy for a product team. Copy it, adjust and cut what does not apply.
QA automation engineer job description template
Job title
Senior QA Automation Engineer (Web, API and Mobile)
Employment type: full-time or contract. Location: remote, with at least four hours of overlap with US Eastern time.
About the role
We are looking for a senior QA automation engineer to own test automation for [product name], a [web app / mobile app / platform] used by [audience]. You will design our test strategy, build and maintain automated suites across UI and API layers, and make our CI pipeline a reliable signal for every release. You will work closely with developers, product managers and designers, and help the whole team write better tests. You will join a team of [number] engineers and report to [title].
Responsibilities
- Define the test strategy for the product: what belongs in unit, integration, API, contract and end-to-end tests, and what stays manual or exploratory.
- Build and maintain end-to-end suites in Playwright or Cypress with stable selectors, page or component abstractions and isolated test data.
- Automate mobile flows with Appium, or with Espresso and XCUITest alongside the mobile developers, on real devices and device clouds.
- Write API tests for REST and GraphQL services, and introduce contract tests with Pact where teams depend on each other.
- Integrate suites into CI with GitHub Actions, GitLab CI or Jenkins: parallel shards, retries with reporting, artifacts and release gates.
- Track and fix flaky tests at the root: race conditions, shared state, timing assumptions and unstable environments, with a quarantine process that has an exit.
- Manage test data and environments, including seeded databases, ephemeral preview environments and service mocks.
- Run performance and load tests with k6 or Gatling for critical paths before major releases.
- Add accessibility checks with axe-core and visual regression checks where they catch real issues.
- Report quality signals the team can act on: escaped defects, suite runtime, flake rate and coverage of critical user journeys.
- Review test code in pull requests and coach developers on writing testable features and useful tests.
Requirements
- 5+ years in software testing or development, with at least 3 years writing production test automation in code.
- Strong programming skills in TypeScript, Python or Java, written to the same standard as application code.
- Deep experience with Playwright or Cypress, including network interception, authentication setup, fixtures and parallel runs.
- Experience designing a test strategy and explaining trade-offs between test layers, speed and confidence.
- Hands-on CI/CD experience: running suites in pipelines, sharding, caching and gating deployments on results.
- A track record of diagnosing and eliminating flaky tests rather than adding blanket retries.
- API testing experience with tools such as Playwright's request context, REST Assured, Postman or pytest.
- Working knowledge of SQL, Docker and reading application logs to isolate whether a failure is in the test, the app or the environment.
- Clear written English for bug reports, test plans and release notes.
Nice to have
- Mobile automation with Appium, Detox, Maestro, Espresso or XCUITest on BrowserStack or Sauce Labs.
- Contract testing with Pact or schema-based API testing.
- Performance testing with k6, Gatling or JMeter.
- Testing event-driven systems, queues or data pipelines.
- Experience moving a team from Selenium or Cypress to Playwright.
- Security testing basics such as OWASP ZAP scans in CI.
Tech stack
Playwright with TypeScript, Appium, Pact, k6, axe-core, Docker, Testcontainers, GitHub Actions, BrowserStack, Allure or Playwright reports, Postgres, Jira or Linear for defects. Replace this list with your real stack and the product surfaces you need covered.
What success looks like in 6 months
- A written test strategy exists, and the team uses it to decide where new tests belong.
- The critical user journeys are covered by end-to-end tests that run on every pull request and gate releases.
- The suite's flake rate and runtime have dropped measurably from where they were when you joined.
- Developers write and maintain tests for their own features using patterns you set up, instead of handing testing off.
How to apply and interview process
Send your resume or LinkedIn profile and a short note about a test suite or quality problem you improved. Our process has four steps: a 30-minute intro call, a technical conversation about test strategy on a system you know, a practical exercise or pairing session writing and debugging automated tests, and a final conversation with the team you would join. We aim to give feedback within a few days of each step.
Junior vs mid vs senior QA automation engineer
The jump from mid to senior in QA automation is a jump from writing tests to owning release confidence. Hire for the level of strategy you need.
| Level | Scope | Typical experience | Key skills |
|---|
| Junior | Automating defined test cases in an existing framework, with review | 0-2 years | Basic TypeScript or Python, locators, assertions, clear bug reports, manual test design |
| Mid-level | Building and maintaining suites for a product area, including CI integration | 2-5 years | Playwright or Cypress in depth, API testing, test data setup, debugging flaky tests |
| Senior | Test strategy, framework architecture, release gates and coaching developers | 5+ years | Test pyramid design, CI sharding and reporting, contract and performance testing, quality metrics |
Tips for writing a QA automation engineer job description that attracts senior talent
- Say whether this is strategy or scripts. Senior candidates want ownership of test strategy and release gates. A role that only converts manual test cases into scripts is a mid-level role; title it that way.
- Name your framework, or your migration. "Moving from Selenium to Playwright" is an appealing project. A long list of every test tool ever made signals no one has decided.
- Describe today's pain honestly. A 90-minute suite that fails a third of the time is a great pitch to the right engineer, if you say it plainly. Use your real numbers.
- Explain how QA works with developers. Strong automation engineers avoid teams where QA is a separate gate at the end. Say whether developers write tests and how the two roles share ownership.
- List the surfaces. Web, iOS, Android, APIs and data pipelines each need different tools. Be specific so candidates can judge fit.
- Treat it as an engineering role. Ask for real programming skills and include the person in code review and design discussions. Candidates read that as respect.
- Mention the device and browser matrix. Supporting Safari, older Android versions or embedded webviews changes the job considerably.
Skip the job post: hire a vetted senior QA automation engineer
Writing a good job description is the first step of a hiring cycle that can run for months. If you need senior QA automation capacity sooner, Ryz Labs can match you with senior QA automation engineers from Latin America who join your team, your repos and your standups and work within an hour of US time zones. Only the top 1% of the engineers we interview make it through our vetting, which covers test strategy, automation code quality and CI design.
Our staff augmentation model lets you add one QA automation engineer or several, working on your team, without rewriting your process. Ryz engineers join your team and report to your leads. Talk to us to scope your team. If you are still running your own hiring loop, our QA automation interview questions cover the topics we test for and what strong answers sound like.
FAQ
What should a QA automation engineer job description include?
A job title with seniority, the product surfaces to cover, your current test framework and CI setup, specific responsibilities including who owns test strategy, realistic requirements, your real tech stack, what success looks like after a few months and the interview steps.
Should a QA automation engineer know how to code?
Yes. Modern automation is software engineering: test frameworks, fixtures, CI configuration and debugging race conditions all require real programming skill. Ask for the language your suites use, usually TypeScript, Python or Java, at the level you would expect from a developer.
Playwright or Cypress: which should I ask for?
Ask for the one you use. Playwright has become the common choice for new web suites because of multi-browser support, parallelism and auto-waiting, while many teams still run large Cypress suites. A strong engineer can move between them, so list your framework as preferred rather than mandatory.
Questions we didn't answer? Email info@ryzlabs.com.