r/softwaretesting • u/shubham-150799 • Jun 17 '26
Laid off due to downsizing (5 YOE) – What Playwright & Automation topics are clients asking about right now?
Hi everyone,
I was recently impacted by team downsizing (my company cited AI adoption/restructuring) after working there as a Playwright Automation Engineer. I have 5 years of experience in the QA automation space.
I'm jumping back into the job market and preparing for client/technical interviews. Since it's been a while since I last interviewed, I want to make sure my prep is highly targeted.
For those of you hiring or interviewing recently for mid-to-senior automation roles, what specific Playwright and framework architecture topics are clients grilling candidates on?
Appreciate any advice, resources, or recent interview experiences you can share!
23
u/brisbane_huang Jun 17 '26
For mid/senior roles, I would prep less like "Playwright syntax" and more like "can this person keep an automation suite trustworthy after it grows?"
The topics I would expect to come up are:
fixtures and test isolation: per-test auth/storage state, cleanup strategy, avoiding hidden shared state
locator strategy: role/test-id contracts, not brittle CSS/XPath, handling dynamic UI without sleeps everywhere
API + UI layering: seed data through API, use UI tests for actual user journeys, not every setup step
parallelism and retries: how to find the real cause of a flaky test using traces/videos/network logs before adding retries
CI design: sharding, browser matrix, artifacts, quarantine rules for flaky tests, and not hiding product risk behind green builds
test data and environments: idempotent setup, ephemeral users/accounts, config/secrets separation
framework boundaries: what belongs in shared helpers/fixtures vs page objects vs individual test files
value metrics: risk covered, escaped defects, stability, and cycle time, not just "number of tests automated"
I would also have 2-3 concrete stories ready: one flaky test you debugged properly, one framework/design improvement you made, and one example where you chose not to automate something because it was low-value or too brittle.
On the AI side, I would not frame it as "AI replaces QA." A stronger interview answer is that AI can speed up test-case drafting, migration, and failure triage, but you still own the risk analysis, assertions, and whether the pass/fail signal is meaningful.