Senior Test Automation · Senior AI Test Automation
Interview field manual
Playwright / TypeScript first. API, data, CI and AI engineering in depth.
Prepare for the recruiter's 90-minute technical interview with precise answers, practical examples and honest career evidence. The vacancy and agenda remain unconfirmed.
10 min / 30 min / 2 hour study routes → Top 25 questions → 20 coding recipes →
Top eight last-minute priorities
- Promises and async
- Locators and retrying assertions
- API tests and lifecycle
- Fixtures and POM
- Auth and isolation
- Debugging CI
- GitLab quality gates
- AI agents and evals
P0 · Master first
The recruiter described a 90-minute interview with Playwright / TypeScript as the primary focus. The exact vacancy and agenda are unconfirmed. Prepare for the shared automation core first, then AI engineering a
JavaScript executes application logic; TypeScript adds compile-time constraints and emits JavaScript. Types do not validate network JSON at runtime. An async function always returns a Promise; await obtains its
Playwright Test is a runner with worker processes, projects, fixtures, assertions and reporters. It creates isolated contexts/pages per test by default; this does not isolate backend accounts. Locators describe
A framework organizes tests, resource lifecycles, service clients, data factories, configuration and evidence. POM encapsulates UI interaction; fixtures inject typed dependencies and manage setup/teardown. test
An API test validates a transport contract and business effects at a service boundary. HTTP success is evidence of request handling, not necessarily final workflow success. Read the OpenAPI/requirements, assert
An HTTP response can acknowledge work before an event-driven system finishes it. In the illustrative verification flow: request → producer → Kafka broker → consumer → database projection → status API → UI. A 20
storageState is a browser-state snapshot, not a permanent server session. Isolated contexts prevent cookie/local-storage collisions; they do not prevent two tests mutating the same account. Choose account scope
CI turns a commit into reproducible validation and evidence; CD promotes approved artifacts. A pipeline contains stages and jobs executed by runners. A quality gate must fail on meaningful critical defects and
A flaky test has inconsistent outcomes without a corresponding relevant code/environment change explaining the expectation. Investigate the whole system: product, test, infrastructure, data and timing. A retry
These recipes use hypothetical sandbox endpoints and UI contracts. They are documentation, not an included banking backend. Complete tests import test, expect from @playwright/test; scoped fragments explicitly
Answer in layers: define the concept, give a condition-based choice, show how it works, then name the failure mode and evidence. The bank below covers both automation roles. Each answer contains practical point
P1 · Senior depth
A test strategy explains which risks to cover, at which layers, with what evidence and maintenance cost. Pyramid/trophy models are heuristics, not percentage quotas. Choose the lowest useful layer that proves t
An agentic workflow lets a model choose tools, observe results and adjust its next actions toward a goal. Deterministic pipelines execute predefined steps. MCP integrates capabilities through a protocol; Skills
An eval is a repeatable measurement of AI behavior against explicit criteria. For generated tests, “compiles,” “passes,” “covers requirements” and “detects defects” are separate outcomes. Build an approved data
SQL validates stored facts and helps trace integration defects. Use joins and aggregates carefully: one-to-many fanout can duplicate totals. NULL means unknown, not empty string or zero. Prefer authorized read-
Separate three claims: strong Senior QA domain reasoning, actual automation coding experience, and a proposed AI engineering design. Use documented organizations and tasks; fill unknown personal actions/results
P2 · Awareness
Selenium / Cypress / WebdriverIO, BDD, accessibility, visual/performance checks, Docker/cloud · TestRail · LangChain / LangGraph / MLOps. These are supporting concepts; prioritize the P0 coding foundation.
Using this manual
Search titles, sections, code and answers with / or Ctrl/Cmd K. Use arrows and Enter to follow a result; Escape closes suggestions. Expand questions to rehearse answers, copy plain-text code, and use your browser's Print command for a readable chapter with disclosures expanded.
All content and interactions work from local files. Optional reference links open online documentation only when you follow them. Examples use hypothetical sandbox contracts. The website contains no application backend, credentials or tracking.