← All roles
Interview practice

QA Automation Engineer

2–5 years · Mid — Selenium / Playwright · API testing · Test design · CI integration · Python / Java · Debugging

0–2 years 2–5 years 5–8 years 8+ years
ownership A failure to automate 1 of 6
Describe a scenario where you refused to automate a particular test and why.
What a strong answer covers

Identifies a specific test with context; explains the reasoning behind the decision, including risks or costs; discusses the impact of manual testing on the project; reflects on the outcome and any lessons learned; avoids blaming external factors.

The follow-up you would get

What criteria would you use to evaluate automation in the future?

Could you have answered that?
scenario Flaky tests 2 of 6
You have several flaky tests in your suite that intermittently fail without clear reasons. How do you approach identifying and resolving these flaky tests?
What a strong answer covers

Isolates flaky tests to determine frequency and conditions of failures; reviews test logs and screenshots to identify patterns; considers environmental factors like timing or resource contention; rewrites tests to be more robust; implements retries for known flaky scenarios.

The follow-up you would get

What criteria do you use to decide whether to keep, fix, or remove a flaky test?

Could you have answered that?
ownership Test data management 3 of 6
Talk about a time when you faced challenges with test data and how you overcame them.
What a strong answer covers

Details the specific challenges faced with test data, including types of data; describes the strategies employed to address the issues; mentions collaboration with teams or tools used; includes metrics or outcomes that illustrate improvement; avoids vague descriptions.

The follow-up you would get

What would you change about your approach to test data management?

Could you have answered that?
scenario Ownership 4 of 6
You've been assigned ownership of a new feature from development through testing to deployment. Walk me through how you manage this process.
What a strong answer covers

Collaborates closely with developers during feature development; identifies key testing requirements early and integrates them into the workflow; conducts thorough testing and gathers feedback; ensures proper documentation and deployment procedures; monitors post-deployment for any issues.

The follow-up you would get

Looking back, what would you change about your approach to this ownership experience?

Could you have answered that?
scenario Debugging 5 of 6
A critical test case fails in production due to an unexpected UI change that was not communicated. Describe your immediate actions.
What a strong answer covers

Identifies the specific UI change that caused the failure; checks if the change was documented in the release notes; communicates with the development team to understand the context; updates the test case to reflect the new UI; assesses the impact on other related tests.

The follow-up you would get

How would you prevent similar issues from arising in the future?

Could you have answered that?
technical Test Design 6 of 6
You need to create automated tests for a web application with a complex login flow that has three different user roles. What strategy do you use to ensure you cover all scenarios effectively?
What a strong answer covers

Identifies key user paths for each role; uses parameterized test cases or data-driven testing; defines clear preconditions and expected outcomes; prioritises based on user impact and risk; documents test coverage explicitly.

The follow-up you would get

How do you manage the maintenance of these test cases as the application evolves?

Could you have answered that?
That is this set.

Load six more — you will get questions you have not seen first.

Give me six more →

Say your answer out loud before revealing. Reading the answer first feels like learning and is not.