cvlift.ai logo
Toggle menu
FeaturesJob TrackerATS CheckerBlog
CV BuilderCV Job MatchCover Letter GeneratorRole ResourcesCV ExamplesSalary GuidesInterview GuidesCover Letter Examples
Log InTry for Free

Role guide

Manual tester interview preparation

Updated 4 September 2026

Manual Tester interviews may cover a range of testing skills and tasks. This guide sets out the limited process evidence available and helps Manual Tester interview candidates prepare examples from their own work.

01

How the interview usually works

The evidence does not establish a standard sequence, participant list or timing across employers. The stage below describes a possible focus for Manual Tester interview candidates, not a universal process.

  1. Possible focus for Manual Tester interview candidates

    The format is not established by the available evidence.

    Possible

    For Manual Tester interview candidates, an interview may focus on a variety of testing skills and tasks.

    What they assess

    • Testing skills and tasks

    How to prepare

    • Manual Tester interview candidates should prepare one project explanation covering objectives and specifications, test scenarios and execution, bugs found, communication with developers, solution tracking and rechecking.
    • Manual Tester interview candidates can prepare an example of identifying, documenting and reporting a bug with a tracking tool, followed by regression testing after a fix or update.
    • Manual Tester interview candidates should choose examples showing collaboration with developers, persistence during repeated testing and creative analysis of an unusual scenario.
02

Your preparation plan

Build a focused evidence bank

Choose two or three truthful projects that you can explain without relying on textbook definitions. For one project, Manual Tester interview candidates should cover the objectives and specifications, test scenarios and execution, bugs found, communication with developers, solution tracking and rechecking.

Manual Tester interview candidates can also prepare separate examples of bug reporting and regression testing, collaboration with developers, persistent repetition, and an unusual scenario that required creative analysis. Explain the situation, your decisions, what you did and the result.

Review the job description and match its testing work to examples you can defend. If possible, Manual Tester interview candidates can complete a mock interview with someone in the industry and ask for targeted feedback.

The week before

  • Review the job description and mark the testing work for which you have direct, truthful examples.
  • As a Manual Tester interview candidate, prepare one project explanation covering objectives, specifications, test scenarios, execution, bugs, developer communication, solution tracking and rechecking.
  • As a Manual Tester interview candidate, choose an example of identifying, documenting and reporting a bug with a tracking tool, followed by regression testing after a fix or update.
  • As a Manual Tester interview candidate, prepare an example of productive collaboration with developers.
  • As a Manual Tester interview candidate, prepare an example showing persistence through repeated testing and explain how it helped prevent customer aggravation.
  • As a Manual Tester interview candidate, prepare an unusual test scenario that shows how you analysed the problem, created tests and obtained a concrete result.
  • If possible, complete a mock interview with someone in the industry and ask for targeted feedback.

The day before

  • Practise concise, structured answers aloud without memorising a script.
  • Confirm the interview time, location or joining details and ask the named contact about anything unclear.

On the day

  • Bring permitted notes with short prompts for your chosen projects and examples.
  • If your interview is remote, test your camera, microphone and connection before joining.
03

What interviewers look for

Manual test execution and result comparison

For manual tester interview candidates, manual testing involves interacting with software, executing test cases without automation tools and comparing actual results with expected results.

Evidence to prepare

  • Choose an example where you followed test cases manually and recorded the actual result.
  • Recall a mismatch between expected and actual behaviour that you investigated.
  • Identify the checks you used to keep execution consistent.

Attention to detail and user-focused analysis

Manual tester roles need close observation to find subtle bugs and analytical thinking to consider how software may fail from a user's perspective.

Evidence to prepare

  • Find an example of a small change or unusual behaviour you noticed.
  • Choose a defect that was easy to overlook but mattered to the user.
  • Recall how you explored beyond the obvious path without losing focus.

Defect reporting and verification

Manual QA testers identify and track defects, verify fixes and document test results.

Evidence to prepare

  • Select a defect report that helped another person reproduce the issue.
  • Recall a fix you retested and the result you recorded.
  • Choose an example where your documentation made the test outcome clear.

