02
H
1st Edition · Premium Guide
Automation Frameworks
Selenium, Cypress, Playwright, and what each one means.
Read the tool stack, and you read the candidate.
This guide is the exclusive intellectual property of Hofler Enterprises LLC, protected under US and international copyright law.
This guide is for the recruiter who places QA engineers and is tired of screening for a role nobody ever explained in plain terms. You do not need to code. You need to understand the work well enough to source, screen, and place with confidence.
Every page here comes from the other side of the interview. It is what a working senior QA engineer would tell a recruiter he trusted.
Read it once, start to finish. Then keep it open beside you on your next QA screen and use the sections as a reference. The questions at the end of each section are meant to be used, not admired.
Each framework gets the same treatment: what it is, who uses it, and what it signals on a resume.
Why frameworks are not interchangeable · the 2026 landscape at a glance
Selenium loyalists insist Cypress can’t handle real complexity, Cypress fans call Selenium dead, and Playwright evangelists say both camps are behind — none of that noise tells you which candidate actually fits which company. You’ll learn why “automation experience” on a resume is a starting point, not a hiring signal, and get the 2026 market snapshot (Playwright ~45%, Selenium ~22%, Cypress ~14%). The section closes with the guide’s core promise: by the end, “Selenium, TestNG, Maven” reads as a Java enterprise engineer and “Cypress, TypeScript” reads as a modern JavaScript-team engineer.
The plain-English version · why the tool choice matters
Before the tool-by-tool breakdown, this section gives you the ninety-second plain-English version of what an automation framework actually is — the toolkit that turns manual clicking into automatic checking. You’ll learn the five slots every stack fills — the automation tool, the language, the test runner, the build tool, and the reporting layer — on both a Java enterprise example and its JavaScript equivalent. It closes on why the choice isn’t just preference: a team lives with a framework for years.
Selenium + Java + TestNG + Maven + ExtentReports · the enterprise ecosystem
Selenium is the two-decade veteran that still runs the test infrastructure of enterprise, banking, insurance, and government shops — and it almost never shows up alone on a strong resume. You’ll learn to tell a senior Selenium engineer from someone with one stale credit by reading the supporting cast around it — TestNG or JUnit, Maven or Gradle, ExtentReports, Selenium Grid. The section closes by countering the “Selenium is dead” claim with the actual numbers, plus a green-flag/red-flag test.
JavaScript/TypeScript · browser-native · the modern web favorite
Cypress runs inside the browser instead of driving it from the outside, and that architectural bet is what launched the “testing doesn’t have to be painful” movement among modern web teams. You’ll learn to identify a modern SaaS product company from “Cypress” alone, on both a resume that lists the full JavaScript/TypeScript ecosystem and a bare one-line mention. It closes with the one follow-up question that splits a Cypress contributor from a Cypress architect in under 90 seconds.
Multi-browser · free parallel · the 2026 momentum tool
Playwright overtook Selenium as the most-used automation framework in 2026, and that momentum changes how you have to source — these engineers are already fielding multiple recruiter messages a week. You’ll learn its real technical edge (true multi-browser support, free parallel execution, auto-waiting, Trace Viewer debugging) so you can explain why teams are migrating. It closes with the recruiting-reality table showing why Playwright candidates respond to cold outreach less than Selenium or Cypress candidates do.
Mobile automation · the one nobody else covers
Here’s the fact that trips up recruiters: Cypress and Playwright cannot test native mobile apps at all, so any role touching an actual iOS or Android app needs Appium instead. You’ll learn to recognize when a JD actually requires Appium versus when the client just means “web on a phone,” and to tell a native mobile test engineer from a mobile-browser tester. The section closes with the placement point: catching a “Cypress and Playwright only” mismatch against a mobile JD before you submit saves everyone a wasted interview loop.
TypeScript vs. JavaScript vs. Java — what the language reveals
Java and JavaScript are unrelated languages despite the confusingly similar names — mixing them up is the fastest way to lose credibility with a technical candidate. You’ll learn to read Java, JavaScript, and TypeScript as world-tells (enterprise Selenium shop vs. modern Cypress/Playwright product team vs. an engineering-mature team that adopted TypeScript). It closes by turning that read into advice: when a hiring manager insists on an exact stack match, you can have an informed conversation about how big a leap an adjacent-stack candidate would really be making.
The single most important screening skill in this guide
Two candidates can list the identical framework and be wildly different hires — one built the system from nothing, one wrote a few tests inside someone else’s. You’ll learn to tell a framework builder from a test-writer without reading a line of code, using the resume-keyword decoder and four questions that surface which one you’re talking to. It closes with ready-to-paste sourcing strings for each framework and a table mapping app type in a JD to the implied stack.
Rehearse the screen — 2 reps + sample script
Two rehearsals — who built the framework versus who used it, and hearing a whole stack described back as a portrait — followed by a full mock exchange, closing on the point that correctly naming the profile out loud is what earns trust.
The Framework Cheat Sheet + Screening Questions
The whole volume compressed onto one printable page — the four frameworks, the three-language tell, and the four ownership questions, closing on the guide’s thesis: owners explain why, exposure explains what.
A clear read on the three frameworks you will see most, what each one says about a candidate's experience, and the follow-up questions that confirm it.
A candidate does not just list a tool. They tell you where they came from and how they think. You just have to know how to read it.
No framework is better than another in the abstract. What matters is the fit between the tool, the team, and the problem. A Selenium expert and a Cypress expert are not ranked; they are suited to different rooms.
Your job is not to grade the tool. It is to notice what the tool tells you about the person, and to ask the one question that turns a resume line into a real story.
Selenium is the oldest and most widely known browser automation tool. If a candidate has been in QA for more than a few years, they have almost certainly touched it. That longevity is the first thing it tells you.
Here is what to take from a Selenium line on a resume:
The follow-up that works: "You listed Selenium. What did you build with it, and would you choose it again today?" Their answer tells you whether they used it or just sat near it.
Once you can read a tool stack, a QA resume stops being a keyword search and starts being a story you can follow. The full guide gives you that read for every framework you will meet.
Get this guide →Tell real AI fluency from someone who used ChatGPT twice.
All 7 recruiter guides in one bundle. Source, screen, and place QA talent end to end.