Skip to main content

Playwright vs Selenium vs Cypress: What Employers Ask For in 2026

Based on 1,075 open QA jobs on QA Job Board, November 2026.

Short answer: Selenium is still mentioned in more QA job posts than any other framework, but Playwright is close behind and already leads in automation and SDET roles. Cypress is a clear third. Across 1,046 QA job posts with a full description, Selenium appears in 30.4%, Playwright in 27.0% and Cypress in 18.7%. If you can only learn one framework this year, the data points to Playwright for new automation roles and Selenium for enterprise and Java teams. Below is where each one wins, what it pays and how employers combine them.

How often each framework appears in QA job posts

We search every job description for each framework by name. Here are today's counts from QA Job Board:

Framework Job posts that mention it Share of QA posts with a description
Selenium 318 30.4%
Playwright 282 27.0%
Cypress 196 18.7%

The gap between Selenium and Playwright is getting smaller. On 6 November 2026 Selenium was in 29.2% of posts and Playwright in 25.2%, a difference of 47 posts. Today the difference is 36 posts. Eleven days is a short period, so this is a direction, not a trend line you can bet on. Cypress moved from 17.8% to 18.7% over the same days.

The three frameworks are also not the whole market. In the same-day job file (see Methodology), 56.8% of QA posts mention none of the three. Many of those are manual testing, QA analyst, compliance or test management roles where the framework is not the point. If you are aiming at those jobs, the framework choice matters less than test design, SQL and domain knowledge.

Automation and SDET roles: Playwright leads

The overall numbers mix very different jobs. When we look only at the 247 QA Automation Engineer and SDET posts with a description, the order changes:

Framework Automation and SDET posts Share
Playwright 128 51.8%
Selenium 112 45.3%
Cypress 77 31.2%

More than half of automation and SDET posts now name Playwright. Selenium's overall lead comes from general QA engineer, QA analyst and older enterprise roles, where it has been the default for many years. You can see the current openings on the QA automation engineer jobs page and the SDET jobs page.

By seniority

Seniority is based on job titles. The share of posts that mention each framework:

Level Posts Playwright Selenium Cypress
Junior 37 10.8% 24.3% 8.1%
Mid-level 577 25.3% 30.0% 18.7%
Senior 231 39.4% 36.4% 25.5%
Lead / Manager 161 21.1% 24.2% 11.8%

Senior roles are the only level where Playwright is ahead overall. The junior group is small (37 posts), so treat those percentages with care, but they suggest that entry-level posts still name Selenium more often. That fits a common pattern: companies with large, older Selenium suites hire juniors to maintain them, while teams building new frameworks hire senior engineers and often pick Playwright.

Which languages go with which framework

The language you already know is a good guide to which framework to learn first. Share of posts for each framework that also mention a language:

Language Playwright posts Selenium posts Cypress posts
JavaScript 45.1% 36.1% 49.7%
TypeScript 44.4% 20.7% 37.6%
Python 39.3% 37.4% 37.0%
Java 26.5% 41.6% 30.7%
C# / .NET 13.5% 13.8% 10.6%

Java is the language most often found with Selenium (41.6%), which matches what you see in banks, insurance and large enterprise teams. TypeScript is twice as common in Playwright posts as in Selenium posts. Cypress is the most JavaScript-heavy of the three, which makes sense because it only runs tests in JavaScript or TypeScript. Python is spread evenly across all three, at 37–39%. Across all QA jobs, Python is the most requested language overall, in 25.6% of posts.

Do employers want one framework or several?

Usually several. Of the posts that mention at least one of the three frameworks, many name two or all three, often written as "Playwright, Cypress or Selenium". In the same-day file:

  • 160 posts mention both Playwright and Selenium.
  • 146 posts mention both Playwright and Cypress.
  • 110 posts mention all three.

Cypress almost never appears alone. Only 7.9% of Cypress posts mention neither Playwright nor Selenium. For Playwright that figure is 28.7% and for Selenium 38.4%. In practice this means Cypress is rarely a hard requirement; employers list it as one acceptable option. Selenium-only posts are the most common single-framework posts, usually in Java teams. If you want to see how these frameworks rank against the rest of the QA tool stack, read the most in-demand QA automation tools in 2026.

What comes with each framework

The other skills in these posts say a lot about the teams behind them:

