Playwright Interview Questions — What SDET Interviewers Actually Ask in 2026
Real Playwright interview questions from actual SDET interview panels. Covers locator strategies, auto-waiting, CI/CD integration, API testing, trace viewer, and the Playwright vs Selenium decision that trips up most candidates.
Published 10 May 2026 • By Mitchell Agoma
It's 11pm. You've got a Playwright SDET interview tomorrow morning. You've written tests with Playwright for a year. You know page.locator(), you can write a fixture in your sleep. But then the doubt creeps in: what are they actually going to ask?
You open a search tab. "Playwright interview questions." 50 results. All different. Some say study locators. Some say understand the architecture. Some list 70 questions you won't have time to memorise. None of them tell you what interviewers at HMRC, Accenture, Nationwide, and the MoD really care about.
This guide is different. It's built from 20 years of sitting on both sides of the SDET interview table — asking the questions and answering them. It covers the categories interviewers probe, not just individual Q&As, so you can handle whatever variation comes your way. And it shows you exactly how SDET Interview Coach can drill you on these topics until they're second nature.
Why Playwright Questions Keep Changing — and Why Most Candidates Are Stuck in 2023
Three years ago, Playwright interview questions were straightforward: "What's a locator?" "How do you run tests in parallel?" "What's the difference between Playwright and Selenium?"
In 2026, that won't get you past the phone screen. Here's what's changed:
- Playwright now dominates enterprise hiring. In panels I've sat on at HMRC and the MoD, Playwright has replaced Selenium as the default framework for new test architecture. Interviewers expect depth, not surface knowledge.
- AI testing questions are in the mix. Interviewers are adding questions about Playwright MCP (Model Context Protocol), AI-generated locators, and self-healing tests. If you can't speak to these, you'll look behind the curve.
- CI/CD integration is table stakes. Running
npx playwright testlocally isn't enough. You need to explain how tests fit into a GitHub Actions pipeline, how you handle flakiness at scale, and what retry + reporter strategy you'd implement.
Are you prepared for the AI-testing questions that 40% of panels now ask? Most candidates aren't — which means those who are stand out immediately.
The 6 Categories Every Playwright Interview Tests
After conducting and sitting in hundreds of SDET interviews across HMRC, Nationwide, Accenture, and the Ministry of Defence, I've noticed a pattern. Playwright questions cluster into six categories. Interviewers don't ask one from each — but they will probe at least three. Master all six, and you can handle any panel.
1. Locator Strategy & Selector Hierarchy
"How do you decide which locator to use?" The trap here is saying "I use CSS selectors." The right answer discusses the Playwright locator hierarchy: role-based → text-based → test IDs → CSS/XPath as last resort. Interviewers want to hear you prioritise accessibility-first, user-facing locators over brittle DOM selectors.
2. Auto-Waiting & Actionability
"How does Playwright's auto-waiting work, and when does it fail?" Most candidates know Playwright auto-waits. Few can explain the actionability checks (visible, stable, enabled, receives events) or diagnose why a test that should pass is timing out. This is where mid-level candidates separate from senior.
3. Fixtures, Hooks & Test Isolation
"Walk me through your test setup pattern." Senior interviewers want to hear about custom fixtures, worker-scoped vs test-scoped setup, auth state reuse, and how you prevent test pollution. They'll push you on what happens when two tests share state and one fails.
4. CI/CD Pipeline Integration
"Your Playwright suite takes 20 minutes. How do you get it under 5?" This tests whether you understand sharding, parallel workers, retry strategy, failure triage with Trace Viewer, and how to balance coverage against pipeline speed. The most common trap candidates fall into: suggesting test deletion instead of intelligent parallelisation.
5. API Testing with Playwright
"When would you use request context instead of browser automation?" Playwright's API testing capabilities catch many candidates off-guard. If you don't know you can mock API responses, intercept network calls, and validate contract schemas without opening a browser, you're leaving capability on the table.
6. Playwright vs Selenium — The Decision Framework
"Why Playwright and not Selenium for this project?" Don't just list features. An interviewer testing for Lead SDET wants to hear a decision framework: when Playwright's auto-waiting and multi-browser support justify the migration cost, and when an existing Selenium suite with 5,000 tests should stay put. It's a tradeoffs question, not a features question.
3 Playwright Interview Traps Most Candidates Fall Into
These are the questions that make interviewers lean back in their chairs and wait. They're not trick questions — but they separate people who've only written tests from people who understand the engineering.
Trap #1: "Playwright auto-waits, so I don't need to handle waiting."
Auto-waiting covers actionability — but not data loading, API responses, or state changes from async operations. If you're testing a dashboard that fetches data after login, auto-waiting won't save you from a race condition. The winning answer discusses waitForResponse, waitForURL, and network idle strategies — and when not to use them (over-waiting bloats test time).
Trap #2: "I use the Trace Viewer to debug failures."
Using Trace Viewer is table stakes. The question that follows is: "How do you use traces at scale across 200 tests in CI?" The answer isn't opening traces one by one — it's about integrating trace-on-failure into your playwright.config.ts, pushing traces to an artifact store, and building a triage workflow that lets you diagnose without downloading 50MB snapshots for every failure.
Trap #3: "Playwright is better than Selenium, so we should migrate everything."
A Lead-level interviewer will immediately push back: "What's the cost of migrating 5,000 Selenium tests? What happens to the test knowledge in those scripts? How do you validate migration accuracy?" The right answer weighs ROI, proposes a strangler-fig migration (new features in Playwright, legacy tests in Selenium until retired), and acknowledges that some test suites aren't worth the migration cost.
The AI-Testing Questions That 40% of Panels Now Ask
By mid-2026, AI-in-testing questions have moved from "nice to have" to "expected." In recent interview panels at Accenture, I've watched candidates who aced the Playwright fundamentals lose offers because they couldn't discuss AI testing concepts. Here's what's coming:
Playwright MCP
"How would you use Model Context Protocol with Playwright?" Interviewers want to know you understand that MCP lets Claude AI control a browser directly — navigating, asserting, and debugging autonomously. The follow-up question is always about the human-in-the-loop: "When would you let AI run tests unattended, and when would you require human review?"
AI-Generated Locators
"Would you let an LLM write your locators?" The sophisticated answer isn't yes or no — it's about the review pipeline. AI can generate role-based locators from component code faster than a human, but they need validation against dynamic states, i18n variations, and accessibility tree changes. Describe the review process, not the generation.
Self-Healing Tests
"Your locator breaks because a developer renamed a button. What's your strategy?" Traditional answer: fix the locator. 2026 answer: implement AI-powered self-healing that maps broken locators to the closest semantic match, flags the change for human review, and learns from corrections over time. The key phrase interviewers want to hear: "confidence threshold."
If your Playwright interview prep hasn't touched AI testing concepts, you're walking in with a gap that 4 in 10 panels will expose. SDET Interview Coach has a dedicated AI in Testing category that covers these exact topics — with the depth and follow-up questions you'd face in a real panel.
How to Prepare: From Knowing to Performing Under Pressure
Knowing the answers is half the battle. Delivering them under interview pressure — when you've got 45 minutes to impress a panel of three — is the other half. Here's what works:
Practice Out Loud, Not in Your Head
Reading answers silently creates the illusion of mastery. Saying them out loud exposes gaps. You'll stumble on "auto-waiting actionability checks" the first five times. By the tenth, it'll roll off your tongue. SDET Interview Coach's mock interview mode forces this — 50-minute timed sessions with adaptive follow-ups that simulate the real thing.
Use Spaced Repetition, Not Cramming
If you cram Playwright concepts the night before, you might recall them in the interview. But you won't recall them on day one of the job — and interviewers can tell the difference between memorised answers and real understanding. The SM-2 spaced repetition system in SDET Interview Coach brings weak topics back at the right intervals so knowledge sticks.
Get AI Feedback on Your Answers
You can't grade your own interview answers. AI-graded feedback scores your responses on technical accuracy, completeness, communication, and code quality — showing you not just what you got wrong, but how to phrase it the way interviewers expect. It's like having a coach who's sat on 200+ interview panels giving you notes after every mock.
What a Real Playwright SDET Interview Looks Like — Timed Breakdown
Here's how most 60-minute SDET interview slots actually flow, based on panels I've conducted at HMRC, Nationwide, and consulting for Accenture:
Warm-Up & Experience Probe
"Tell us about a Playwright project you built." They're listening for framework ownership — did you set it up from scratch, or inherit an existing suite? Did you make architectural decisions? Expect follow-ups on why you chose specific patterns.
Technical Deep-Dive
Locator strategy, fixtures, parallel execution, CI/CD integration. You'll likely be asked to whiteboard a test for a given scenario. Don't just write the code — narrate your thinking. Interviewers are evaluating your engineering judgment, not your typing speed.
System Design & Tradeoffs
"Design a test framework for a microservices app with Playwright." This is where seniority is determined. Discuss fixture scoping, auth state management, test data strategy, reporting, and — importantly — what you'd do differently if the app had 50 services vs 5.
Behavioural & Culture Fit
STAR-format questions about flaky test incidents, disagreements with developers about test ownership, and how you mentor junior testers. The Playwright-specific angle: "Tell us about a time you had to convince a team to adopt Playwright."
Your Questions
Ask about their current test infrastructure, their biggest testing pain point, and what success looks like in the first 90 days. This shows you're thinking like an engineer who'll solve their problems, not just someone who wants a job.
How to Prepare for Your Playwright Interview — Starting Tonight
You don't need to memorise 70 answers. You need to understand the six categories, practice articulating your reasoning out loud, and get feedback on where your gaps are. Here's the 3-step plan:
- Download SDET Interview Coach and complete the 2-minute onboarding assessment. Select Playwright + TypeScript as your stack and your target seniority level. The app surfaces the questions that matter for your interview, not generic ones.
- Run one mock interview today. Pick the Playwright stack, set a 30-minute timer, and answer the questions out loud — even if you stumble. The AI feedback will show you exactly which of the six categories needs work.
- Use Job Match for your target role. Got a specific company in mind? Paste their job description into Job Match and get 50 questions tailored to their exact stack and seniority level. No more guessing what they'll ask.
The window for being early to AI-testing interview prep is closing. By late 2026, every SDET panel will expect Playwright candidates to discuss MCP, AI locator strategies, and self-healing tests. The candidates who prepare now will be the ones setting the curve — not chasing it.
If you're coming from a manual QA background, start with our guide on transitioning from manual QA to SDET — it covers the full career-change roadmap, including which framework to learn first and how long the journey realistically takes.
Ready to Transform Your Testing?
The AI Test Automation Playbook gives you everything you need: Playwright setup, Claude AI integration, MCP deep dive, 10+ ready-to-use prompts, CI/CD pipeline setup, and a 30-day implementation roadmap.
By Mitchell Agoma, Senior SDET & AI Testing Specialist with 8+ years of experience