← 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
scenario Debugging 1 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?
scenario Test design 2 of 6
You are tasked with testing a new feature that has conflicting requirements from different stakeholders. How do you prioritise and manage the testing process?
What a strong answer covers

List all conflicting requirements and their impacts; consult with stakeholders to clarify priorities and risks; design a test plan that covers the most critical functionalities first; document assumptions made during testing; prepare to adjust tests as requirements evolve.

The follow-up you would get

How do you handle situations where stakeholders change their priorities mid-testing?

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?
technical Test Data Management 4 of 6
Your tests rely on a large dataset, but they sometimes fail due to data integrity issues. How do you ensure reliable test data for your automation suite?
What a strong answer covers

Creates a consistent test data generation strategy; uses fixtures or factories to define test data; implements data cleanup routines to maintain integrity; considers using mocks or stubs for external dependencies; integrates data validation checks within tests.

The follow-up you would get

How do you handle versioning of test data when the application schema changes?

Could you have answered that?
scenario Ownership 5 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 Flaky tests 6 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?
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.