Software Testing
Get through the interviewPremium · free during launch9 min readPublished November 12, 2026

Junior QA interview questions, with model answers

The questions junior testers are asked most often, grouped by topic, each with a short model answer and a link to the article that explains it in depth. Use them to practise out loud, not to memorise.

On this page

Key takeaways

  • Junior QA interviews usually cover fundamentals, test design, bugs, process (Agile), technical basics (web, API, SQL), sometimes automation, and behaviour.
  • Strong answers follow a pattern: a short definition, a concrete example, and why it matters. An example from your own practice beats a perfect definition.
  • Practise out loud, ideally in English as well as your own language, and link each answer to something in your portfolio.

How to use this list

Don't memorise the answers word for word; interviewers notice. Read each one, then answer in your own words, with your own example. Each answer links to the article that goes deeper.

Fundamentals

1. What is software testing, and why is it needed?

Checking software against what it should do and reporting what you find, so the team can decide what to do. It reduces the risk of failures reaching users, which cost money, time and trust. Read more

2. What's the difference between QA and testing?

Testing finds defects in the product. QA (quality assurance) is broader: the processes that prevent defects, like reviews, standards and good requirements. In job ads, the words are often used interchangeably.

3. Error, defect, failure: what's the difference?

A person makes an error (a mistake), which creates a defect (a bug) in the code or documents. When the defective code runs, it can cause a failure: visible wrong behaviour. Read more

4. Name some of the testing principles.

For example: testing shows the presence of defects, not their absence; exhaustive testing is impossible; early testing saves money; defects cluster together. Give an example for one or two. Read more

5. Verification vs validation?

Verification: "Are we building the product right?", checking it matches the specification. Validation: "Are we building the right product?", checking it meets users' real needs. Read more

6. What are the levels of testing?

Component (unit), integration, system and acceptance testing. Each checks a different scope, from one function up to the whole product in the user's hands. Read more

7. Functional vs non-functional testing?

Functional: what the system does (the discount is applied correctly). Non-functional: how well it does it (speed, security, usability, accessibility). Read more

8. What is static testing?

Examining work products without running code: reviewing requirements, designs or code. It finds defects earliest and cheapest. Read more

Test design

9. What makes a good test case?

A clear title and objective, preconditions, specific steps and data, one expected result per check, and traceability to a requirement. Someone else should be able to run it and get the same verdict. Read more

10. Explain equivalence partitioning.

Split inputs into groups the system should treat the same, valid and invalid, and test one value from each group. For ages 18–65: one value below 18, one in range, one above 65. Read more

11. Explain boundary value analysis.

Bugs gather at the edges, so test values at and just outside each boundary: 17, 18, 65, 66 for an 18–65 range. Read more

12. Black-box vs white-box testing?

Black-box: tests designed from the requirements without looking at the code. White-box: tests designed from the code's structure, measured by coverage. Read more

13. What is exploratory testing?

Learning, designing and executing tests at the same time, guided by a charter and a time box, adapting as you find things out. It's structured, not random clicking. Read more

14. Positive vs negative testing?

Positive tests check the system works with valid input. Negative tests check it handles invalid input and misuse gracefully: clear errors, no crashes, no corrupted data.

15. Test case vs test plan vs test strategy?

A test case checks one thing. A test plan describes how a specific project or release will be tested. A test strategy is the general approach across projects. Read more

Bugs

16. What goes into a good bug report?

A specific title, steps to reproduce, expected and actual results, environment (build, browser, device), severity and evidence (screenshot, video, logs). Read more

17. Severity vs priority? Give an example of high severity, low priority.

Severity is the impact; priority is how soon to fix it. High severity, low priority: a crash in a rarely used admin report with a workaround. Low severity, high priority: a typo in the company name on the home page. Read more

18. Describe the bug life cycle.

New → Assigned → In progress → Fixed → Ready for retest → Closed, with exits like Rejected, Duplicate, Deferred and Reopened if the retest fails. Read more

19. A developer says your bug "works on my machine". What do you do?

Compare environments (build, browser, data, account), add more detail and evidence, and try to reproduce it together. The goal is to understand the problem, not to win the argument.

20. What do you do if you find a bug you can't reproduce?

Report it anyway, clearly marked as intermittent, with everything you know: time, environment, data, logs, screenshots. Note how often it happens and keep trying variations.

Process and Agile

21. What is the STLC?

The phases of testing: requirement analysis, test planning, test design, environment setup, execution and closure, each with entry and exit criteria. Read more

