Automation interviews have moved beyond “What is Selenium?”. Panels now expect you to explain your framework, debug flaky tests and talk about CI. Many also ask how you use AI coding tools. This guide covers the questions that come up most for automation testers and SDETs in India, with answers you can adapt to your own project.
Tool details in this article were checked against the official Selenium, Playwright, Cypress and REST Assured documentation in October 2026.
Selenium questions
1. What is Selenium WebDriver, and which languages does it support?
WebDriver is Selenium’s API for controlling browsers through the W3C WebDriver standard. Official bindings exist for Java, Python, C#, Ruby and JavaScript.
2. What is Selenium Manager?
A tool bundled with Selenium 4 that automatically finds or downloads the correct browser driver, and the browser if needed. You no longer need a separate driver-manager library. The Selenium team lists third-party driver managers as a common outdated pattern in AI-generated code.
3. Implicit vs explicit vs fluent wait?
An implicit wait sets a global timeout for finding elements. An explicit wait (WebDriverWait) waits for a specific condition on a specific element. A fluent wait is an explicit wait with custom polling interval and ignored exceptions. Do not mix implicit and explicit waits, because the combined timeouts become unpredictable.
4. Why are Thread.sleep calls bad?
They waste time when the app is fast and still fail when it is slow. Replace them with waits for the actual condition, such as an element being clickable or a request finishing.
5. How do you choose locators?
Prefer stable IDs, data-test attributes and short CSS selectors. Use relative XPath only when needed (for example, finding by text) and never absolute XPaths copied from DevTools.
6. What is WebDriver BiDi?
A newer bidirectional browser protocol that lets Selenium listen for events such as console logs and network activity across browsers. Recent Selenium 4.x releases, including 4.49 in September 2026, continue to expand BiDi support.
Playwright and Cypress questions
7. Why might a team choose Playwright over Selenium?
Playwright includes its own test runner, auto-waiting locators, parallel execution, tracing, and Chromium, Firefox and WebKit support in one package. Selenium offers wider language support and a longer enterprise history. The choice depends on the team’s language, browsers and existing investment.
8. What is auto-waiting in Playwright?
Before acting, Playwright checks that the element is ready, for example visible, stable and enabled. This removes most manual waits.
9. How does Playwright handle authentication across tests?
Log in once in a setup step, save the storage state (cookies and local storage) to a file, and reuse it in other tests. This avoids repeating the login UI.
10. What are Cypress’s main limitations?
Tests are written in JavaScript or TypeScript only. Browser support covers the Chrome family, Edge and Firefox, with WebKit still experimental. Cypress 16 (September 2026) also removed some commands, such as cy.exec().
Flaky tests and reliability
11. How do you handle flaky tests?
Reproduce the failure, find the cause (timing, test data, order dependency, environment) and fix it. Quarantine tests you cannot fix immediately so they do not block the pipeline, and track flakiness over time. Retries should be a diagnostic tool, not a cure. Playwright 1.62 added an “isolated” retry strategy that reruns failures at the end of the run to separate real flakiness from parallel interference.
12. How do you stop parallel tests from clashing over shared data?
Give each test its own data (unique users or records), clean up after tests, and serialise only the tests that truly share a resource. Playwright 1.63 added named test locks for exactly this case.
Framework design
13. Explain your framework architecture.
Use layers: test cases; page objects or screen objects; reusable utilities (waits, API clients, data builders); configuration (environment, browser); test data; and reporting. Mention how it runs in CI and how results are shared.
14. What is the Page Object Model?
A pattern where each page or component is a class holding its locators and actions. Tests call methods like loginPage.login(user) instead of using raw locators. This reduces duplication and simplifies maintenance.
15. Data-driven vs keyword-driven vs BDD?
Data-driven runs the same test with multiple data sets. Keyword-driven builds tests from reusable action keywords. BDD (for example Cucumber) writes scenarios in Given/When/Then language shared with business stakeholders.
16. How do you run tests in CI?
Trigger on pull requests and merges, run in parallel (for example with Selenium Grid or Playwright workers), publish HTML reports and artefacts such as screenshots and traces, and fail the build on agreed conditions.
API automation
17. How do you automate API tests in Java?
With REST Assured, using given/when/then syntax to set request details, send the call and assert on status code, headers and body. REST Assured 6 requires Java 17 or later.
18. What do you validate in an API test?
Status code, response schema, field values, headers, response time, error handling for bad input, authentication and authorisation, and data persisted in the database where relevant.
19. PUT vs PATCH?
PUT replaces the whole resource. PATCH updates part of it. PUT is designed to be idempotent: sending the same request twice leaves the same result.
AI and modern practice
20. How do you use AI tools in automation?
Give an honest, specific answer. For example: generating first drafts of tests or data, then reviewing locators, waits and assertions. Mention known weaknesses. The Selenium project notes that agents often produce outdated code with sleeps and absolute XPaths. Playwright now offers built-in planner, generator and healer agents.
Coding round tips
Many automation interviews include a short coding task: reverse a string, find duplicates in an array, count word frequency, or parse a JSON response. Practise these in your chosen language without an IDE’s autocomplete.
Last-week checklist
- Draw your framework on paper and explain it in two minutes.
- Prepare one flaky-test story and one CI improvement story with numbers.
- Revise waits, locators, POM, TestNG or pytest annotations, and REST Assured basics.
- Run your GitHub project once more so you can share your screen confidently.
Frequently asked questions
Is Selenium still asked in interviews in 2026?
Yes. Selenium 4 remains widely used, with regular releases through 2026, and many enterprise projects run on it. Playwright questions are increasingly common, so knowing the main differences helps.
How much coding is expected for automation tester roles?
Enough to write clean framework code and solve simple to moderate problems. SDET roles at product companies usually add data structures and algorithms rounds.
Should I mention AI tools in an automation interview?
Yes, if you have used them, and explain how you review their output. Interviewers want to know you can use AI safely, not that you rely on it.
Official sources
- Selenium documentation
- Selenium: Using AI agents with Selenium
- Selenium 4.49 release
- Playwright: Getting started
- Playwright release notes
- Playwright: Test agents
- Cypress: Launching browsers
- Cypress changelog
- REST Assured 6.0 release notes

Leave a Reply