Software tester interview questions for beginners (with answers)

Most junior software tester interviews in the UK ask the same core things: what testing is for, how you'd write a test case, how you'd report a bug, and how you'd test something in front of you. Learn clear answers to about a dozen questions and practise one live testing exercise, and you'll be ahead of most applicants. The people who get offers answer with real examples, not textbook definitions.

What do interviewers want to hear from a junior tester?

Three things. That you think in a structured way. That you can explain a problem clearly to a developer. And that you're curious enough to keep poking at something until it breaks.

The National Careers Service lists thoroughness, attention to detail, analytical thinking and good verbal communication as core skills for testing roles. That matches what hiring managers screen for. Nobody expects a junior to know every testing technique. They want to see that you'd be useful in a sprint by week three.

So every answer should show your thinking out loud. Don't recite. Explain.

What are the most common manual testing interview questions?

These come up again and again in manual testing interview questions for junior roles. Short sample answers follow each one.

What's the difference between verification and validation? Verification checks you've built the product right (does it match the spec). Validation checks you've built the right product (does it do what users actually need). Give a quick example: a form can match the spec perfectly and still confuse every real user.

What's the difference between severity and priority? Severity is how badly the bug affects the system. Priority is how soon it needs fixing. A spelling mistake in the company name on the home page is low severity but high priority. A crash in a rarely used admin report might be high severity but lower priority.

What is regression testing? Re-running tests after a change to check nothing that used to work has broken. Mention that regression packs are often the first thing teams automate, because they're repetitive.

What's the difference between smoke and sanity testing? A smoke test is a quick check that a new build is stable enough to test at all. A sanity test is a narrow check that a specific fix or feature works.

What are boundary value analysis and equivalence partitioning? Both are ways to pick test data without testing every possible value. If an age field accepts 18 to 65, you'd split values into partitions (under 18, 18 to 65, over 65) and test the edges: 17, 18, 65 and 66. These techniques are part of the ISTQB Foundation syllabus, so if you've passed it, say so and then show you can use them.

What goes into a good test case? An ID, a clear title, preconditions, numbered steps, test data, expected result and actual result. Anyone on the team should be able to run it and get the same outcome.

How do you answer the "how would you test this?" question?

This is the question that sorts people. It might be a pen, a lift, a kettle, or the interviewer's own login page.

Don't start listing tests. Start by asking questions. Who uses it? What are the requirements? What platforms does it run on? What matters most to the business? Then group your ideas:

• Functional: does it do the main job?
• Negative: what happens with wrong or missing input?
• Boundaries and edge cases
• Usability and accessibility
• Performance and security, at a basic level

For a login page, for example, you'd cover valid and invalid credentials, empty fields, password masking, account lockout after failed attempts, the "forgot password" flow, keyboard-only use and what happens on a slow connection. Talk the interviewer through why each one matters. Structure beats volume every time.

How should you describe a bug report in an interview?

You'll often be asked to write one or talk through one. A good bug report has a short, specific title, the environment (browser, device, build number), steps to reproduce, expected result, actual result, severity, and evidence such as a screenshot or screen recording.

Then add the bit most candidates miss: tone. A bug report is a message to a colleague. It should be neutral and factual so a developer can fix it without a back-and-forth. If you can mention that you've logged bugs in Jira or Azure DevOps, do. If you can show a real one you wrote (with anything confidential removed), even better.

What technical questions might come up?

Junior manual roles rarely go deep on code. You may still get asked:

What's the difference between the SDLC and the STLC? The software development life cycle covers building the whole product. The software testing life cycle covers the testing activities within it: planning, analysis, design, execution and closure.

How does testing fit into Agile? Testers work inside the sprint, join refinement sessions, help shape acceptance criteria and test stories as they're finished rather than at the end.

Have you used any tools? Be honest. Name what you've genuinely touched: Jira for tickets, TestRail or Zephyr for test cases, Postman for API checks, browser developer tools for checking console errors. If you've only read about Selenium or Playwright, say that you understand what they do and that you're learning.

Can you write a basic SQL query? Some test analyst roles ask this. Know SELECT, WHERE and a simple JOIN. That covers most junior checks on whether data saved correctly.

What behavioural questions should you prepare for?

Expect "tell me about a time" questions. A developer disagreed with your bug. You found an issue late in a release. You had too many things to test and not enough time.

Use a simple structure: the situation, what you did, what happened. Keep it under two minutes.

This is where beginners struggle, because they don't have stories. "I'd raise it with the developer" is a guess. "On the booking form I tested, I found that the date picker allowed past dates, I logged it with a recording, the developer pushed back, so I showed the acceptance criteria and it was fixed in the next sprint" is evidence. The second answer gets the job.

If you don't have stories yet, that's the gap to close before your next interview, not more revision.

How do you stand out with no experience?

Bring proof. A one-page portfolio with a short test plan, five or six well-written test cases and two or three real bug reports from a live product changes the whole conversation. It gives the interviewer something to ask about other than your CV.

Practise out loud. Record yourself testing a public website and narrating your thinking.

Ask good questions at the end. "How do testers and developers work together here?" and "What does a tester's first month look like?" show you're thinking about the actual job. Our guide to software testing skills covers what to practise, and the manual software tester jobs page shows the roles these questions lead to.

How Experiencely can help

If you already have your ISTQB Foundation, a relevant degree or a testing course behind you, the Experiencely software testing programme gives you the missing piece: real experience. It's experience only, so there's no training or certification included. You're placed within 48 hours on a live product, working fully remote for about an hour a day over three months, writing test cases and raising real bugs. That gives you genuine stories for every behavioural question above. The programme costs £2,495 and comes with a guarantee: hired within 60 days of finishing (conditions apply) or your money back.

Frequently asked questions

Sources

Figures are taken from the sources below. Salary ranges are indicative and individual offers vary. Last checked 9 November 2026.

1. BCS: ISTQB Certified Tester Foundation Level
2. National Careers Service: Test lead job profile
3. ITJobsWatch: Test Analyst jobs, UK