QAAnywhere

Remote QA & testing jobs, worldwide.

Guides

Playwright vs Selenium vs Cypress: which one remote QA jobs ask for

By the QAAnywhere team · Published November 8, 2026

The short answer

If you are learning browser automation to get a remote QA job, learn Playwright first and Selenium second. Learn Cypress when a specific job you want asks for it.

That order comes from the listings themselves, not from which tool is newest. At the start of November 2026, Playwright was named in 32 of the 261 remote QA roles on QAAnywhere, Selenium in 28 and Cypress in 17. Two months earlier the same count was 21, 15 and 10 out of 136 roles. All three grew with the market, Playwright stayed in front, and Selenium did not fade away the way many blog posts predict.

The rest of this guide explains why each tool shows up where it does, what employers expect you to know about it, and how to show that knowledge when you apply.

What the listings actually say

Counting tool names is a blunt instrument, so here is what sits behind the numbers, taken from the roles on the board on 8 November 2026 that include a full job description.

  • Playwright roles rarely want Playwright alone. Of the 26 open roles naming Playwright, 15 also named Selenium, and 14 named an API testing tool (Postman or REST Assured). Employers are often in the middle of a migration, or run both: Selenium for an older suite, Playwright for new work.
  • Playwright is language-neutral in practice. Those 26 roles asked for TypeScript or JavaScript (about half), Java (10) and Python (8). If you write tests in Python or Java, you do not need to switch languages to use Playwright.
  • Selenium is still mostly a Java market. Of the 22 roles naming Selenium, 13 asked for Java.
  • Cypress almost never comes alone. Every one of the 10 roles naming Cypress also named another browser tool, most often Selenium or Playwright. Knowing Cypress is a plus; knowing only Cypress narrows your options.
  • CI is assumed. Nearly every Playwright role (25 of 26) mentioned a CI/CD system such as GitHub Actions, GitLab CI or Jenkins. Writing tests that only pass on your laptop is not what these teams are hiring for.

Playwright: what it is good at

Playwright is Microsoft's open-source browser automation library. It drives Chromium, Firefox and WebKit (the engine behind Safari) through one API, and has official bindings for TypeScript/JavaScript, Python, Java and .NET.

The features employers care about:

  • Auto-waiting. Actions wait for an element to be visible, stable and enabled before acting, which removes most of the hand-written waits that make UI suites flaky.
  • Web-first assertions. expect(locator).toHaveText(...) retries until the condition holds or times out.
  • Browser contexts. Each test gets an isolated, incognito-like context, so tests can run in parallel without sharing cookies or storage.
  • Trace viewer. A failed run in CI can save a trace with screenshots, DOM snapshots, network calls and console logs for every step. For a remote team this is a big deal: you can debug a teammate's failure without reproducing it on your machine.
  • API testing in the same runner. The request fixture lets one test call a backend API to set up data, then check the UI.

A small but realistic test in TypeScript:

import { test, expect } from '@playwright/test';

test('a signed-in user can update their display name', async ({ page }) => {
  await page.goto('/settings/profile');
  await page.getByLabel('Display name').fill('Ada Tester');
  await page.getByRole('button', { name: 'Save' }).click();
  await expect(page.getByRole('status')).toHaveText('Profile saved');
});

Notice what is not there: no explicit waits, no CSS selectors tied to the page's markup. Locators by role and label are what interviewers look for, because they survive redesigns and match how a user finds things on the page.

Selenium: why it is still everywhere

Selenium has been the standard for browser automation for well over a decade, and the W3C WebDriver protocol it pioneered is now a web standard that every major browser implements. That history is exactly why it keeps appearing in listings: large companies have years of Selenium suites, Selenium Grid setups and in-house frameworks built on top of it, and they need people to maintain and modernise them.

