InterviewPrepInterviewPrep· Job Insights

QA Engineer technical round: test design and automation

The QA Engineer technical round tests how you think about breaking software: designing test cases, spotting edge cases, automating checks and reasoning about defects. It rewards a structured, sceptical mindset over rote tool knowledge. Below is how the round runs, the areas probed, worked strong-versus-weak answers, and how to rehearse the test-design thinking interviewers look for.

Start a free mock interview →

What the QA technical round tests

QA rounds check whether you can turn a requirement into thorough, prioritised tests and automate the repeatable ones.

  • Test design: equivalence partitioning, boundary values, and negative cases.
  • Edge-case thinking: what breaks when inputs are empty, huge, malformed or concurrent.
  • Automation: when to automate, framework structure, and stable versus flaky tests.
  • API and integration testing: status codes, contracts, and data validation.

The signal they want is someone who finds the bugs others miss and knows which tests are worth automating.

Classic questions and how to approach them

Some prompts appear in almost every QA round.

'How would you test a login page?'

A strong candidate structures it: valid and invalid credentials, boundary lengths, SQL-injection and XSS attempts, locked accounts, session handling, and cross-browser behaviour. A weak candidate lists 'correct and wrong password' and stops.

'How would you test a text field that accepts 1 to 100?'

They watch for boundary values (0, 1, 100, 101) and non-numeric input.

'When would you not automate a test?'

This probes judgement about maintenance cost and low-value or one-off checks.

Strong vs weak answers

Question: 'How would you test a file-upload feature?'

Strong: 'I would cover valid types and sizes, then push boundaries: empty file, oversized file, unsupported type, corrupted file, a file with a spoofed extension, and simultaneous uploads. I would check the error messages, the storage result, and security concerns like malicious payloads. Then I would automate the high-frequency happy paths and leave exploratory edge cases manual.' It shows breadth, security awareness and automation judgement.

Weak: 'I would upload a file and check it works.' It covers one path, ignores negatives and security, and shows no prioritisation. Interviewers read it as a tester who confirms rather than challenges.

How to prepare

Train the habit of decomposing any feature into test scenarios quickly.

  • Practise designing tests for everyday features: search, checkout, forms, uploads.
  • Always include negative, boundary and security cases, not just happy paths.
  • Be ready to justify what you would automate and why.

Since you must explain your reasoning aloud, rehearse narrating a test strategy clearly. A free AI voice mock interview on InterviewPrep builds a QA mock from your CV and a real job description, then scores your structure, pace and filler words, so your test-design thinking sounds systematic rather than a scattered list.

Frequently asked

Do QA technical rounds require coding?
Increasingly yes, at least enough to write or explain automation scripts and API tests. The depth depends on whether the role is manual, automation or hybrid. Even for manual roles, being able to reason about what to automate and why is a strong differentiator.
How do I answer 'how would you test X' questions?
Structure it rather than listing randomly. Cover happy paths, boundary values, negative and invalid inputs, security concerns and cross-environment behaviour, then note which cases you would automate. A visible structure shows thoroughness, which is exactly what QA interviewers screen for.
What edge cases do interviewers want me to mention?
Empty inputs, maximum and just-over-maximum values, malformed or malicious data, concurrency and unusual environments. Security cases like injection attempts on inputs earn extra credit. Naming edge cases others forget is the clearest signal of a strong tester.
When should I say a test should not be automated?
When it is one-off, changes constantly, or costs more to maintain than it saves, such as exploratory or rarely run checks. Showing this judgement matters, since automating everything indiscriminately creates flaky, high-maintenance suites that interviewers view as a red flag.
How do I stand out in a QA technical round?
Demonstrate a sceptical, structured mindset: decompose features quickly, surface non-obvious edge and security cases, and justify your automation choices. Narrating your test strategy clearly, rather than reciting a tool list, is what separates strong candidates from average ones.
Where do QA engineer roles get posted most often?
Naukri Jobs and LinkedIn carry the bulk of Indian QA listings; filter for automation frameworks you already know, since manual-only roles are shrinking and automation exposure is what recruiters shortlist on.

Related prep

Qa Engineer Hr Round Practice · Software Engineer Technical Round Practice · Software Engineer System Design Interview Practice · Software Engineer Coding Round Practice

Reading about it isn't practice.

Run a real AI mock interview built from your CV and a live job description — scored feedback on your answers, pace and filler words.

Start your free mock interview →