Money-back guarantee
Delivery from 24 h
Free revisions for 14 days

QA tester CV example

In a QA tester's CV, show which products you have tested, which testing methods and tools you used and what you achieved: fewer bugs in the live product, faster releases or time saved for the team.

The example below works for both manual and automation testers. Give the most space to the experience and skills the job ad asks for, and use the ad's terms where they truly describe your work, because recruiters and applicant tracking systems (ATS) search for them.

CV example

Vardenė Pavardenė
QA Engineer · 6 years' experience · manual + automated testing (Playwright, Postman)
Profile

QA engineer in a fintech product team. Built an automated test suite (Playwright) that cut regression testing from 3 days to 4 hours; zero critical bugs in production over the past year.

Work experience
QA Engineer
Paylab, UAB, Vilnius · 2022–present
  • Built 600+ automated end-to-end (E2E) tests (Playwright, TypeScript), cutting regression from 3 days to 4 hours.
  • Added API testing (Postman, Newman) to the CI pipeline: zero critical bugs in production in a year.
  • Wrote the testing strategy for 3 product teams and trained 4 colleagues.
Software Tester
Softera, UAB, Kaunas · 2020–2022
  • Manually tested web and mobile apps (iOS, Android); logged 1,200+ defects in Jira.
  • Wrote test cases from requirements (TestRail), reaching 95% coverage.
Education

Vilnius Gediminas Technical University (VILNIUS TECH): BSc,Information Systems Engineering, 2020

ISTQB Certified Tester Foundation Level (CTFL), 2021

Skills
Manual testingPlaywrightSeleniumPostman / API testingTypeScriptSQLJira / TestRailCI/CD (GitLab)Agile / ScrumLithuanian (native), English (C1)
The example is shortened. In a real CV every section is tailored to your experience.

What to put in a QA tester CV

Quality metrics instead of lists

Replace “tested software” with numbers: how many tests, how long regression takes, how far production bugs fell, what coverage you reached.

Separate manual and automated testing

Job ads differ. If you are aiming at automation, put the programming language and frameworks first; if at manual testing, lead with test cases, exploratory testing and domain knowledge.

ISTQB: yes, but not instead of experience

The certificate helps you get through ATS screening and is useful for junior candidates. At senior level, the products you have tested and your results matter more.

Domain knowledge

Fintech, e-commerce, healthcare: name the sectors you have tested in. Companies look for people who understand the risks of their business.

Most common mistakes

  • The number of defects found presented as the only achievement. A manager wants to see fewer bugs, not more.
  • A tool list that does not match the keywords in the ad (you write “Cypress” when the ad asks for “Playwright”: list both if you genuinely know both).
  • Not a word about process: Agile, CI/CD, working with developers.

Frequently asked questions

Can I work as a tester without programming skills?

Yes. Manual testing roles are still common, especially in product companies. But even basic SQL and API testing skills widen your options considerably.

How do I move from manual to automated testing?

Show the first steps in your CV: an automated test suite in a personal project (on GitHub), courses, and the part of your current work you have already automated. Employers value the direction you are heading in.

What should I write if I am at the start of my career?

Completed courses, ISTQB, testing projects (even study ones, with a link) and internships. Describe them with the same structure as a job.

More examples