Read enough interview reports from QA candidates and a pattern jumps out. Nobody is being asked 75 obscure questions. They’re asked the same ten or so things, again and again, and then grilled on their own project.

Look at what candidates post on Glassdoor’s QA manual testing interview pages: describe your experience, write test cases for something everyday like Google Search or a WhatsApp call, write a few SQL queries, and explain the difference between web and mobile testing. One Infosys candidate summed it up simply: basics and real-time experience. Get those right and the interview gets much easier.

So instead of another giant list, here’s what actually comes up and how to handle it.

“Tell me about your experience”

This is the question that decides most interviews, and it’s the one people prepare least. Don’t recite your resume. Pick the project, say what the application did, what you tested, and one defect you’re proud of finding. Two minutes, tops.

Expect follow-ups on anything you mention. If you say “I did API testing”, be ready to explain what you checked in a response. Interviewers can tell within a minute whether experience is real.

“Write test cases for…”

A pen, a lift, Google Search, a login page, a UPI payment. The object doesn’t matter. They’re watching how you organise your thinking.

The candidates who do well don’t start listing cases straight away. They ask one or two questions first, like “Is this the mobile app or the website?”, then work through it in groups: does the main flow work, what happens when things go wrong, what about the edges, and is it secure and usable.

Take UPI payment at checkout. Main flow: pay and see the order marked Paid. Things going wrong: wrong PIN, not enough balance, closing the UPI app halfway. The case most people miss: the bank is slow, the payment sits on Pending, and you need to check that it resolves correctly and doesn’t create a second order. Mention that one and you’ll stand out.

The theory questions

Yes, they still ask them: the seven testing principles, verification vs validation, severity vs priority, the bug life cycle. Most Indian panels use the ISTQB Foundation syllabus as their reference.

The trick is to never stop at the definition. “Severity is impact, priority is urgency” is fine. Then add: “A spelling mistake in the company name on the home page is low severity but high priority.” That one example shows you understand it, which a memorised line doesn’t.

Same with boundary values. If a field accepts ages 18 to 60, just say: “I’d test 17, 18, 60 and 61.” Done. You’ve shown the technique instead of describing it.

SQL and APIs, even for “manual” roles

This surprises a lot of people. Plenty of manual testing jobs now expect you to check data in the database and look at an API response. You don’t need much: SELECT with WHERE, a JOIN, GROUP BY with COUNT. For APIs, know what a status code tells you and what you’d check in a response body. An evening or two of practice covers it.

The awkward situation questions

“The developer says your bug isn’t reproducible.” “You have one day to test the release.” These are about attitude more than technique.

For the first: retry on a clean setup, add the build, device, data and a screen recording, then offer to look at it together. Stay factual, not defensive. For the second: smoke test, then whatever changed in this release, then the flows that matter most to users. And say clearly at the end what you didn’t get to test. That last bit is what a test lead wants to hear.

The new one: AI

More panels now ask whether you use AI tools in testing. Be honest. Using it to brainstorm test ideas or generate test data is fine, as long as you say you review what it gives you. ISTQB has even added a separate certification for this, CT-GenAI. Our CT-GenAI vs CT-AI comparison covers whether it’s worth your time.

Don’t forget the HR round

Candidates regularly report being asked why they’re leaving, their current CTC and their expected CTC, sometimes in the very first round. Have honest, calm answers ready before you walk in. Our guides on “Tell me about yourself” and tester salaries in India help with both.

If you only have a weekend

Practise your two-minute project story out loud. Write test cases for three everyday things. Do an hour of basic SQL. Prepare one real defect story. That covers most of what you’ll face.

Thinking about moving beyond manual testing? Our manual to automation roadmap and automation interview guide are the next steps.

Leave a Reply

Trending