QA interview questions for freshers

A fresher interview has three jobs: check that you know the basics, check that you think like a tester, and check that you are someone a team can teach. You do not need to know everything. You need to answer clearly and say "I have not used that yet, but here is how I would find out" when you do not know.

The basics they will almost certainly ask

Prepare a two-sentence answer for each of these. The details are on the manual testing questions page.

• What is software testing and why is it needed?
• Difference between QA, QC and testing.
• What is the STLC? What is the bug life cycle?
• Difference between severity and priority (with examples).
• Smoke vs sanity, regression vs retesting (smoke vs sanity).
• Test case vs test scenario vs test plan.
• Black box, white box and grey box testing.
• What are boundary value analysis and equivalence partitioning?
• What is a test case for a pen, a lift or a login page? (login page)

Questions that show how you think

"Tell me about yourself."

Keep it to 40 seconds: your degree, why you chose testing, one thing you built or practised, and what you want next. Do not read your resume aloud. Example: "I studied computer science, enjoyed finding why things break more than building them, and spent three months testing an open-source app. I wrote 60 test cases and found 14 bugs, and I am learning Selenium with Java. I want a team where I can learn automation."

"Why do you want to be a tester?"

Avoid "I could not get a developer job". Give a real reason: you like breaking things, you care about users, you enjoy finding patterns in failures. Then back it up with something you did.

"You have no experience. Why should we hire you?"

Point at evidence. A fresher with a small GitHub project, a written test plan and a bug list is ahead of one with only certificates. The portfolio project kit is built for exactly this, and the buggy app is free to start with.

"How would you test a ballpoint pen?" (or a lift, a vending machine, a water bottle)

They do not care about pens. They want structure. Say: "First I would ask what the pen is for and who uses it. Then functional: writes, ink flow, clicking mechanism. Usability: grip, comfort. Durability: drop it, leave it in a hot bag. Performance: how many metres it writes. Safety: ink is non-toxic. Compatibility: refill fits." Categories first, examples second.

"What do you do if a developer rejects your bug?"

Re-check the requirement and your steps, add evidence (a screen recording), talk to them directly, and if there is still disagreement bring in the product owner. Stay calm and about the product.

Tools questions at fresher level

• Have you used Jira or any bug tracker? Say what you filed and how you described it. A free account and ten practice bugs are enough to answer honestly.
• Have you written test cases in Excel or a test management tool? Use the test case template.
• Any automation? If you know a little Selenium or Playwright, say exactly what you can do (open a page, fill a form, assert a title). If you know none, say you are learning and show what you have done so far.
• Basic SQL: select, where, joins, group by. See SQL for testers.
• Basic Java or Python: strings, loops, collections (Java for testers).

Twenty more questions freshers get, with short answers

Say these in one or two sentences, then add an example if you can.

1. What is a bug, a defect, an error and a failure?

An error is a human mistake (a wrong line of code). A defect or bug is the flaw that mistake leaves in the software. A failure is what happens when that flaw is triggered and the software behaves wrongly. Teams often use bug and defect to mean the same thing.

2. What are the levels of testing?

Unit (a function or class, by developers), integration (parts working together), system (the whole product against requirements) and acceptance (the business confirms it meets needs).

3. What is the difference between functional and non-functional testing?

Functional testing checks what the system does (login works, the total is right). Non-functional testing checks how well: performance, security, usability, reliability, compatibility.

4. What is the difference between a test case and a test script?

A test case is the design: steps, data and expected result, usually written for people. A test script is code that runs the steps automatically.

5. What is a test suite?

A collection of test cases grouped for a purpose, such as a smoke suite or a regression suite.

6. What is the bug life cycle in one line?

New, assigned, fixed, retested, then closed if it passes or reopened if it does not; with side paths for rejected, duplicate and deferred.

7. What are the severity levels and one example of each?

Critical (the app crashes or money is wrong), major (a main feature does not work), minor (a feature works with a problem), trivial (a cosmetic issue such as a misaligned icon).

8. What is regression testing and why is it automated?

Re-testing existing features after a change to make sure nothing broke. It repeats the same checks every release, so automation saves time and removes boredom errors.

9. What is a test plan, and who writes it?

A document describing scope, approach, resources, schedule, risks and entry and exit criteria. A test lead or senior tester usually writes it; a tester should know how to read one.

10. What is a traceability matrix?

A table linking each requirement to its test cases (and defects), so you can see what is not covered.

11. What is a build, a release and a patch?

A build is a version of the software made for testing. A release is a version delivered to users. A patch is a small update that fixes specific problems.

12. What are verification and validation, in a sentence each?

Verification: are we building it right (against the specification, by reviews). Validation: are we building the right thing (does it meet user needs, by running it).

13. What is a test environment?

The hardware, software, data and configuration where tests run. A test environment that differs from production can hide bugs or create false ones.

14. What do you do when you cannot reproduce a bug?

Check the steps, data, build and browser; look for timing and data dependencies; ask the reporter for a recording or logs; try again in the same environment; and report how often it happens. An intermittent bug is still a bug.

15. Which testing tools have you used, and for what?

Name only what you have used: a bug tracker (Jira), a spreadsheet or test management tool for cases, Postman for APIs, browser DevTools for inspecting requests and elements, and the automation tool you are learning. Specific beats a long list.

16. What is API testing and why do testers do it?

Sending requests directly to a service and checking the responses, without the user interface. It is faster, more stable and finds problems early. See API testing questions.

17. What is SQL used for in testing?

Checking that data was saved correctly after an action, setting up and cleaning test data, and investigating defects. See SQL for testers.

18. What is Agile and what is a sprint?

Agile means delivering software in small steps with frequent feedback. A sprint is a short, fixed period (usually one to three weeks) in which the team plans, builds and tests a small set of features.

19. What is the difference between a bug and a change request?

A bug is behaviour that does not match the agreed requirement. A change request asks for new or different behaviour. If the requirement was missing or unclear, discuss it with the product owner before labelling it either.

20. Where do you see yourself in three years?

Give a direction, not a title: "stronger in automation and API testing, owning part of a framework, and mentoring newer testers." Tie it to what you are doing now: the project, the practice, the learning.

What not to do

• Do not memorise definitions you cannot give an example for. The second question will expose it.
• Do not claim experience you do not have. Interviewers ask follow-ups until they find the edge.
• Do not put every tool you have heard of on the resume. Only list what you can talk about for five minutes.

One week before the interview

1. Day 1: manual testing questions and the quiz. Note the ones you miss.
2. Day 2: write test cases for login, signup and search from scratch, then compare with ours.
3. Day 3: SQL practice: joins, group by, second highest salary.
4. Day 4: one small automation script and be able to explain every line.
5. Day 5: your project: what you tested, what you found, what you would do differently.
6. Day 6: mock interview with a friend; record yourself answering "tell me about yourself".
7. Day 7: rest, then read the job description again and match your examples to it with the resume keyword matcher.