Many software tester resume pages carry a line like "Responsible for regression testing of web and mobile applications". The line may be true, and it is also very hard to find. Here is a made-up example.
Suppose a payments company wants a QA engineer with 3 or more years of experience. The posting asks for API testing, Postman, SQL and risk-based testing. It also says that ISTQB Foundation Level is preferred. A recruiter opens the company's hiring software and searches for "API testing" and "Postman." The tester with the regression line may have done exactly that work for 4 years. But those words are not on the page, so the resume may sit low in the list or not come up at all.
What happens to your resume before anyone reads it
Most large employers collect applications in an applicant tracking system, or ATS. An ATS is the database that stores every resume sent for a job. Jobscan's 2026 ATS usage report (August 20, 2026) found one at 487 of the Fortune 500 companies. Workday was the most common, at over 40% of them.
You may have read that these systems reject most resumes before a person sees them. The evidence for that is thin. Enhancv interviewed 25 US recruiters in September and October 2025. 92% of them said their ATS does not reject resumes on its own because of format or content. Only 2 of the 25 had set up content-based rejection rules, such as a match score or a required skill.
So what does the software do for most applicants? It stores, sorts and searches. An employer can set eligibility rules, such as a required skill, that reject an application automatically, but few of the recruiters Enhancv spoke to had done so. The recruiter can type words into it. In an exact keyword search, a resume without those words may not show up. Jobscan's report cites its own recruiter survey, in which 76.4% said they search and rank by skills taken from the job description. Education, job titles, licenses, certifications and experience came after skills.
When the search returns its list, a person reads the top of it. In a 2018 eye-tracking study, Ladders found the first screen took 7.4 seconds on average. The resumes that did well had clear section headers and bold job titles with bullet points under them. The ones that did badly had long sentences, several columns and too many keywords stuffed in.
Taken together, those findings give your resume two jobs. It has to contain the words the recruiter will search for. And each bullet has to make sense to a person who will give it a few seconds.
Use the posting's words, but only where they are true
A recruiter may search with the posting open, so tailor your resume to its terms. If the posting says "API testing," write "API testing," not "backend validation." If it says "risk-based testing," use that term where it fits your work. Risk-based testing means you use risk to choose what to test, how thoroughly and in what order. You judge each risk by how likely a failure is and how much harm it would cause. It is a term from the ISTQB Foundation Level syllabus.
For tools, write the exact name, such as Postman, Playwright with TypeScript or SQL on PostgreSQL. An exact search for Postman will not match the phrase API tools. And name a certification the way the posting does, with its full title, such as ISTQB Certified Tester Foundation Level (CTFL).
If you push keyword matching too far, a skills section with 40 tools in it reads as a keyword list. The Ladders study found that kind of stuffing in the resumes that did badly. Every word you add should be a word you can explain in an interview, including how you used it and how you would answer follow-up questions. If the posting asks for Cypress and you have never used it, leave it out. A recruiter who finds you through a false keyword will lose interest once you are on the call.
A software tester resume bullet, before and after
Go back to the tester from the payments posting, and take one of their duties as many testers would write it.
- Before: Responsible for testing the refund feature. Performed regression testing and worked with developers to fix bugs.
Regression testing means running tests again after a change, to check that the change did not break something that used to work. The bullet says the tester did that. It does not say what they tested, how or what came of it. It also contains none of the posting's search words. The duty-style line has a reason to exist. Job descriptions are written as lists of duties, and many testers may copy that shape because it feels safe and complete. But a list of duties only tells a recruiter what your job was. It says nothing about what you found or what changed because of your testing.
Here is the same work, rewritten so that it answers those questions.
- After: Did API testing of the refund service in Postman, with 85 tests ranked by risk with the product owner. Found 12 defects before release, including a refund that could post twice. Checked refund records with SQL queries.
The numbers in this example are made up for teaching. Yours have to come from your own work. The rewritten bullet names the test object, the refund service. It names API testing and Postman, which are both in the posting. And it ends on a result the business cares about, which is a defect that was caught before customers saw it.
What if your old job never measured anything? Most testing work still leaves countable traces. How many test cases did you design? How many defects did you report, and how many were fixed before release? Which high-risk area did you cover that nobody had tested before? A defect report or a test management tool will often hold those counts. If a number is a rough figure, write "about 80," and be ready to say how you counted it.
Evidence a hiring manager can check
Once a bullet gets you past the search, a hiring manager may still want proof before spending an hour with you. A link to a small public test project is strong proof, because they can open it and read your test design. We wrote about building one in this post on test automation portfolios.
A clean bug report from a public project is a smaller piece of proof, because it shows how you write. A certification shows that you know the standard testing terms. In the Jobscan survey, though, recruiters ranked certifications after skills and job titles, so list yours below bullets that show the work. If a posting lists ISTQB Foundation Level and you are not sure you are ready, the free CTFL assessment can show you where you stand.
The interview itself is a different stage, and our software testing interview guide covers it. Every number on your resume is a question you may be asked. The interviewer may ask how you chose the 85 tests, or which of the 12 defects was the worst. When you can answer from memory, the bullet supports what you say in the room. When you cannot, the interviewer may start to doubt the rest of the page, including the bullets that were accurate.
Sources
- Jobscan, 2026 ATS Usage Report: Fortune 500 use of applicant tracking systems, August 20, 2026.
- Enhancv, Does ATS reject resumes? Recruiter interviews, November 3, 2025.
- Ladders via PR Newswire, Ladders updates popular recruiter eye-tracking study, November 6, 2018.
- ISTQB, Certified Tester Foundation Level (CTFL) v4.0, accessed October 2, 2026.