Test design and prioritisation

Manual testers may create test plans with product development colleagues, turn requirements into test scenarios and prioritise tests by criticality.

Evidence to prepare

  • Choose a requirement you translated into test scenarios.
  • Recall how you decided which tests to run first under time pressure.
  • Find an example where a review improved your test plan or test cases.

Communication and teamwork

Manual tester interviews may assess communication and teamwork because manual tester roles involve working with stakeholders, including developers and senior management.

Evidence to prepare

  • Choose an example of discussing a difficult defect with a developer.
  • Recall how you explained test risk to someone with a different level of technical knowledge.
  • Find a case where teamwork helped resolve a difficult testing issue.

Adaptability and testing-tool awareness

Manual tester roles need adaptability when testing priorities change, and familiarity with JIRA may be expected in some roles.

Evidence to prepare

  • Recall a late change that forced you to revise your testing priorities.
  • Choose an example of learning a testing tool or workflow quickly.
  • If you have used JIRA, identify a testing task for which you used it.
04

Questions you should be ready for

Use the answer plans as prompts, not scripts. Your examples should sound like you.

Manual-testing fundamentals

Check whether the candidate can explain core manual-testing concepts and apply them clearly.

What is manual testing, and how do you compare actual results with expected results?

What they want to learn: To assess whether you understand manual execution without automation tools and can explain how results are judged.

Answer plan

  • Give a concise definition of manual testing.
  • Explain how you determine the expected result in your example.
  • Describe how you performed the interaction, recorded the actual result and compared the two.
  • Finish with what you did when the results differed.

Evidence to use: Use a test you personally executed and explain one comparison you made between expected and actual behaviour.

Avoid

  • Giving a definition without explaining the comparison.
  • Failing to explain how you investigated a difference between expected and actual results.
  • Describing an automated script instead of manual interaction.
What is the difference between manual and automated testing, and where can manual testing be limited?

What they want to learn: To assess your grasp of the distinction between manual and automated testing and the limits of manual work.

Answer plan

  • Define each approach in plain terms.
  • Compare them using a testing situation you understand.
  • Explain one genuine limitation of manual execution.
  • State how you chose an approach in your example rather than arguing that one is always better.

Evidence to use: Choose a project or exercise where you can explain why manual execution was useful and where it became restrictive.

Avoid

  • Claiming one approach is always better.
  • Turning the answer into a list of tools.
  • Claiming that manual testing always requires coding.
How do a test plan and a test case differ?

What they want to learn: To assess whether an entry-level candidate understands broad QA concepts concerning test plans and test scripts or cases.

Answer plan

  • Define the purpose of a test plan.
  • Define an individual test case in plain language.
  • Explain the relationship between the case and the wider plan.
  • Use a small feature to illustrate the distinction.

Evidence to use: Think of one feature and outline the broad planning decisions followed by one concrete test case.

Avoid

  • Using the terms interchangeably.
  • Reciting definitions without an example.
  • Adding process rules that did not apply in your own setting.

Test design and risk

Explore how the candidate turns requirements into test scenarios and prioritises testing when time is limited.

How would you turn a business or technical requirement into test scenarios?

What they want to learn: To assess how you decompose requirements into test-case scenarios during test-strategy work.

Answer plan

  • State the business or technical requirement you are working from.
  • Break that requirement into test-case scenarios and explain the connection between each scenario and the requirement.
  • When performing test-strategy formulation, identify the test data needed for your scenarios.
  • Note any unclear part of the requirement and explain how it affected your work.

Evidence to use: Choose a real requirement you broke down and note which scenario exposed the most useful information.

Avoid

  • Listing scenarios without connecting them to the requirement.
  • Ignoring assumptions or missing information.
  • Presenting every conceivable test as equally useful.
How do you prioritise tests when time is limited?

What they want to learn: To assess whether you can rank tests by criticality and explain your judgement.

