Technical screening questions
Ask for one example per question and listen for specifics.
- How do you write a good test case? A good answer: Clear steps, data, expected results and traceability.
- How do you prioritize testing under time pressure? A good answer: Risk-based testing on critical paths.
- What goes in a good defect report? A good answer: Steps, expected versus actual, environment and evidence.
- How do you test an API manually? A good answer: Requests, status codes, payloads and negative cases.
- What is the difference between regression and retesting? A good answer: Checking nothing else broke versus confirming a fix.
Quick screening questions
Use these when you have only a few minutes.
- How do you write a test case from a user story?
- Describe a critical defect you found.
- How do you prioritize regression testing under time pressure?
What separates the levels
Match the level to the requirement before you submit.
- Junior: executes test cases.
- Mid: designs tests and owns a module.
- Senior: leads test strategy.
Red flags
Any of these is a reason to probe further.
- Cannot describe a defect they found.
- No requirement traceability.
- Never wrote test cases.
Tools you should hear mentioned
A manual QA tester with real experience usually names several of these without prompting.
- JIRA
- TestRail or similar
- Postman
- SQL
- Browser dev tools
- Test documentation
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a manual QA tester screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.