Interview practice by role
QA / Test Engineer Interview Practice
QA and test automation interviews check that you can design a test strategy, not only write scripts. Expect questions on flaky tests, test data and where automation pays off.
200 practice questions5 topics5 typical rounds
How the interview usually runs
Loops differ by company. Treat this as a common pattern, not a fixed format.
- 01Screening callYour testing background, the frameworks you used and the products you tested.
- 02Testing fundamentalsTest levels, techniques, bug reports and how you decide what to test first.
- 03Automation framework deep diveSelectors, waits, page objects, fixtures and structuring a maintainable suite.
- 04Practical taskAutomate a login or checkout flow and explain how you would keep it stable.
- 05Behavioural roundWorking with developers on a disputed bug and improving quality in a team.
What interviewers probe
- Why tests are flaky and how you make them reliable
- Choosing what to automate and what to keep manual
- Test data, environments and isolation between tests
- Running tests in CI and acting on the results
- Writing a bug report a developer can reproduce
Common mistakes
- Using fixed sleeps instead of explaining proper waits
- Describing a tool but not the test strategy around it
- Automating everything without a view on cost and maintenance
Practice questions for QA / Test Engineer interviews
A starting set from each topic. Every question has a short answer, the full reasoning and the follow-ups interviewers ask.
01How does Playwright differ from Selenium?Mediumplaywright · selenium · test automation02How do you set up a Playwright project?Mediumsetup · playwright config · typescript03Why prefer getByRole and other user-facing locators?Mediumlocators · accessibility · role selectors04How does Cypress architecture work?Mediumarchitecture · runner · browser05How does Cypress compare with Playwright?Mediumplaywright · comparison · e2e testing06How does the Cypress command chain work?Mediumcommand queue · chaining · async07How does Selenium WebDriver work end to end?Mediumarchitecture · webdriver · browser drivers08How does Selenium compare with Playwright?Mediumselenium · playwright · tooling trade-offs09How do CSS selectors work in Selenium and where do they break?Mediumcss selectors · locators · dom10What is the full lifecycle of a Jest test?Mediumlifecycle · hooks · ordering11How should you handle setup and teardown in Jest?Mediumsetup · teardown · cleanup12When do you use jest.fn versus jest.spyOn?Mediumjest.fn · jest.spyOn · mocking13What is the difference between continuous delivery and continuous deployment?Mediumcontinuous delivery · continuous deployment · release14What is a build artifact and why should you build once?Mediumartifacts · immutability · reproducibility15How do you choose a version control branching strategy?Mediumbranching · git · release management
Reading is step one
Now say it out loud.
Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live QA / Test Engineer mock interview and get scored feedback on depth, clarity and confidence.