"Tested software" credits nothing next to naming the specific automation framework (Selenium vs. Cypress vs. Playwright) and the specific pipeline it runs in (Jenkins, GitHub Actions). QA postings filter on the exact tool and the exact test type — regression, API, load — not the general idea of quality assurance. Yoxon's CV builder automates exactly that — it rewrites your bullets around the specific keywords each job posting uses.
These are exact-match terms — not synonyms — that recruiters commonly build screening filters around for this role. If you genuinely have the experience, make sure the specific term appears in your CV, not just a paraphrase of it. Before you spend that time, it's worth confirming the listing is a real, active opening — run it through our free ghost job detector first.
And before you rewrite your resume, it's worth checking how your CV or LinkedIn profile itself reads — run our free Resume Auditor to see your score and get rewrite suggestions.
Example 1
Tested software features and reported bugs to the development team.
Built a Cypress automation suite covering 85% of critical user flows, integrated into GitHub Actions CI/CD, cutting regression-testing time from 2 days to 90 minutes per release.
Example 2
Found and documented issues in the application.
Logged and triaged 300+ bugs in Jira across 6 sprints, writing reproducible test cases that cut the bug-reopen rate from 18% to 5%.
Should I list Selenium if my current experience is mostly Cypress or Playwright?
List whichever frameworks you've genuinely automated tests in — they're scored as separate keywords, and many teams are actively migrating from Selenium to Cypress/Playwright, so naming the newer tools you know can work in your favor rather than needing to pad with Selenium.
How do I keyword a role that was mostly manual QA, not automation?
Don't inflate it — list "Manual QA" and test-case-design terms honestly, and be specific about scale (number of test cases, release cadence, bug-catch rate) rather than implying automation experience you don't have; a follow-up technical question will expose the gap.
Does CI/CD integration matter if I only wrote the tests, not the pipeline itself?
Yes, but frame it accurately — integrating tests into an existing Jenkins/GitHub Actions pipeline is still a real, searchable skill distinct from building the pipeline itself, and most QA postings are looking for exactly that level of CI/CD fluency, not full DevOps ownership.
Applying in a different field? Our Mechanical Engineer CV guide covers the same keyword-matching approach for that role.
More role-specific CV guides