QA Interview Questions for Freshers: 50 Questions You Will Actually Be Asked

Most fresher QA interview lists on the internet were written in 2018 and copy-pasted ever since. This one is from someone who has sat on both sides of the table in the last twelve months. The questions are current. The answers are how a real tester would think.

How fresher QA interviews actually work

The structure has not changed much in five years. Round one is usually a screening: SDLC, types of testing, basic vocabulary. Round two goes deeper into manual testing, defect lifecycle, and walkthroughs of how you would test a feature. Round three covers automation if the role expects it, plus behavioral questions and the inevitable “what is your weakness” trap.

I am sorting these questions by topic, not by difficulty, because in real interviews the topics blur together.

Foundation and SDLC

1. What is the difference between QA and QC? QA is about preventing defects through process. QC is about detecting defects through testing. They overlap, but they are not the same.
2. Walk me through the SDLC. Requirements, design, development, testing, deployment, maintenance. Modern teams iterate through these continuously rather than sequentially.
3. What is STLC and how is it different from SDLC? STLC is the testing life cycle that runs inside the SDLC. Six phases: requirement analysis, planning, design, environment setup, execution, closure.
4. What is the difference between verification and validation? Verification asks: are we building it right. Validation asks: are we building the right thing.
5. Explain the V-model. A development model where each phase has a corresponding testing phase. Requirements map to acceptance testing, design maps to system testing, and so on.
6. What is Agile testing and how is it different from waterfall testing? Agile testing happens continuously across short iterations. Waterfall testing happens in a dedicated phase after development is complete.

Test design and execution

7. What goes into a good test case? ID, title, preconditions, numbered steps, test data, expected result, actual result, status, severity if failed.
8. Walk me through testing a login page. Positive, negative, edge cases. Cover field validation, authentication logic, session handling, security, accessibility, and cross-browser behavior.
9. What is equivalence partitioning? Grouping inputs into classes that should behave the same way, then testing one representative value from each class.
10. What is boundary value analysis? Testing the values at the edges of input ranges, where most off-by-one bugs hide.
11. What is the difference between smoke and sanity testing? Smoke checks the most critical paths after a build. Sanity is a targeted retest of a fixed area.
12. What is regression testing? Re-running tests on existing functionality to make sure new changes did not break what used to work.
13. What is exploratory testing? Structured improvisation. Testing without a script to find what scripted tests miss.
14. What is risk-based testing? Prioritizing test effort on the areas where failure would cause the most harm.

Defects and bug reporting

15. Walk me through the defect lifecycle. New, Assigned, Open, Fixed, Retest, Verified, Closed. With detours through Rejected, Deferred, Reopened.
16. What is the difference between severity and priority? Severity is technical impact. Priority is business urgency. They are independent.
17. What goes into a good bug report? Specific title, environment, numbered reproduction steps, expected vs actual, attachments, frequency, severity and priority.
18. What if a developer disagrees that something is a bug? I gather evidence: requirements, screenshots, similar past defects. I have the conversation in writing. If we still disagree, we escalate to product or QA lead.
19. What is a flaky test and how do you handle it? A test that sometimes passes and sometimes fails without code changes. Investigate timing, dependencies, test data, environment. Quarantine if needed. Never just rerun until green.
20. What is the cost of a defect found late? Exponentially higher than one found early. The earlier in the SDLC a defect is caught, the cheaper it is to fix.

Automation and tools

21. Why automate? To run repeatable tests faster, more often, and with less human error. To free human testers for exploratory work.
22. What should not be automated? One-off tests, exploratory scenarios, anything that changes constantly, anything where the cost of automation exceeds the cost of manual execution.
23. What is the Page Object Model? A design pattern that wraps each page or component in a class, so test logic and UI selectors stay separate. Easier to maintain.
24. What is the difference between Selenium and Playwright? Playwright was built later, has auto-waiting, cleaner syntax, and better debugging tools. Selenium has a longer history and broader legacy support.
25. What are explicit and implicit waits? Implicit waits set a default wait time for the whole driver session. Explicit waits target a specific condition. Modern frameworks like Playwright handle this automatically.
26. How do you handle dynamic elements in automation? Stable locators based on roles, text, or test IDs. Avoid brittle XPath. Wait for state, not time.
27. What is data-driven testing? Running the same test logic against multiple sets of input data, often via parameterization or external data sources.
28. What is CI/CD and how does QA fit into it? Continuous Integration runs tests on every commit. Continuous Deployment ships passing changes automatically. QA owns the test suites that gate the pipeline.

API testing

29. What are HTTP status codes? Three-digit responses. 2xx is success, 3xx is redirection, 4xx is client error, 5xx is server error.
30. What is the difference between PUT and PATCH? PUT replaces the entire resource. PATCH applies a partial update.
31. How do you test an API? Validate status codes, response time, response body schema, authentication, error handling, and edge cases for each endpoint.
32. What is REST? An architectural style for APIs based on stateless requests, standard HTTP methods, and resource-based URLs.
33. What is the role of headers in an API request? They carry metadata: authentication tokens, content type, caching directives, custom application data.

Behavioral and situational

34. Tell me about yourself. 30-second pitch covering background, current focus, why QA, and what you are looking for next.
35. Why QA and not development? Honest answer about your interest in product quality, breaking things to understand them, and the engineering side of testing.
36. Tell me about a time you found a critical bug. Use STAR: situation, task, action, result. Specific bug, your role, what you did, the outcome.
37. How do you handle disagreements with developers? Direct, evidence-based, written, escalate only when necessary. Frame it as a shared goal: ship quality.
38. What is your weakness? Pick a real one with a real plan to improve. Avoid the cliche fake weaknesses.
39. Where do you see yourself in three years? Honest career trajectory. Senior QA, automation lead, SDET, whatever fits the role.
40. Why this company? Specific reasons tied to the product, the team, or the technology. Generic answers signal you did not prepare.
41. How do you stay current with QA trends? Specific sources: blogs, podcasts, communities, books. Name two or three.
42. What was your most challenging project? Real example with real stakes and a real outcome. Show how you think under pressure.

Tricky and trap questions

43. What is the most important quality of a tester? Curiosity. Everything else can be taught.
44. How would you test a coffee machine? Functional, edge cases, usability, durability, error handling, accessibility. Show structured thinking, not memorized testing types.
45. What is a test plan vs test strategy? Strategy is the high-level approach for the org. Plan is the project-specific document derived from strategy.
46. Can you 100 percent test a product? No. Exhaustive testing is impossible. The goal is sufficient coverage of risk.
47. How would you test if there are no requirements? Talk to stakeholders, study similar products, write down assumptions, validate them, document everything.
48. What is shift-left testing? Moving testing activities earlier in the SDLC, into requirements and design phases.
49. What is a test pyramid? The model that prescribes more unit tests at the base, fewer integration tests in the middle, and the smallest layer of end-to-end tests at the top.
50. Do you have any questions for us? Always yes. About the team, the process, the product, the role. Never end an interview with no questions. It signals disinterest.

How to actually prepare

Reading 50 questions is the easy part. Memorizing answers is the trap. The interview is a conversation, not a quiz. Practice answering each of these questions out loud, in your own words, with specific examples from your own work. Record yourself. Listen back. The first three rounds will feel awkward. By round ten, the answers feel like reflexes. That is the goal.

Written by

Anveet Singh Chhabda

QA engineer and software testing educator. Manual testing, Playwright automation, and API testing taught from real-world product experience.