Interview prep · Marathahalli
Playwright interview questions for SDET and automation roles
Playwright, Python, API and CI/CD questions used in Bangalore SDET interviews, plus how MufaSoft mock interviews work.
Why Playwright is the filter
SDET interviews in Bangalore now assume Selenium knowledge and use Playwright to see if you understand auto-wait, traces, fixtures, and parallel runs. Python + Playwright is a common combo alongside API tests.
Questions you should be able to answer live
They will ask you to debug a flaky locator, choose between role/text/test-id, explain browser contexts vs pages, and wire Playwright into GitHub Actions with artifacts. Expect API + UI contract tests, not only click scripts.
- How does Playwright auto-wait differ from Selenium implicit wait?
- When do you use APIRequestContext instead of the UI?
- How do you shard tests and still get one HTML report?
- Trace viewer vs video — what do you attach on CI failure?
Our SDET mock format
A 45-minute mock: 15 minutes framework design, 15 minutes live coding on a public site or API, 15 minutes CI and flaky-test strategy. You leave with a written scorecard, not a vague “do more practice.”
FAQ
- I only know Selenium. Can I still sit Playwright interviews?
- Yes. We map POM and waits you already know onto Playwright fixtures and then run mocks on that stack.
- Is interview support only for testing roles?
- No. Playwright is one track. We also prep Python, GenAI, backend, DevOps and more — see interview support in Marathahalli for all software roles.
Train at MufaSoft in Marathahalli
Next step: Automation testing in Bangalore, or talk to a counsellor in 5 minutes.