QA Tester Interview Questions
A junior QA tester interview usually checks two things. Hard skills: whether you understand testing basics, can write a bug report, and know how client-server applications work. Teamwork: whether you know how Scrum and development processes work and whom to ask about what.
Interviewers care less about memorised definitions than about understanding: why you answered the way you did and what you would do in a real situation. That is why every quiz below explains the answers, and all its questions with explanations are listed right under the quiz.
QA basics and the tester’s role
Interviews usually start here: how testing differs from QA, what the levels of testing are, how smoke testing differs from regression testing, what positive and negative checks are, and what to do when requirements are incomplete.
Example. “What is the difference between testing and QA?” Testing checks the product against requirements and looks for defects. QA is broader: it also covers requirements, processes, and reviews so that defects do not appear at all.
Practise it
Bug reports, severity, and priority
Almost every interview asks you to take a bug report apart: what makes a good title, what goes into the actual result, what good steps to reproduce look like, and what to put in the environment. Interviewers also check behaviour: what you say to a developer who answers “it works on my machine”.
Example. Severity is how badly a bug affects the product; priority is how urgently it must be fixed. A typo on the home page has low severity but high priority. A crash in a rarely used old report is the opposite.
Practise it
Practical questions
Here interviewers check how you think: how to test a login form, where to start when the release is tomorrow, which bug to retest first, what to check in a Postman response, what a test case and a test report contain, and why a tester needs SQL.
Example. “How would you test a login form?” A strong answer names a successful sign-in, a wrong password, empty fields, an invalid e-mail format, spaces and long values, error messages, and also security and usability.
Practise it
Client-server at an interview
Even for a manual testing role, interviewers ask how a web application works: what a client and a server are, what happens after you press “Sign in”, how HTTPS differs from HTTP, which methods and status codes exist, and how to tell whether a problem is on the client or the server.
Example. “What is the difference between 404 and 500?” 404 means the requested resource was not found: the problem is in the request or address. 500 is an internal server error. The first digit of the code already tells you where to look.
Practise it
Scrum, Agile, and development processes
The second part of the interview is about teamwork. Interviewers ask how Agile differs from Scrum, what a sprint, the Daily, a retrospective, and the Definition of Done are, how QA takes part in a sprint, and also about the SDLC, acceptance criteria, code freeze, test environments, CI, and what to do about a bug in production.
Example. “What is the difference between Agile and Scrum?” Agile is an approach and a set of values: short iterations, fast feedback, readiness for change. Scrum is one of the frameworks that implements it, with specific roles, events, and artefacts.
Practise it
- Scrum, Agile and TeamworkQuiz: Agile and Scrum, sprint, roles, Daily and retrospective, Definition of Done, Sprint Review, Backlog Refinement, the QA role in a sprint and communication in a team.
- Development Processes: SDLC, retro, code freezeQuiz: SDLC, retrospective, code freeze, acceptance criteria, sprint planning, test environments, CI and a bug on production.
Team roles
The interviewer wants to know whether you will fit into the team: whom to go to when the test environment is down or Postman returns 500, whom to ask about a mismatch with the design, how to tell a developer about a bug, and what to do when the Product Owner asks for an urgent check in the middle of a sprint.
Example. “Who is responsible for quality in an Agile team?” The whole team: developers, analysts, designers, and QA, each in their own area. The tester helps find risks but is not the only one responsible.
Practise it
How to prepare
Take the quizzes in order and note the topics where you make mistakes. Review them in the QA basics, bug reports, and client-server quizzes, and practise them in the test design and HTTP trainers. At the interview, answer in your own words and give an example from practice: it is more convincing than any definition.