Technical screening questions
Ask for one example per question and listen for specifics.
- How do you decide what to automate? A good answer: Stable, repeatable, high-value paths first.
- How do you reduce flaky tests? A good answer: Waits, isolation, stable locators and test data.
- How do you structure a test framework? A good answer: Page objects or similar, reusable utilities and reporting.
- How do you test an API? A good answer: Contracts, status codes, payloads and negative cases.
- How do tests run in the pipeline? A good answer: Triggers, parallelism and reporting.
Quick screening questions
Use these when you have only a few minutes.
- What does your framework look like and who maintains it?
- How do you reduce flaky tests?
- What do you automate and what do you leave manual?
What separates the levels
Match the level to the requirement before you submit.
- Junior: writes tests within a framework.
- Mid: builds and maintains suites.
- Senior: designs the test strategy and framework.
Red flags
Any of these is a reason to probe further.
- Record-and-playback only.
- Cannot discuss framework design.
- No CI experience.
Tools you should hear mentioned
A QA automation engineer with real experience usually names several of these without prompting.
- Selenium, Playwright or Cypress
- Java, Python or JavaScript
- API testing tools
- CI/CD
- Test frameworks
- Git
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 QA automation engineer 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.