Answer plan

  • State the time constraint and what has changed.
  • Explain how you judged the criticality of the tests in that situation.
  • Group the tests by high, medium and low criticality.
  • Describe the order you chose and the reasoning behind it.

Evidence to use: Use an occasion when you had to reduce or reorder planned coverage and explain the consequence of that choice.

Avoid

  • Saying you would simply work faster.
  • Treating every test as high priority.
  • Giving an order without explaining your judgement.
How do you define the scope of testing for a change?

What they want to learn: To assess the scope-setting judgement that may be explored in advanced manual tester interviews.

Answer plan

  • Describe the change and the information available to you.
  • State the scope you chose in that example.
  • Explain the reasoning behind your scope decision.
  • Describe the outcome and what the experience taught you about setting scope.

Evidence to use: Choose a substantial change for which you set or influenced test scope and explain the judgement you made.

Avoid

  • Claiming complete coverage without limits.
  • Confusing a list of test cases with a reasoned scope.
  • Giving a scope decision without explaining why you made it.

Defects and difficult situations

Examine defect investigation, reporting, retesting and judgement when problems carry significant risk.

Tell me about a subtle bug you found. How did you investigate and report it?

What they want to learn: To assess the attention to detail, analytical thinking and reporting needed to find and communicate subtle defects.

Answer plan

  • Set the context and describe the behaviour you noticed.
  • Explain how you reproduced it and narrowed the conditions.
  • Describe the evidence and steps you recorded.
  • State what happened next and what you learnt.

Evidence to use: Pick a bug that another tester might easily have missed and use only details you can defend.

Avoid

  • Taking sole credit for a team result.
  • Omitting reproducible steps or observed evidence.
  • Spending most of the answer describing the product.
What would you do if you found a mission-critical bug shortly before release?

What they want to learn: To assess how an advanced manual tester candidate handles a serious defect and communicates the issue.

Answer plan

  • Explain how you would confirm the behaviour without delaying the report unnecessarily.
  • Set out the evidence you would capture and whom you would inform under the employer's process.
  • Describe how you would make the affected behaviour clear without overstating what you know.
  • Explain how you would support retesting once a fix became available.

Evidence to use: Use a truthful example of a high-impact defect or, if you lack one, explain your reasoning as a hypothetical.

Avoid

  • Claiming authority over a release decision you did not hold.
  • Downplaying the need for clear evidence.
  • Treating severity and urgency as self-explanatory.
How do you verify a defect fix and document the result?

What they want to learn: To assess whether you can retest a reported problem and leave a clear record of the outcome.

Answer plan

  • Restate the original failure conditions and expected behaviour.
  • Run the original reproduction steps against the fix.
  • Compare the new result with the expected behaviour.
  • Document the test result and any remaining concern.

Evidence to use: Choose a fix you verified and explain the result you documented.

Avoid

  • Treating one changed screen as sufficient proof without repeating the relevant test.
  • Forgetting to record the conditions under which you tested.
  • Claiming broad regression coverage you did not perform.

Collaboration, change and tools

Assess how the candidate works with others, responds to shifting priorities and discusses experience with JIRA.

Tell me about a difficult issue you helped a team resolve.

What they want to learn: To assess problem-solving and teamwork through evidence from a candidate's manual-testing experience.

Answer plan

  • Describe the issue and your responsibility in resolving it.
  • Explain the investigation or communication you personally contributed.
  • Show how you worked with others and handled disagreement or uncertainty.
  • Give the outcome and one lesson you carried forward.

Evidence to use: Choose a case with a genuine obstacle and make your own contribution distinct from the team's work.

Avoid

  • Using a routine task with no difficult decision.
  • Blaming colleagues for the problem.
  • Describing only the team's actions.
How do you explain a defect and its risk to developers and senior management?

What they want to learn: To assess communication with stakeholders who may need different levels of detail.

Answer plan

  • Start with the observed behaviour and who or what it affects.
  • Explain the reproduction detail and evidence you gave to developers.
  • Describe how you presented the issue to senior management in your example.
  • Explain how you answered questions without presenting assumptions as facts.

