HireToolX

Resume example3 years

QA Tester (Manual & Automation) Resume Example & Format

Many QA roles in India still combine manual and automation testing, especially at IT services companies and mid-sized product firms. A tester with around three years of experience is usually expected to write and run test cases independently, automate regression suites with Selenium and a framework such as TestNG, test APIs with Postman or Rest Assured, and manage defects in JIRA.

Recruiters scan QA resumes for the tools and the type of testing, but hiring managers look for evidence of impact: how much of the regression suite you automated, how long a cycle took before and after, how many defects you found and how many escaped to production. Domain knowledge, such as banking, insurance or e-commerce, also matters, because test design depends on understanding the business flow.

The sample below is for a QA engineer with about three years of experience who started in manual testing and gradually took on automation and API testing for a banking application.

Sample QA Tester (Manual & Automation) resume

Fictional candidate. Names, employers, colleges and figures are illustrative; replace every line with your own work.

Divya Example

QA Engineer · Manual & Automation Testing · Selenium, TestNG, Rest Assured · BFSI

  • Noida, Uttar Pradesh
  • divya.example@example.com
  • +91 9XXXX XXXXX
  • linkedin.com/in/divya-example
  • github.com/divya-example

Summary

QA engineer with 3 years of experience in manual and automation testing of web and mobile banking applications. Designs test cases from user stories, automates regression with Selenium WebDriver, Java and TestNG, tests REST APIs with Postman and Rest Assured, and manages defects end to end in JIRA. ISTQB Foundation Level certified.

Experience

QA Engineer

Coho Software Services · Noida

  • Automated 420 of 610 regression test cases for a retail net banking application using Selenium WebDriver, Java, TestNG and Page Object Model.
  • Cut the full regression cycle from 5 days of manual effort to about 8 hours by running the suite in Jenkins on every release candidate.
  • Built a Rest Assured API test suite of 180 tests for account, payee and transfer services, run in the CI pipeline on each merge.
  • Logged 300+ defects in JIRA with clear steps and evidence; production defect leakage for the module stayed under 2% across 4 releases.
  • Validated transaction data with SQL queries on Oracle and wrote test data scripts that cut setup time before each cycle.

Junior QA Engineer

Wingtip Digital Solutions · Noida

  • Wrote and executed 900+ manual test cases for an insurance policy portal covering functional, regression, smoke and UAT support testing.
  • Tested REST APIs with Postman collections and environment variables, catching contract mismatches before frontend integration.
  • Performed cross-browser and mobile responsive testing on Chrome, Firefox, Safari and Android devices.
  • Started the team's first Selenium smoke suite with 40 tests, which ran daily on the staging environment.

Skills

  • Testing: Functional, Regression, Smoke and sanity, Integration, UAT support, Cross-browser, Test case design
  • Automation: Selenium WebDriver, Java, TestNG, Page Object Model, Maven, Cucumber (BDD) basics
  • API testing: Postman, Rest Assured, JSON schema validation, Swagger
  • Tools: JIRA, Zephyr, Jenkins, Git, SQL (Oracle, MySQL), BrowserStack
  • Process: STLC, Defect life cycle, Agile / Scrum, Requirement traceability

Education

B.Tech, Information Technology

Sample Institute of Engineering · Greater Noida · CGPA 7.8 / 10

Certifications

  • ISTQB Certified Tester Foundation Level (CTFL)

What makes this resume work

  • Automation coverage is given as a count out of the total suite, which is more credible than "automated most test cases".
  • Regression time before and after automation shows the business value of the automation work.
  • Manual testing experience is kept and described properly, since most 3-year roles still expect both skills.
  • API testing and SQL validation appear in bullets, showing the candidate tests beyond the UI.
  • Defect leakage is used as a quality outcome, which QA managers recognise and value.
  • The progression from manual tester to automation is visible across the two roles.

QA Tester (Manual & Automation) resume keywords for ATS

Recruiters and applicant tracking systems search for these terms. Use the ones that genuinely match your experience, in your bullets as well as your skills section, and mirror the wording of each job description.

  • QA Engineer
  • Software Testing
  • Manual Testing
  • Automation Testing
  • Selenium WebDriver
  • Java
  • TestNG
  • Page Object Model
  • Cucumber
  • API Testing
  • Postman
  • Rest Assured
  • JIRA
  • Test Case Design
  • Regression Testing
  • Functional Testing
  • Smoke Testing
  • SQL
  • Jenkins
  • CI/CD
  • STLC
  • Defect Tracking
  • Agile
  • ISTQB

QA Tester (Manual & Automation) resume mistakes to avoid

  • Listing every testing type ever named (load, security, accessibility) without having done most of them.
  • Writing "automated test cases" with no count, framework or effect on regression time.
  • Hiding manual testing work to look automation-only. Most mid-level roles want both, and interviewers will ask about test design.
  • Leaving out the domain. Banking, insurance or e-commerce testing experience is often a shortlisting factor.
  • Claiming automation skills without a framework you can explain, such as how your Page Object Model and reporting are structured.

Frequently asked questions

How do I write a resume with both manual and automation testing experience?

Show both clearly. Use your summary to state the split, then write bullets for test design and manual execution alongside automation work with counts and tools. Group skills into testing types, automation, API testing and tools. Show a progression if your role moved toward automation, because that is what many hiring managers want to see at three years.

Which automation tools should a 3-year QA engineer know?

Selenium WebDriver with Java or Python, a test framework such as TestNG, JUnit or PyTest, Maven or Gradle, Git and a CI tool like Jenkins are the common baseline. Postman and Rest Assured cover API testing. Playwright, Cypress and Appium appear in a growing number of listings. List only what you have used and support each tool with a bullet.

Is the ISTQB certification useful for testers in India?

It can help, particularly with IT services companies and clients in regulated domains, because it shows you know standard testing terminology and process. It will not replace hands-on automation skills. Add it to a certifications section and focus the rest of the resume on what you tested, automated and improved.

Should I mention my notice period on my QA resume?

Most of the time, no. Naukri and company application forms ask for notice period separately, and recruiters confirm it on the first call. If you are already serving notice or can join quickly, mention it in your application message, as some testing roles are filled urgently for project ramp-ups. Keep salary details off the resume.

How can a manual tester move into automation testing?

Learn one language and one framework well, usually Java with Selenium and TestNG, then automate a slice of your current regression suite or a public demo application. Put the code on GitHub with a clear README and reporting. On your resume, describe any automation you did at work, even a small smoke suite, with the number of tests and how often it ran.

Make your QA Tester (Manual & Automation) resume

Start from a clean ATS-friendly template, fill in your own experience, then check it against the job description.