Selenium Automation Internship Interview Questions for Freshers (with Answers)
By K. Boopathikumar, CEO & Founder · 16 November 2026 · 8 min read
Selenium internship interviews test whether you can write automation that is reliable, not just automation that passes once. Expect questions on locators, waits and framework design, and a small coding task.
WebDriver and locators
- What is Selenium WebDriver? A library that controls a real browser through code, used to automate tests of web applications.
- Which locators do you prefer and why? Stable ids or dedicated test attributes (data-testid) first, then CSS selectors. Avoid long absolute XPaths that break when the layout changes.
- findElement vs findElements? findElement returns the first match or throws an error; findElements returns a list, empty if none match.
- How do you handle a dropdown, alert and new window? Use the Select class for dropdowns, switchTo().alert() for alerts, and switchTo().window() with window handles for new tabs.
Waits and reliability
- Implicit vs explicit wait? An implicit wait applies to every find; an explicit wait waits for a specific condition (element clickable). Prefer explicit waits and do not mix the two.
- Why avoid Thread.sleep? Fixed sleeps make tests slow and still fail when the page is slower than expected.
- What causes flaky tests? Timing issues, shared test data, unstable locators and dependence on test order. Fix the cause instead of adding retries.
- What is StaleElementReferenceException? The element was removed or re-rendered after you found it; find it again after the page updates.
Frameworks and CI
- What is the Page Object Model? Each page is a class holding its locators and actions, so tests read like steps and a UI change is fixed in one place.
- TestNG or PyTest features you use? Annotations or fixtures for setup and teardown, grouping, data-driven tests with parameters and HTML reports.
- How do you run tests in CI? Run headless browsers in GitHub Actions or Jenkins on every push, store reports and screenshots of failures as artifacts.
- What is Selenium Grid? A way to run tests in parallel on many browsers and machines.
- What should you not automate? One-off checks, rapidly changing features and visual judgement that needs a human eye.
How to answer well in the interview
- Show a small framework on GitHub with page objects and a README.
- Explain how you made a flaky test stable.
- Know basic Java or Python well; automation is programming.
- Mention screenshots on failure and clear reports.
Next steps
- Study the free Selenium Automation learning path and take its module quizzes for a free certificate.
- Follow the Selenium Automation skill track from basic to advanced.
- Do real, reviewed work in a Selenium Automation internship and keep every project in your own GitHub.