QA Automation CV 2026: Bullets That Show Engineering

A QA Auto with three years of experience sent me his CV last week and asked, "Why are recruiters not calling, my stack is solid". I opened it. The first bullets were "Wrote autotests in Selenium", "Wrote autotests in Cypress", "Wrote autotests in Playwright". Three frameworks, one verb, zero information. A recruiter reading that learns nothing except that you can spell three tool names.

Why QA Auto CVs read identically to each other

The bar for QA Automation went up quietly in 2025-2026. Frameworks became table-stakes, every junior bootcamp ships with Selenium plus Cypress on day one. The CV that wins is no longer the one that lists more tools. It is the one that shows you owned a piece of infrastructure that the team relied on. Most QA Auto CVs still read like a Manual CV with framework names sprinkled on top: same passive verbs, same lack of numbers, same "wrote N tests" energy. That is why they blend.

What separates QA Auto from QA Manual on paper

QA Manual CVs prove you think like an attacker, you find edge cases and document them well. QA Auto CVs need to prove a different thing entirely: that you build systems other engineers depend on. A Manual bullet sounds like "found 47 critical bugs, blocked release until fixed". An Auto bullet sounds like "built the framework that runs on every PR and feeds back in 12 minutes". The center of gravity shifts from finding bugs to owning a piece of CI. If your Auto CV still reads as a bug-finder CV with Selenium glued on, you read as Manual who learned a tool, not as an engineer who builds.

The "wrote N tests" anti-pattern and what to write instead

"Wrote 400+ autotests" is the most common bullet I see and one of the weakest. It tells me you produced volume, nothing about what that volume did for the team. A real engineering bullet has three layers: what you built, what it replaced, what changed because of it. Compare these two: "Wrote 420+ API tests in REST Assured" versus "Wrote 420+ API tests in REST Assured, catching 65% of bugs before they ever reached the frontend release". Same fact. The second one tells the hiring manager you understand where in the funnel your tests fire.

Four bullets that actually signal engineering work

• Built a Playwright + TypeScript framework from scratch, covered 78% of critical flows, cut regression from 3 days to 4 hours
• Reduced flaky tests from 18% to 3% by refactoring locators and stabilising waits across the suite
• Configured parallel execution on Selenium Grid + Docker, cutting full-suite runtime from 95 to 22 minutes
• Migrated legacy Selenium tests to Playwright, shrank the codebase by 35% and halved maintenance time

Notice what these have in common. Every one of them names a specific number, a before-and-after, and something the team actually felt. None of them say "wrote tests". All of them sound like engineering ownership.

How framework lists betray junior vs senior

A junior QA Auto CV lists every framework they ever touched: "Selenium, Cypress, Playwright, Puppeteer, TestCafe, WebdriverIO, Nightwatch". Seven tools, all weighted equally, no signal which one was actually used in production for two years versus a weekend tutorial. A senior CV lists two or three with depth: "Playwright (primary, 2 years), Selenium (legacy migration), Cypress (read-only on a previous project)". The seniority signal is in the qualifier. The recruiter reading the second one knows exactly which framework to ask about in the screening call.

The CI/CD work that recruiters miss

Most QA Auto candidates do real CI/CD work and then leave it out of the CV because "that is not really QA". Wrong. The single bullet that flips you from "writes tests" to "owns the test pipeline" is something like "Integrated autotests into GitLab CI so every PR got feedback in 12 minutes instead of next-day manual checks". That sentence tells hiring teams you understand where your work lives in the developer workflow. Pair it with a second bullet about reporting infrastructure: "Rolled out Allure reports plus a Grafana dashboard, cutting failure-triage time by 40%". Now you sound like a tooling engineer, which is what senior QA Auto roles in 2026 actually are.

Skills section additions for 2026

• Containerised test runs (Docker, sometimes Kubernetes for parallel suites)
• API contract testing (Pact or similar) on top of REST Assured / Postman
• Visual regression tooling (Percy, Applitools, Playwright snapshots)
• Observability for test runs: Allure, ReportPortal, Grafana dashboards
• One programming language at clean-code level, not "syntax familiar"
• A public GitHub with at least one demo framework against a public API

Salary delta between Manual and Auto in 2026

The gap is real and it widened in the last year. Mid-level QA Manual in Ukraine sits around $1,200-2,000/month, mid-level QA Auto sits at $1,800-3,200. In the EU the spread looks like 2,500-3,800 EUR for Manual mid versus 3,800-5,800 EUR for Auto mid. In the US the delta at mid-level is roughly $25-35k per year. The Auto premium is not paid for the framework knowledge itself, it is paid for the leverage. One QA Auto who builds a stable suite frees up two Manual seats. That is the math hiring managers run, and your CV either shows that leverage or it does not.

Common mistakes that get the CV filtered

• Listing seven frameworks with no depth qualifier, reads as bootcamp graduate
• No GitHub link, or a GitHub with one fork and zero original code
• "Wrote 1000+ tests" with no metric on what those tests caught or saved
• No mention of CI, sounds like tests live on your laptop only
• Calling yourself "QA Engineer" in the headline when recruiters search "QA Automation Engineer"
• Zero programming-language depth, listing Java, Python, JS, TS, Kotlin all at once

ATS gotcha specific to QA Auto

Job descriptions for this role use "QA Automation Engineer", "Test Automation Engineer", and "SDET" roughly interchangeably depending on the company. ATS keyword scoring will weakly match a CV that only contains one of those strings. Put all three somewhere in the document: headline as your primary, the other two in a tagline or summary line. Cheap trick, real recall lift.

The interview question that catches QA Auto candidates

"Walk me through how you would stabilise a flaky test." Junior answers: "Add a sleep". Mid answers: "Replace sleep with explicit wait". Senior answers: "First, I check whether the flakiness is in the test or in the system under test. If the test, I look at locator strategy, network conditions, animation timing, and shared state across tests. If the system, I file a ticket because flakiness in tests often hides a real race condition". That last answer signals you treat tests as a diagnostic instrument, not a chore. Hiring managers remember it.