Skill Playwright posts Selenium posts Cypress posts
Postman 41.5% 43.6% 50.8%
GitHub Actions 32.4% 17.4% 29.6%
Jenkins 22.9% 27.9% 28.6%
Cucumber / BDD 10.2% 19.7% 9.5%
AI / LLM testing 27.6% 16.4% 25.4%

Playwright teams lean towards GitHub Actions and products with AI features. Selenium teams are almost twice as likely to use Cucumber or BDD and more likely to run Jenkins. Cypress posts ask for API testing with Postman most often, in about half of them. The practical advice is the same for all three: a framework without API testing and a CI pipeline is not what these teams are hiring for.

Salary: the framework does not change pay much

Only some posts publish pay. Across all QA jobs, 17.5% include a salary, which gives 188 salaries with a median of $110,000 a year. Split by framework, the samples are small:

Posts that mention Salaries 25th percentile Median 75th percentile
Selenium 51 $84,000 $108,000 $120,000
Playwright 41 $89,000 $105,000 $128,000
Cypress 30 $92,000 $102,000 $120,000

The medians are within $6,000 of each other, and with 30 to 51 salaries per group that difference is not meaningful. The role matters far more than the tool. SDET posts have a median of $121,000 (16 salaries) and Senior QA Engineer posts $128,000 (32 salaries), compared with $98,000 for general QA Engineer posts. A framework helps you get into automation and SDET roles; those roles are where the higher pay is. Our QA engineer salary report has the full breakdown.

Remote work is the norm for all three

Across all QA jobs we track, 91.8% are remote. For the three frameworks the share is 96–97%. Playwright posts come from 236 different companies, Selenium posts from 242 and Cypress posts from 171, so no single employer shapes these numbers. The United States is the most common country restriction for all three, followed by India and Canada. You can filter by location on the remote QA jobs page, and see which employers hire testers most often on our daily list of the best software companies to work for.

Which one should you learn?

  1. You are starting out: learn Playwright with TypeScript. It is the framework most often requested in new automation roles, and the skills (locators, fixtures, API calls, CI) transfer to Cypress easily. Keep an eye on junior posts, which still mention Selenium more often.
  2. You work in Java: stay strong in Selenium, then add Playwright for Java. Many Java teams are planning or running a migration, and having done one is a good interview story.
  3. You already know Cypress: you are well placed for JavaScript-heavy front-end teams. Add Playwright, because 77.2% of Cypress posts also list it.
  4. Whichever you pick: add API testing and a GitHub Actions or Jenkins pipeline to your project. Then prepare for questions on waits, flaky tests and framework design with our QA automation interview questions.

To compare the current openings yourself, browse Playwright jobs, Selenium jobs and Cypress jobs. For a deeper look at one framework, read Playwright jobs in 2026.

Frequently asked questions

Is Playwright replacing Selenium?

Not yet, but it is getting close. Selenium is mentioned in 30.4% of QA job posts on QA Job Board and Playwright in 27.0%, and in automation and SDET roles Playwright already leads with 51.8% against 45.3%.

Should I learn Playwright, Selenium or Cypress first?

Playwright is the best first choice for most new automation engineers, because it appears in 51.8% of automation and SDET posts. If you work in Java or apply to large enterprise teams, Selenium is still the safer choice, since 41.6% of Selenium posts mention Java.

Which test automation framework pays the most?

The differences between them are small. Posts that mention Selenium have a median salary of $108,000, Playwright $105,000 and Cypress $102,000, and those groups are too small for the difference to matter. Role and seniority have a much bigger effect.

Is Cypress still in demand in 2026?

Yes, but as a third option. Cypress appears in 18.7% of QA job posts, and only 7.9% of Cypress posts mention neither Playwright nor Selenium, so employers usually accept it alongside the other two.

Where can I find Playwright, Selenium and Cypress jobs?

QA Job Board lists jobs for all three frameworks, updated daily from 1,075 open QA jobs. Start with QA automation engineer jobs, or search directly for Playwright jobs.

Methodology

We analysed 1,075 open QA jobs collected by QA Job Board on 17 November 2026; framework shares are based on the 1,046 posts with a full description, and the 6 November figures come from that day's saved dataset. Breakdowns by role, seniority, language, co-skill, country and salary come from the same day's published job file (1,006 posts with a description), using the same keyword matching. Salaries were converted to annual USD, and medians are only shown for groups with at least 5 salaries.

Hiring QA engineers? Post a QA job on QA Job Board and reach testers who work with Playwright, Selenium and Cypress.