Automation Test Engineer
Practice Automation Test Engineer questions on Playwright, Selenium, Cypress, locators, waits, API tests, CI pipelines and flaky test fixes.
- Questions
- 100
- Interview Qs
- 30
- Judged problems
- 111
- Skills
- 9
About the role
An Automation Test Engineer writes code that tests software automatically. Instead of clicking through the app by hand for every release, you build test suites with tools like Playwright, Selenium or Cypress for the UI, and frameworks like REST Assured, pytest or Postman/Newman for APIs. These tests run in CI on every pull request, so the team learns within minutes if a change broke something.
A typical day includes writing new automated tests for features in the sprint, fixing tests that broke because the UI changed, investigating flaky failures, and improving the framework so tests are faster and easier to write. You need solid programming skills in JavaScript/TypeScript, Java or Python, plus a tester's mindset for edge cases.
As you grow, you design the overall test architecture: what to test at unit, API and UI level, how to manage test data and environments, how to run tests in parallel, and how to report results so developers trust and act on them.
Practise by level
Open the full question bank (100 questions) →Mock interview
Screening round
4 questions · 4 min each · pass 50%
mediumTechnical round
5 questions · 4 min each · pass 60%
hardFinal round
6 questions · 3 min each · pass 70%
Coding problems for automation test engineers
- Alphanumeric Palindrome Checkeasy
- Balance Point of a Beameasy
- Balanced Bracket Stringeasy
- Banner From Letter Tileseasy
- Best Single Trade Profiteasy
- Binary Classifier Metricseasy
- Can One Person Attend Every Booking?easy
- Cancel Adjacent Twinseasy
- Collapse Repeated Readingseasy
- Compare Release Versionseasy
- Compress Character Runseasy
- Constant Diagonals Grideasy
Skills in this track
Learning roadmap
- 1
Programming basics
Learn one language well: TypeScript, Java or Python. Cover functions, classes, async code, collections, error handling and unit testing frameworks like Jest, JUnit or pytest.
- 2
Testing fundamentals
Understand test levels, the test pyramid, test design techniques and how to write clear assertions. Good automation starts with good test cases.
- 3
UI automation
Learn Playwright or Selenium WebDriver: locators, auto-waiting and explicit waits, the Page Object Model, screenshots, traces and cross-browser runs.
- 4
API automation
Automate REST and GraphQL tests with Playwright request, REST Assured or pytest with requests. Validate schemas, auth and negative cases.
- 5
CI/CD and scaling
Run tests in GitHub Actions, GitLab CI or Jenkins, in Docker, in parallel and with sharding. Publish reports and artifacts for failures.
- 6
Framework design and reliability
Design maintainable frameworks with fixtures, test data factories, mocks and contract tests. Track and fix flaky tests and keep suites fast.
Top Automation Test Engineer interview questions
- Why do teams automate tests, and what should not be automated?
- Explain the Page Object Model and its benefits. Are there any downsides?
- What is the difference between implicit waits, explicit waits and auto-waiting?
- How do you run automated tests in a CI pipeline?
- When would you write an API test instead of a UI test?
- How do you choose locators for UI tests, and what makes a locator fragile?