ResumeCrew
Menu
Start free

Resume example · QA Engineer · Fresher

QA Engineer resume for freshers: a sample from India

A QA fresher is read for proof that you can test, not only describe testing: cases written, defects raised and what a developer did with them. One internship or one small automation project, with honest counts, carries the page, and the marks line stays short and easy to find.

Last reviewed
October 2026
Fictional sample
0 to 1 year of experience
Build yours in the chatCheck yours

Summary examples for a fresher

Two ways to open the page. Neither is the summary on the sample resume beside it, so you can see more than one approach.

Summary example 1

Summary
B.Tech Computer Science graduate (2026) who wrote 120 test cases and raised 31 defects in JIRA during a 3-month internship. Works in manual testing, SQL checks and Postman; applying for QA Engineer roles in services and product teams.Leads with the two numbers a tester is judged on, cases written and defects raised. Use it when your internship was mostly manual.

Summary example 2

Summary
Final-year BCA student with a Selenium and Python mini-project that automates 25 form checks on a college portal, plus Postman practice on 20 REST endpoints. Looking for a junior automation tester role.Puts the automation project first and names the language. Fits a candidate with no internship but a repository a recruiter can open.

Bullet rewrites, weak to strong

Each pair shows a line people really write and a stronger version of the same fact. The numbers are illustrations. If you have no number, see resume bullets with numbers when you have none.

  1. Before

    Did manual testing during internship

    After

    Ran 180 manual test cases over 3 sprints on a hospital-appointment web app; logged 27 defects in JIRA and developers accepted 24

    Why

    Cases run, defects logged and defects accepted: three counts a QA lead can ask about. 'Did manual testing' says only that you were present.

  2. Before

    Knows how to write test cases

    After

    Wrote 70 test cases from user stories for a fee-payment module, covering valid, invalid and edge inputs, and traced each one to a requirement

    Why

    Shows the source (user stories), the coverage idea and the traceability. A claim of knowing is not the same as a sheet a reviewer can open.

  3. Before

    Used Selenium in project

    After

    Automated 25 form-validation checks on a college admission portal with Selenium and Python; the suite runs in 5 minutes against 40 by hand

    Why

    Names the target, the tool, the language and the time saved. A GitHub link beside it lets the reader verify the claim in a minute.

  4. Before

    Tested APIs using Postman

    After

    Tested 18 REST endpoints of a food-ordering API in Postman with status and schema assertions, then ran the collection in Newman after each change and caught 5 regressions

    Why

    Count of endpoints, the kind of assertion and a result. The Newman run shows the checks were repeatable, not one-off clicks.

  5. Before

    Maintained bug reports

    After

    Wrote 31 JIRA defects with steps, expected and actual results, severity and a screen recording; only 2 needed a follow-up question from the developer

    Why

    Turns a vague duty into a quality signal: how clear your reports were. Defect writing is a visible sample of how you communicate in a QA role.

  6. Before

    Tested our final-year project

    After

    Planned testing for a 4-member final-year attendance app: 90 test cases, 3 test cycles and a defect log that took open defects from 21 to 0 before the demo

    Why

    Planning, size and a before-and-after. Even a college project reads as real testing when it has cycles and a defect count.

Skills to list, grouped

Group skills into three or four lines and keep only those you could discuss for ten minutes. Each should appear in a bullet, a project or a certificate.

  • Testing: Manual Testing, Test Case Design, Regression Testing, Exploratory Testing
  • Automation: Selenium, TestNG, Java, Maven
  • Tools: JIRA, Postman, MySQL, Git
  • Core: SDLC and STLC, Bug Life Cycle, REST API basics

What recruiters for this role tend to look for

  • Test artefacts a reader can picture: how many cases you wrote or ran, how many defects you raised and which tool they lived in (JIRA, Excel, TestRail).
  • Basics stated plainly: SDLC and STLC, severity versus priority, smoke versus regression. Interviews often start there, so the resume should not contradict them.
  • One runnable automation sample: a GitHub link with a README, a clear folder structure and a run command. A link that opens is usually read as evidence.
  • Marks that clear the screen. Service companies running campus drives often set a minimum percentage or CGPA, so keep it where a parser and a person both find it.
  • Honest tool claims: Selenium on the list should have a project bullet behind it, with the language named.

Mistakes common at this level

  • Listing 'manual testing' and 'automation testing' as skills with no cases, defects or framework behind them.
  • Calling a recorded-and-replayed script an automation project. Say what you coded: the language, the pattern and how many scenarios.
  • Dropping defect numbers because the internship was short. '27 defects logged, 24 accepted' still beats 'responsible for testing'.

Section order on the sample

The sample uses the Fresher First template, A4 (210 by 297 mm), one column, with the sections in this order: Summary, Education, Projects, Skills, Experience, Certifications. The order follows the level: education and projects lead because there is little job history yet.

Questions people ask

Can a fresher get a QA job without automation skills?

Plenty of entry-level QA openings are manual-first, and some teams teach automation after joining. A small Selenium or Postman project still helps, because it shows you can pick up a tool and finish something. Present it the way the B.Tech CSE fresher guide suggests for projects.

Should I put ISTQB on a fresher resume?

Yes, if you hold it: write the full name and the year. It shows you know the vocabulary of testing, though it does not replace a project or an internship. Avoid listing it as 'in progress' unless you have an exam date booked.

How do I write a testing project that was not on a live product?

Test a public demo site or a course application, name it as practice, and keep the numbers real: scenarios automated, defects found, run time. If something cannot be counted, resume bullets without numbers shows how to describe scope instead.

Keep reading

Next step

Build yours in the chat

Answer a few questions, one at a time. The reviewer drafts each line, asks for the numbers it cannot guess and never adds a fact you did not give. Already have a resume? Check it first and see what a parser reads.

Build yours in the chatCheck yours