Things worth knowing if a role names Selenium:

  • Selenium 4 is the baseline. It uses the W3C protocol natively, and Selenium Manager (built in since 4.6) downloads the right browser driver for you. If your knowledge stops at managing chromedriver by hand, refresh it.
  • Explicit waits are your job. Selenium does not auto-wait the way Playwright does. Knowing WebDriverWait with expected conditions, and why Thread.sleep is a code-review smell, is a standard interview question.
  • Framework design matters more than the API. Most Selenium roles are about a framework: page objects, test data handling, reporting, parallel runs on a grid. Be ready to explain how you would structure one.

The same test in Java with Selenium:

driver.get(baseUrl + "/settings/profile");
WebElement name = driver.findElement(By.id("display-name"));
name.clear();
name.sendKeys("Ada Tester");
driver.findElement(By.cssSelector("button[type='submit']")).click();

new WebDriverWait(driver, Duration.ofSeconds(10))
    .until(ExpectedConditions.textToBe(By.cssSelector("[role='status']"), "Profile saved"));

It is longer, and the waiting is explicit, but nothing here is obsolete. A tester who can write both versions, and explain the trade-offs, is exactly who a team mid-migration wants.

Cypress: where it fits

Cypress runs inside the browser, next to the application, which gives it a very good interactive runner: you watch each command execute and can step back through the app's state at every point. Front-end developers like it because it feels like part of the JavaScript toolchain, so it is common in teams where developers write many of the tests themselves.

Its trade-offs are well known and come up in interviews:

  • Tests are written in JavaScript or TypeScript only.
  • Multiple tabs are not supported, and visiting a second origin in one test needs cy.origin().
  • Its command chain is asynchronous but not built on async/await, which trips up people coming from other tools.

None of that makes Cypress a bad choice. It makes it a choice that suits some teams, and a listing that names Cypress usually means the team already made it, often next to a second tool for the cases Cypress handles less well.

Which one to learn first

If you are starting from zero, Playwright with TypeScript is the most efficient path: it is the tool named most often, the language overlaps with Cypress, and its defaults teach good habits (role-based locators, no fixed waits, isolated tests).

If you already know Selenium well, do not throw it away. Add Playwright on top and learn to talk about the difference. Roles that name both tools are common, and "I have migrated a Selenium suite to Playwright" is one of the strongest lines a test automation CV can carry right now.

If you are a front-end developer moving into testing, Cypress or Playwright are both fine starts; pick the one your target companies use.

Whichever you choose, the tool is maybe a third of what these roles assess. The rest is the same across all three:

  1. Test design. What to test at the UI level and what to push down to API or unit tests.
  2. Stability. Diagnosing a flaky test, rather than adding retries until it goes green.
  3. CI. Running the suite on every pull request, in parallel, with useful reports.
  4. API skills. Setting up test data through an API instead of clicking through the UI.

How to show it in an application

Remote hiring leans heavily on written evidence, because nobody watches you work. Three things help more than a list of tool names:

  • A small public repository with a real test suite against a public demo application, running in GitHub Actions, with the trace or report saved as a build artifact. Reviewers open it.
  • One sentence of impact per tool on your CV: "Moved 400 Selenium tests to Playwright; CI run time from 40 to 12 minutes." Numbers you can explain beat adjectives.
  • The job's own words. If a listing says "Playwright with TypeScript", say "Playwright with TypeScript", not "modern automation frameworks". Recruiters screen for the exact terms.

The roles below are open now and name Playwright. Each listing shows where you can work from, so check that before you spend time on an application; the guide on what "remote" means in a QA listing explains how to read it.

Open remote QA roles that use Playwright

  1. Senior QA Engineer, RuntimeUnqork · United States
  2. Quality Assurance EngineerCare Access · USA Remote
  3. Senior QA Automation EngineerProxify AB · Remote
  4. QA Engineer Team LeadSupplyHouse.com · Remote, Remote, India
  5. QA Engineering Team LeadSupplyHouse.com · Remote, Remote, India

More guides