QA Automation: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

The Junior market is large — banks + outsourcing shops regularly hire after Manual QA or courses. The Junior → Middle jump — mastering one framework end-to-end + CI/CD + reporting. Senior owns test-framework architecture + mentoring. Career flow: Manual QA → Junior Automation → Middle → Senior → either Test Automation Lead, SDET (deeper programming), or QA Architect.

Top 5: ci/cd, java, playwright, selenium, agile. Python — the dominant language in CIS (pytest + Selenium/Playwright). Java — the standard in banks/EPAM (Selenium + JUnit 5/TestNG + Allure). JavaScript/TypeScript — frontend teams (Playwright + Cypress). Web frameworks: Selenium 4 (legacy industrial), Playwright (modern, fastest growing — learn first in 2026), Cypress (SPA-specific). API testing: Postman + Newman (CI integration), RestAssured (Java), Karate (DSL-based), requests+httpx+pytest (Python). Mobile: Appium. Reporting: Allure (CIS standard), ReportPortal. Test management: TestRail, Zephyr, qase.io. Knowledge of Docker + Kubernetes (test environments) — Senior must. BDD (Cucumber/Behave/Gherkin) — bonus for enterprise.

Playwright (Microsoft, 2020+) — modern winner. Multi-browser (Chrome/Firefox/Safari), auto-wait + auto-retry, parallel execution out of the box, network interception, mobile emulation, codegen tool. Growing trend: 2026 — the year of Playwright. Languages: TS/JS (primary), Python,.NET, Java. Senior Playwright + CI/CD — premium skill +10-15% over Selenium. Selenium 4 — the industrial standard, large market of legacy projects (banks, enterprise). Any language (Python/Java/JS/C#/Ruby). Downsides: flaky tests without proper waiters, slower than Playwright. Cypress — frontend SPA teams (React/Vue/Angular). JS-only. Good DX, time-travel debugger, easy start. Downsides: Chrome/Firefox only (no native Safari), not suitable for multi-tab/cross-origin. Strategy: Playwright first (future-proof), Selenium as an add-on for legacy jobs, Cypress only if you're going into pure frontend QA.

Manual QA — manual testing: test cases against requirements, exploratory testing, bug reports in Jira. Low programming bar (SQL + basic Linux + Postman). Details — Manual QA. QA Automation Engineer (this page) — test automation: writes E2E/UI/API tests on existing frameworks (Selenium/Playwright + pytest/JUnit), maintains CI/CD. Programming at "can solve a kata + read code" level. SDET (Software Development Engineer in Test) — at the intersection of Automation and Backend. Writes TEST FRAMEWORKS (not just tests), optimises performance test stack, builds testing infrastructure. Programming = Backend Middle/Senior level. Details — SDET. Career progression: Manual QA → Automation → SDET in 3-5 years.

Yes, 38% of QA Automation jobs are full-remote or hybrid. Work is cloud-based (Selenium Grid/BrowserStack/Sauce Labs + CI). Russian banks — more often office due to compliance requirements on the test environment. Outsourcing shops — almost always remote. International SaaS — full-remote. Relocant hubs: Poland (Warsaw/Krakow — huge demand for QA Automation among Russian-speakers), Germany, Czechia, Serbia, Georgia, Armenia.

QA Automation — writes TESTS to verify the working product. Focus: verification and bug-hunting. Programming level: "confident middle-skill". Backend/Frontend Developer — writes the PRODUCT. Focus: feature implementation. Programming level: deeper + architecture + performance. Pay: QA Automation Senior is 15-25% below Backend/Frontend Senior on average (but SDET ≈ Backend). Career switch QA Automation → Backend/Frontend is possible in 6-12 months (master the framework + design patterns + DB modelling). Reverse switch Backend → QA Automation — 1-2 months; happens less often.

Roadmap: 1) Testing fundamentals — ISTQB Foundation Level (book + exam), test types, test-design techniques. 2) Python or Java to a confident level — functions, OOP, collections, exception handling. 3) SQL basics + one RDBMS (PostgreSQL). 4) HTTP/REST + Postman — go through a REST API tutorial. 5) Selenium 4 or Playwright — official tutorial + 5-10 auto-tests on an open-source app (e.g. saucedemo). 6) Pytest or JUnit 5 + Allure for reporting. 8) Docker basics — bring up Selenium Grid or a Playwright container. 9) Pet project: end-to-end automation for an open-source web app + API tests + CI/CD pipeline. Courses: Otus "QA Automation", Karpov.Courses, Yandex.Practicum "Test Engineer", JavaRush for the Java stack. Books: "Lessons Learned in Software Testing" Kaner, ISTQB syllabus. Time to Junior Automation — 6-10 months (faster than Backend).

969 active open QA Automation positions — the largest QA segment after Manual QA. Geography: Russia / Poland / Ukraine. The real market is broader than the sample thanks to internal-only positions. Time to close a Senior QA Automation role — 3-6 weeks.

A Senior QA Automation owns the full test-automation cycle. Programming: clean code in Python or Java (OOP, design patterns: Page Object, Factory, Strategy), refactoring, code review. Test framework architecture: designing a reusable test framework, parametrised tests, fixtures, data-driven testing. Selenium 4 or Playwright mastery (auto-wait strategies, multi-tab, network interception, mobile emulation). API testing: REST/GraphQL/gRPC + contract testing (Pact). SQL: advanced queries for test-data setup + verification. CI/CD: pipeline-as-code (Jenkinsfile /.gitlab-ci.yml / GitHub Actions YAML), parallel execution. Containerisation: Docker (test envs), Kubernetes basics. Performance testing: one of JMeter/Gatling/k6 at the level of designing load scenarios. Mobile: Appium basics (bonus). Soft: code review, mentoring Juniors, communication with developers + PM. English for Senior+ must — for outsourcing/EU relocation.