5 QA Automation Interview Questions That Senior Engineers Still Get Wrong

Whether you're preparing for a QA Engineer or SDET interview, some questions trip up even experienced professionals. Here are 5 I've seen catch people off guard: 1. "Design a test automation framework from scratch — what's your architecture?" Most candidates jump straight to tools (Selenium, Playwright). Interviewers want to hear about: Page Object Model vs Screenplay pattern Test data management strategy CI/CD integration approach Reporting & failure analysis Tip: Start with the problem (what are we testing?), not the tool . 2. "You have 2 hours to test this API — walk me through your approach" The trap: candidates start writing tests immediately. Better approach: 5 min: Read the API docs/Swagger 10 min: Identify critical paths & edge cases 15 min: Set up collections (Postman/REST client) 90 min: Execute tests (happy path → edge cases → security) Remaining: Document findings 3. "What's the difference between a flaky test and a genuine failure?" This tests your debugging mindset: Flaky