// Interview Prep/Role-based prep/Automation QA
🤖 Automation QA interview prep
End-to-end, API, and CI automation — from the first spec to a reliable pipeline.
// WHO THIS IS FOR
For engineers interviewing for roles that centre on building and maintaining automated test suites — browser-based E2E, REST API testing, CI/CD integration, and framework architecture. Covers both individual-contributor and tech-lead scopes at the mid-to-senior level.
// SKILLS INTERVIEWERS EXPECT
Green = most frequently tested
// TYPICAL INTERVIEW ROUNDS
Technical screen
30–45 min with an engineer. Expect live coding or a take-home spec: given a URL, write a login test with assertions and stable locators. Interviewers look for auto-wait usage, meaningful assertions, and clean setup/teardown.
Framework design
Whiteboard or discussion round on how you structure a test suite — POM layers, fixture factories, config management, parallelism strategy. Come ready to justify trade-offs (e.g., Playwright fixtures vs class-based POM).
API & integration testing
Write REST API tests: auth flows, schema validation, chaining requests. May include contract testing concepts (Pact or schema matching) at senior level.
CI/CD & DevOps
GitHub Actions pipeline walk-through: trigger on PR, shard test runs, publish Allure/HTML report, fail the build on threshold. Senior roles add Docker-based environments and parallel grid configuration.
Behavioural / system design
Situational questions — flaky pipeline, legacy codebase with no tests, shifting deadlines, team resistance to automation. Demonstrates ownership, stakeholder communication, and quality advocacy.
// TOPICS TO STUDY
- Playwright fixtures, auto-waits, and web-first assertions
- Cypress command lifecycle and cy.intercept()
- Selenium WebDriver vs WebDriverIO vs Playwright differences
- Page Object Model and component-level abstraction
- Locator strategies: ARIA roles, data-testid, CSS/XPath trade-offs
- Test isolation: independent test state, shared vs per-test fixtures
- Parameterised tests and data-driven testing
- REST API testing: status codes, headers, schema validation
- Authentication flows in tests: cookies, tokens, session seeding
- Flaky test root causes and quarantine strategies
- GitHub Actions: workflow triggers, job matrices, secrets
- Parallel execution and sharding
- Allure and HTML test report generation
- BDD with Cucumber: feature files, step definitions, anti-patterns
- Shift-left strategy and testing in PR pipelines
// READINESS SELF-CHECK
How ready are you for a Automation QA interview? Score yourself 1–5 per competency. Be honest — it is a map of where to focus, not a test. Nothing is saved; print or copy it to track over time.
| Competency | 1–2 — weak signals | 4–5 — strong signals | You |
|---|---|---|---|
| Framework design | Writes scripts directly with no POM or fixture abstraction; a single UI change breaks multiple tests. | Architects layered POM or fixture factories, justifies trade-offs (e.g. fixtures vs class-based POM). | __/5 |
| Locator and sync strategy | Uses brittle XPath or CSS class selectors; adds hard sleeps to handle timing issues. | Selects ARIA roles and data-testid attributes; relies on auto-wait and avoids fixed delays. | __/5 |
| API testing | Tests only through the UI; no API-layer coverage in the test suite. | Writes chained REST tests with schema validation, auth seeding, and meaningful status assertions. | __/5 |
| CI/CD integration | Runs tests locally only; has not configured a pipeline, sharding, or a published report. | Configures PR triggers, sharding, report publishing, and fail-threshold gates end-to-end. | __/5 |
| Flake management | Accepts flaky tests or reruns the suite repeatedly without investigating root cause. | Diagnoses root cause (state leak, timing, environment), quarantines, and fixes systematically. | __/5 |
Reading your score — max 25
Your lowest two competencies are your study list — see Topics to study above and the Automation QA prep plan.
🗓️ Structured prep plan available
A day-by-day plan with study, practice exercises, and deliverables to get interview-ready.
More for this role coming soon
Hands-on assignments (test case writing, automation spec exercises) and scenario drills (flaky pipeline, legacy codebase) are coming soon.