22. What does a tester do in a Scrum sprint?

Helps refine stories and acceptance criteria, estimates testing, designs tests while code is written, tests stories as soon as they're ready, retests fixes, runs regression, and checks the Definition of Done. Read more

23. What is the Definition of Done?

A shared checklist every story must meet to be "done", typically code reviewed, tests passing, tested on a test environment, and no open major bugs.

24. Regression testing vs retesting?

Retesting checks that a specific bug is fixed. Regression testing checks that the change didn't break anything else. Read more

25. Smoke vs sanity testing?

Smoke: a quick, broad check that a new build works well enough to test at all. Sanity: a quick, narrow check that a specific fix or change works. Read more

26. When do you stop testing?

When the agreed exit criteria are met (coverage, no open critical bugs, risks addressed), or when time runs out, in which case you report clearly what wasn't tested and the remaining risk. You can never test everything.

Technical basics

27. What happens when you type a URL in a browser?

DNS resolves the domain to an IP address, the browser opens a (secure) connection, sends an HTTP request, the server responds with a status code and content, and the browser renders the page, making more requests for resources. Read more

28. What do 200, 201, 400, 401, 403, 404 and 500 mean?

OK, Created, Bad Request, Unauthorized (not logged in), Forbidden (no permission), Not Found, and Internal Server Error (a server bug). 4xx: the client's request was wrong. 5xx: the server failed.

29. GET vs POST?

GET reads data and shouldn't change anything. POST sends data to create something, like an order.

30. How would you test an API?

Check status codes, response data and structure for valid requests; then invalid data, missing fields, wrong types, no authentication, and another user's data. Tools: Postman or code. Read more

31. Write a SQL query to find all orders over 500 from customers in Cluj.

SELECT o.id, o.total
FROM orders o
JOIN customers c ON c.id = o.customer_id
WHERE c.city = 'Cluj' AND o.total > 500;

Read more

32. How do you use browser DevTools when testing?

The Console for JavaScript errors, the Network tab for requests, status codes and response data, Application for cookies and storage, and device mode for quick responsive checks. Read more

Automation

33. What should you automate, and what not?

Automate stable, repetitive, high-value checks such as regression of critical flows, and data-heavy checks. Keep exploration, usability and fast-changing features manual. Read more

34. What is the test pyramid?

Many fast unit tests at the bottom, fewer integration/API tests in the middle, few slow UI tests at the top, for fast, reliable feedback. Read more

35. What makes an automated test flaky, and what do you do about it?

It passes and fails without code changes, often because of timing, shared data or unstable environments. Find the cause rather than adding waits, and quarantine it so it doesn't hide real failures.

Behaviour and motivation

36. Why do you want to be a tester?

Be specific and honest: what you enjoy (finding how things break, attention to detail, helping users), what you've already done (portfolio), and why this company or product.

37. Tell me about a bug you found.

Use your portfolio. Describe the context, how you found it, how you reported it, and what happened. Show your thinking, not just the bug.

38. What would you do if the release deadline doesn't allow time to test everything?

Prioritise by risk: critical flows and recent changes first. Be transparent about what won't be tested and the risk it carries, so the release decision is made with full information.

Real-world exampleTwo answers to the same question

In a practice interview (an illustrative example), two candidates were asked: "What's the difference between severity and priority?"

The first said: "Severity is the impact of the bug and priority is the urgency." Correct, but forgettable.

The second said: "Severity is how bad the impact is, and priority is how soon we fix it. They can differ. Last week I tested a demo shop where the logo linked to a 404 page. It was low severity, but on a real launch day I'd argue for high priority, because it's the first thing customers click. The opposite would be a crash in an export nobody uses until year-end." Then she showed the bug report.

Lesson: definition, example, reasoning. That structure turns a textbook answer into evidence that you can do the job.

Do

Prepare 4–5 stories from your portfolio and past jobs that you can adapt to many questions: a bug you found, a disagreement you resolved, a time you learned something fast.

Don't

Recite definitions without examples, or pretend to know a tool you've never used.

Check yourself

The interviewer asks a question you can't answer: 'What's the difference between load and stress testing?' How do you respond?

Show answer

Be honest and reason out loud: "I haven't done performance testing yet. My understanding is that load testing checks behaviour under expected traffic, and stress testing pushes beyond it to find the breaking point. I'd want to confirm that." That shows honesty, reasoning and curiosity. (And it's right: see performance testing fundamentals.)