Software Tester Resume Examples & Writing Guide
A software tester resume has to prove you find real defects and can prove it with numbers. Show the products you tested, test case and defect counts, your escaped-defect or regression figures, and the tools you actually use: Jira, TestRail, Postman, Selenium or Playwright, SQL and a CI pipeline.
Software tester resume example (manual plus automation)
A fictional resume for a tester with eight years of experience who does both manual and automated testing. That mix is what most US job postings ask for now, even when the title says manual tester or QA analyst. Swap the products, tools and numbers for yours.
Elena V. Sarkis (fictional example)
Software Test Engineer | Manual and Automation QA
Austin, TX · (512) 555-0119 | e.sarkis@example.com | github.com/example-qa | ISTQB CTFL
Summary
Software tester with 8 years across payments and healthcare software, working in two-week sprints on products released 24 times a year. Cut a 9-hour manual regression pass to 55 minutes with a Playwright suite, and held escaped defects to 0.8 per release across 2025. ISTQB Foundation, Agile Tester and Advanced Test Analyst certified.
Experience
Software Test Engineer · Northwind Payments (B2B payments platform)
Apr 2022 - Present
- Own testing for the merchant onboarding and settlement services: 1,400 test cases in TestRail, 24 releases a year, and an escaped defect rate held at 0.8 per release through 2025.
- Built a Playwright regression suite of 310 tests covering the 18 highest-risk user journeys, replacing a 9-hour manual pass with a 55-minute run in GitHub Actions.
- Test 40 to 60 REST endpoints per release in Postman and Newman, including negative and boundary cases on amount, currency and idempotency key handling.
- Logged 340 defects in Jira in 2025 with reproduction steps, logs and screenshots; 91% were accepted without a request for more information.
- Found a settlement rounding defect in pre-production that would have mis-posted about $27,000 a month across 1,200 merchant accounts.
QA Analyst (Manual Testing) · Belmont Health Systems (clinical scheduling software)
Sep 2019 - Mar 2022
- Wrote and executed 900+ manual test cases for a scheduling module used by 60 clinics, covering functional, regression, cross-browser and accessibility checks.
- Ran SQL queries against the staging database to verify appointment and audit records after each release, catching 22 data integrity defects in two years.
- Led user acceptance testing sessions with 14 clinic staff across 6 releases and turned their findings into 80 prioritized Jira tickets.
- Cut the sprint regression cycle from 4 days to 2.5 by reorganizing the suite by risk and retiring 130 duplicate test cases.
Junior QA Tester · Loop Retail Software (point of sale vendor)
Jul 2018 - Aug 2019
- Executed 250 test cases per release cycle on a point of sale app across 9 device and OS combinations using BrowserStack.
- Reported 210 defects in a year and verified 180 fixes, with a defect rejection rate under 8%.
- Wrote the first smoke test checklist for release day, which cut post-release hotfixes from 4 per quarter to 1.
Education
Bachelor of Science, Information Systems
Texas Gulf State University, 2018
Certifications
- ISTQB Certified Tester Foundation Level (CTFL), 2019
- ISTQB Certified Tester Foundation Level Agile Tester extension, 2021
- ISTQB Advanced Level Test Analyst, 2024
- AWS Certified Cloud Practitioner, 2023
Skills
What a QA lead checks first
The person reading your resume has a backlog and a release date. They are asking whether you can pick up a product area and start finding things in week two. Four signals answer that.
- What you tested, not just that you tested. Payments, EHR, a mobile game and a warehouse system need different instincts. Name the domain and the users.
- Numbers that only a real tester has: test case counts, defects logged and accepted, defect rejection rate, escaped defects per release, regression cycle length.
- Whether you can automate at all. Most manual tester postings now expect some Selenium, Playwright, Cypress or Postman scripting. Say honestly what you can build alone.
- How you think about risk. A tester who says which 18 journeys mattered most is more valuable than one who ran 900 cases with no priority.
“Every resume says "strong knowledge of SDLC and STLC". Nobody cares. Tell me the defect you found that saved the company money, how many cases you own, and what your escaped defect number was. Three numbers and I will book the call.”
Software tester resume summary examples (fresher to senior)
Three or four lines. Domain, years, one automation fact, one quality number. Use an objective only as a fresher or career changer, where you need to explain a move rather than summarize a record.
Information systems graduate with ISTQB Foundation certification and a 40-hour manual testing bootcamp, plus a personal portfolio of 120 written test cases and 35 logged defects against three open-source web apps. Looking for a junior QA role where manual testing is the starting point and automation is the goal.
QA analyst with 3 years testing a clinical scheduling product used by 60 clinics. Owns 900 manual test cases, verifies release data with SQL, and cut the sprint regression cycle from 4 days to 2.5 by retiring 130 duplicate cases. ISTQB Foundation certified.
Software test engineer with 6 years in payments, running 1,400 test cases across 24 releases a year and maintaining a 310-test Playwright suite that replaced a 9-hour manual regression pass with a 55-minute CI run.
Senior test engineer who owns the quality strategy for two payment services: risk-based test planning, a Playwright and Postman suite in GitHub Actions, and an escaped defect rate held at 0.8 per release. Mentors 3 testers and runs the release go or no-go review.
Former tier-2 support specialist who spent 4 years reproducing customer bugs on a retail platform, filing 600+ tickets with logs and reproduction steps. Now ISTQB Foundation certified and looking for a manual QA role where reproduction discipline is the core skill.
Testing duties on a resume: weak vs. strong bullets
The duties are the same for every tester on earth. What differs is the product, the volume and the outcome. Keep the duty, add all three.
| Weak (generic duty) | Strong (specific and countable) |
|---|---|
| Involved in manual testing of web applications. | Owned 1,400 test cases in TestRail for merchant onboarding and settlement across 24 releases a year, with escaped defects held at 0.8 per release. |
| Wrote test cases based on requirements. | Wrote 900 test cases for a clinical scheduling module used by 60 clinics, covering functional, regression, cross-browser and WCAG 2.1 AA accessibility checks. |
| Logged and tracked defects in Jira. | Logged 340 Jira defects in 2025 with reproduction steps, logs and screenshots; 91% were accepted with no request for more information. |
| Performed regression testing. | Cut a 9-hour manual regression pass to a 55-minute CI run by building a 310-test Playwright suite over the 18 highest-risk journeys. |
| Tested APIs using Postman. | Tested 40 to 60 REST endpoints per release in Postman and Newman, including negative cases on amount, currency and idempotency key handling. |
| Performed database testing. | Verified appointment and audit records with SQL after every release, catching 22 data integrity defects in two years. |
| Participated in UAT. | Ran user acceptance sessions with 14 clinic staff across 6 releases and converted their findings into 80 prioritized Jira tickets. |
| Worked closely with developers. | Found a settlement rounding defect in pre-production that would have mis-posted about $27,000 a month across 1,200 merchant accounts. |
If you cannot get exact figures from a past employer, estimate from what you remember: cases per sprint times sprints per year. Approximate honest numbers are far better than none.
Start with an example, finish in minutes.
No sign-up to start. Download works. One-time $12 for a clean PDF, no subscription.
Skills to put on a software tester resume
Group them, and be honest about level. A lead will ask you to write a locator or a SQL join in the interview, so do not list what you cannot do under mild pressure.
- Test design and technique: equivalence partitioning, boundary value analysis, decision tables, state transition, exploratory charters, risk-based prioritization
- Test types: functional, regression, integration, smoke, sanity, cross-browser, mobile, accessibility, basic performance and security checks
- Automation: Playwright, Selenium WebDriver, Cypress, Appium; a language to write it in (JavaScript or TypeScript, Python, Java, C#)
- API and data: Postman, Newman, REST Assured, SQL, JSON and XML payloads
- Performance: JMeter, k6 for load and soak runs
- Tooling: Jira, TestRail, Xray, Zephyr, Azure DevOps, Git, Jenkins, GitHub Actions, BrowserStack or Sauce Labs, Chrome DevTools, Charles Proxy
Two habits are worth stating because they separate testers who get promoted from testers who do not: writing a bug report a developer can reproduce on the first try, and saying out loud in a release meeting that something is not ready. Show them through a result, not as an adjective.
Software tester resume for a fresher or with no experience
This is the most searched version of this page for a reason: QA is one of the few software roles you can enter without a computer science degree. The problem is that fresher resumes all look identical. Build proof instead of listing keywords.
- 1Test something real and document it. Pick two or three open-source or free web apps, write 40 test cases each in a public spreadsheet or TestRail trial, and log the defects you find with steps and screenshots.
- 2Publish it. A GitHub repository with your test plan, test cases, bug reports and a small Playwright or Selenium script is the single strongest thing on a fresher QA resume.
- 3Take ISTQB Foundation Level. It is the accepted entry credential in most of the world and it costs less than a month of a bootcamp.
- 4Learn just enough SQL and one automation tool. Two weeks of SELECT, JOIN and GROUP BY, plus ten Playwright tests, puts you ahead of most applicants.
- 5Write the experience section around projects, internships and the portfolio work, in that order. Put education below it, not above.
- 6Keep it to one page and cut every line that any other fresher could have written.
Wrote and executed 120 manual test cases against three open-source web apps, logged 35 defects with reproduction steps and console logs, and published the full test plan and bug reports on GitHub.
Built 25 Playwright tests covering login, search and checkout flows on a demo e-commerce site, running them in GitHub Actions on every push with an Allure report.
Executed 180 regression cases per release during a 12-week QA internship on a point of sale app, verified 60 fixes, and reported 40 defects with a rejection rate under 10%.
Reproduced and documented 600+ customer-reported bugs over 4 years in tier-2 support, escalating with logs, environment details and exact reproduction steps.
Certifications and education for testers
No certification is legally required, and no employer will hire on a certificate alone. But a credential does get a fresher resume read, and one Advanced Level certification separates you at the senior end. Only these are worth space.
- ISTQB Certified Tester Foundation Level (CTFL). The standard entry credential, administered in the US by ASTQB. Put the year on it.
- ISTQB Agile Tester extension, useful if you work in sprints, which is nearly everyone.
- ISTQB Advanced Level: Test Analyst, Technical Test Analyst or Test Manager, depending on where you are heading.
- Certified Software Tester (CSTE) from QAI, still recognized by some US enterprises and government contractors.
- A cloud fundamentals certificate (AWS Cloud Practitioner, Azure Fundamentals) if you test cloud-hosted products, because it helps you read the infrastructure your bugs live in.
- Degrees: computer science, information systems and engineering are common, but many strong testers come from support, biology, accounting or teaching. If your degree is unrelated, keep it to one line and let the portfolio carry the weight.
Format, length and keywords to mirror
- One page up to about five years, two pages after that. Testers with 7 to 10 years sometimes run three; do not.
- Order: name with certification and GitHub link, summary, experience, skills grouped, certifications, education.
- PDF unless the posting asks for Word. Single column, no tables, no skill rating bars. Rating bars tell a reader nothing and confuse parsers.
- No photo, no date of birth, no marital status on a US resume. If you are applying from India, the Gulf or Europe, strip those fields for US applications.
- Add a GitHub or portfolio link if you have automation code or published test artifacts. Make sure the repository is not empty before you link it.
Mirror the posting's vocabulary inside your bullets rather than in a keyword block. The terms that carry weight in QA postings:
- Title variants: software tester, QA analyst, QA engineer, test engineer, SDET, test analyst, manual tester.
- Tool names exactly as written in the posting: Playwright, Selenium, Cypress, Postman, TestRail, Xray, Jira, Azure DevOps, JMeter.
- Test type words: regression, integration, smoke, exploratory, API testing, cross-browser, accessibility, performance.
- Process words: sprint, backlog refinement, acceptance criteria, definition of done, shift-left, CI pipeline.
- Metric words: escaped defects, defect density, defect rejection rate, test coverage, regression cycle time.
Frequently asked questions
How do I write a software tester resume?
Open with a four-line summary naming your domain, your years, one automation fact and one quality number. Then give each job three to five bullets with counts: test cases owned, defects logged and accepted, escaped defects per release, regression cycle time. Group your tools by category, list ISTQB with the year, and keep it to one or two pages.
How do I write a software tester resume for a fresher with no experience?
Build proof before you apply. Write 40 test cases each against two or three real web apps, log the defects properly, publish the test plan and bug reports on GitHub, and add ten Playwright or Selenium tests. Take ISTQB Foundation Level. Then structure the resume around those projects, with education below them.
What skills are required for a software tester?
Test design techniques (boundary value, equivalence partitioning, risk-based prioritization), manual functional and regression testing, API testing in Postman, SQL for data checks, one UI automation framework such as Playwright or Selenium, and a test management tool such as TestRail or Xray. Reading logs and writing reproducible bug reports matter as much as the tools.
Should a manual tester put automation on a resume?
Yes, at whatever level is honest. Most US manual QA postings now list some automation or API scripting. Even "25 Playwright tests running in GitHub Actions" from a personal project gets you past a filter that a purely manual resume will not. Never claim a framework you cannot demonstrate in an interview.
What should a software tester resume objective say?
Use one only as a fresher or a career changer. Say your credential, your portfolio evidence and the role you want. For example: "ISTQB Foundation certified with 120 published test cases and 35 documented defects against open-source apps, seeking a junior manual QA role with an automation path." Skip anything about seeking growth.
How long should a software tester resume be?
One page up to about five years of experience, two pages beyond that. Testers with long tool lists often stretch to three pages, which weakens the document. Cut the tool inventory, keep the numbers, and describe older jobs in one or two lines each.
Ready to write yours?
The builder suggests a summary from your own experience, then checks it against the job posting.
How this page was made: a first draft was written with AI assistance from cvplex's example library, then edited and fact-checked by the cvplex Careers Team. Examples are fictional composites; numbers are illustrative. Report an error via the editorial policy page.