trackr
All articlesCV Tips

QA Manual CV in 2026: How to Sound Like an Engineer, Not a Clicker

·5 min read

A junior QA recently asked me why she was not getting interviews despite "two years of experience". I opened her CV. The first three bullets were "Tested web application", "Reported bugs in Jira", "Communicated with developers". None of those are bullets. Those are job descriptions of someone watching the screen.

What changed for QA Manual hiring in 2026

The QA Manual role survived the "everyone goes automation" panic of 2023-2024 because exploratory testing, edge-case hunting, and UX-level bug detection still cannot be automated cheaply. But the bar for what counts as Manual went up. A 2026 QA Manual is expected to read API responses in Postman, write basic SQL, and diff staging vs production. Pure click-through testers compete with offshore at $300/month. Specialists with concrete metrics earn 3-5x more.

The bullet that signals you are an engineer

"Found and documented 320+ bugs in a year, 47 of them critical that blocked release until fixed." This is the bullet that flips you from clicker to engineer in the recruiter's head. Why: it shows volume, severity discrimination, and business impact ("blocked release"). Compare with "found bugs" - the same fact, zero signal.

What to add to skills this year

  • Postman / Bruno for API testing - even at "comfortable" level
  • Basic SQL: SELECT, JOIN, WHERE, GROUP BY (you do not need windows yet)
  • Chrome DevTools network and performance panels
  • One automation tool exposure (Playwright or Cypress, even read-only)
  • Test design techniques by name (boundary, equivalence, decision table)

ATS gotcha for QA CVs

QA candidates love writing "Quality Assurance Engineer" while every recruiter searches for "QA Engineer". The two-word vs three-word mismatch makes ATS keyword scoring miss your CV. Use "QA Engineer" explicitly in the title line, then spell it out somewhere in the body for the human reader.

The interview question that catches everyone

"How would you test a login form?" The trap: candidates list happy-path cases first - valid email, valid password, click. Strong QA candidates start with boundary and negative cases: empty fields, SQL injection in email, password 1000 chars long, paste with newlines. Leading with edge cases signals you think like an attacker, not a user. That is the entire job.

Organise your job search with Trackr

Track applications, analyse your CV with AI, and prepare for interviews - free.

Get started free
📄
See how your CV scores
Get a real ATS score + line-by-line suggestions - free.
Analyze my CV free