Evidence to use: Recall one issue you explained to people with different technical backgrounds and how you changed the level of detail.

Avoid

  • Using the same technical detail for every audience.
  • Presenting assumptions as confirmed impact.
  • Becoming defensive when the defect is challenged.
How have you used JIRA in your manual-testing work?

What they want to learn: To assess your practical familiarity with JIRA in a manual-testing context.

Answer plan

  • Describe the project or testing context.
  • State the testing task for which you used JIRA.
  • Explain what you personally did in the tool without assuming a standard workflow.
  • Finish with the outcome of your work.

Evidence to use: Use a genuine example involving JIRA. If you have not used it, say so and discuss only relevant experience you actually have.

Avoid

  • Claiming JIRA experience you do not have.
  • Listing interface features without describing your own work.
  • Presenting one employer's use of JIRA as universal.
Tell me about a time changing priorities forced you to revise your testing.

What they want to learn: To assess the adaptability needed when priorities change in manual tester roles.

Answer plan

  • Explain what changed and why it affected the original plan.
  • Describe how you reassessed the criticality of tests and the time available.
  • Explain the revised order you chose.
  • State the result and what you would repeat or change next time.

Evidence to use: Choose an example where you made a clear trade-off rather than merely accepting a new task.

Avoid

  • Presenting adaptability as agreeing to everything.
  • Giving no reason for the revised order.
  • Leaving your own decision out of the answer.
05

Questions to ask them

“How does the team document, prioritise and track defects?”

This clarifies the team's defect-reporting process and the information you would need to provide.

“What types of manual testing would take up most of my time?”

This helps you compare the day-to-day work with your experience and interests.

“How are requirements and expected results shared with testers?”

This shows what information you would receive before designing or executing test cases.

“What happens after a developer marks a defect as fixed?”

This clarifies how the team handles rechecking and regression testing after fixes.

“How do testers and developers handle disagreements about a reported defect?”

This can show how the team discusses evidence and resolves different interpretations.

“Which testing tools and working methods would I use in this role?”

This identifies what you would need to learn or use after joining.

06

On the day

In person

  • Bring concise notes on two or three genuine testing examples, including the objective, tests performed, defects found and what happened afterwards.
  • Read each scenario carefully. State your assumptions, then explain the checks you would run and why.
  • When discussing a defect, separate what you observed from what you expected and explain how someone else could reproduce it.
  • Arrive early enough to deal with reception or access arrangements without rushing.

Remote

  • If your interview is remote, test your camera, microphone and connection beforehand.
  • Keep the job description and brief notes nearby, but do not read answers from a script.
  • Close unnecessary applications and notifications so you can concentrate on detailed scenarios.
  • If the invitation mentions screen sharing, prepare a tidy desktop and check that you can share the correct window.
07

Common mistakes

Going into a Manual Tester interview with only a loose grasp of testing fundamentals.

Revise the concepts you genuinely use and practise explaining how they affect a real testing decision.

Describing test cases in theory but being unable to explain how you would write and execute one.

Practise building a test case, then explain how you would execute it and record the result.

Giving textbook answers without showing real-world problem-solving.

Use a truthful example where you investigated an unexpected result and decided what to do next.

Missing small but relevant details when discussing a Manual Tester scenario.

Pause, read the available information closely and explain which details influenced your proposed tests.

Reporting defects vaguely when discussing work with development teams.

Explain the observed behaviour, expected behaviour, reproduction steps and supporting evidence in neutral language.

Treating manual and automated testing as interchangeable.

Explain that manual testing can suit usability or unusual situations, while automation may suit repetitive or performance tests.

08

After the interview

Send a short thank-you message that refers to one relevant point from the conversation. Include any information you promised and keep the message factual.

If you do not receive an offer, you may politely ask for feedback. The interviewer may not provide it.

09

Frequently asked questions

From guide to application

Make your CV and your answers tell the same story.

Use cvlift to tailor your CV to the role and bring the most relevant experience forward. Then use this guide to practise the examples behind it.

Tailor my CV