Tech with Jatin
Join 10,000+ Learners

Playwright TypeScript Interview Playbook

Not 300 questions. The 48 Playwright TypeScript questions SDET interviews keep coming back to.

Free: the 48 Playwright TypeScript questions SDET interviews keep coming back to, with clear answers, code and the mistakes to avoid.

Not 300 questions. The 48 Playwright TypeScript questions SDET interviews keep coming back to, with clear answers, code and the mistakes to avoid.

  • 48 pages
  • 12 parts
  • 48 questions

4.8 from 4 verified owners

  1. Enter your name and email
  2. Type the 6-digit code from your inbox
  3. Download the PDF

Knowing Playwright and explaining it are two different skills

In interviews, good testers lose marks because:

  • They describe what a feature is, not the problem it solves in a real project.
  • Scenario questions (two users side by side, a flaky test, a 3 second token setup) catch them without a ready example.
  • Their code works on their machine but they cannot explain why, for example why a fixture beats beforeEach.
  • They repeat the same weak answer interviewers hear all day.

Why 48 and not 300

Question banks with hundreds of entries spread your time thin and repeat the same idea in ten forms. These 48 are the questions SDET interviews keep returning to, each answered properly with code. You prepare what you are most likely to be asked, and you prepare it well.

After this playbook you can

  • Answer every common Playwright question in short points you can say out loud.
  • Back each answer with a small, real TypeScript example.
  • Handle scenario questions on contexts, locators, auto-waiting, fixtures, network mocking, auth, flaky tests and CI.
  • Avoid the common mistake listed under every answer.
  • Prove it with a hands-on task at the end of every part.

Look inside

The first 3 pages of 48, exactly as you get them. Swipe, then tap a page to enlarge it.

  • Preview page 4 of 48, locked
  • Preview page 5 of 48, locked
  • Preview page 6 of 48, locked

Get it free to unlock all 48 pages

Full table of contents

All 12 parts and 48 questions, exactly as they appear in the PDF. Tap a part to see its questions.

Part 1. Playwright Basics and Architecture4 questions
  1. Your company runs Selenium. Why are teams like yours moving to Playwright?
  2. One test must show an admin and a customer working at the same time. How do Browser, BrowserContext and Page make that possible?
  3. Which browsers does Playwright support, and what is the difference between bundled Chromium and the Chrome channel?
  4. How do you set up a Playwright TypeScript project from scratch?
Part 2. TypeScript for Testers5 questions
  1. Why use TypeScript instead of JavaScript for Playwright tests?
  2. What are interfaces and types, and where do you use them in a test framework?
  3. A test sometimes fails with "Target closed" and sometimes passes. You suspect a missing await. Explain what is going on.
  4. What are generics, and how do they help in a test framework?
  5. How do you manage environment config and secrets in a Playwright TypeScript framework?
Part 3. Locators5 questions
  1. Your element handle throws errors after the page re-renders. Why do Playwright locators not have this problem?
  2. Which locator strategy do you recommend, and in what order?
  3. How do you work with lists and tables using filter, nth and chaining?
  4. A card payment form sits inside an iframe and a cookie banner lives in shadow DOM. How do you automate both?
  5. How do you generate and debug locators quickly?
Part 4. Auto-waiting and Assertions5 questions
  1. What is auto-waiting, and what does Playwright check before it performs an action?
  2. What are web-first assertions, and why are they better than reading a value and checking it?
  3. Explain soft assertions, expect.poll and toPass.
  4. What are the different timeouts in Playwright, and what are their defaults?
  5. How do you do visual testing with toHaveScreenshot?
Part 5. Test Runner, Config and Projects4 questions
  1. Walk me through the important settings in playwright.config.ts.
  2. You must run one suite on Chrome, Safari and a phone viewport, after a login step. How do projects handle this?
  3. How do you organise and filter tests with describe, tags and annotations?
  4. How do you run tests in order when a flow truly needs it?
Part 6. Fixtures and Hooks3 questions
  1. Every spec file starts with the same 20 lines of setup. How do Playwright fixtures fix this?
  2. What is the difference between test-scoped and worker-scoped fixtures? What is an auto fixture?
  3. When do you use beforeAll and beforeEach hooks instead of fixtures?
Part 7. Page Object Model and Framework Design3 questions
  1. The same login locators are copied into 30 test files. How would you refactor this with the Page Object Model?
  2. How would you design a scalable Playwright framework? Walk me through the folder structure.
  3. Two parallel tests keep editing the same student account and fail at random. How should test data be managed?
Part 8. Network Mocking and API Testing5 questions
  1. How do you mock or change network responses with page.route?
  2. After clicking Place order, you need the order id from the API response. How do you capture it reliably?
  3. Can Playwright test a REST API without opening a browser? Show how.
  4. You want to create an order quickly through the API, then check it on screen. How do you mix API and UI in one test?
  5. What is HAR recording and replay, and when would you use it?
Part 9. Authentication and Sessions3 questions
  1. Every test spends 6 seconds on the login screen. How do you remove that cost?
  2. How do you test an app with several user roles?
  3. How do you handle OTP, 2FA and captcha in automated tests?
Part 10. Debugging and Flaky Tests4 questions
  1. A test failed in last night's run. Which tools do you open, and in what order?
  2. What is the Trace Viewer, and what does it show?
  3. Your checkout test is green on your laptop and red in CI every third run. Walk me through your investigation.
  4. Your suite has 15 tests that fail at random. Which causes do you look for, and how do you fix each one?
Part 11. Parallel Runs, CI/CD and Docker4 questions
  1. You set workers to 4. What actually runs in parallel, and what must your tests do to stay safe?
  2. Your suite takes 40 minutes on one machine. How do you split it across 4 CI machines and still get one report?
  3. Your team wants every pull request tested automatically. What does a Playwright pipeline look like?
  4. Screenshots differ between your laptop and CI because fonts render differently. How does running Playwright in Docker fix this?
Part 12. Playwright with AI3 questions
  1. Your manager asks how an AI assistant could explore the app and draft tests. Explain Playwright MCP.
  2. How would you use AI in your testing work without lowering quality?
  3. What are Playwright test agents (planner, generator, healer)?

Who it is for

This is for you if

  • Testers interviewing for Playwright roles where the team writes tests in TypeScript.
  • Selenium testers moving to Playwright.
  • Anyone who wants to check the quality of TWJ playbooks before buying one.

It is not for you if

  • Your team uses JavaScript. Get the Playwright JavaScript Interview Playbook.
  • You have never written a test. Start with the free Playwright lessons on the LMS first.

What is inside

  1. In every answerShort points to say out loud, a small real code example, the one line to remember and the common mistake to avoid.
  2. Try it yourselfA hands-on task at the end of every part.

PDF, 48 pages. Reads well on phone, tablet and laptop. Free instant download.

What changed
  • 2026-10-23. First edition: 48 questions in 12 parts with diagrams and practice tasks

From Jatin

Jatin Shharma

12+ years in test automation at Infosys, HERE Maps (originally Nokia Maps) and B2X. Client work for BMW and Audi, including self-parking car automation.

More about Jatin

Questions

Why only 48 questions?

Long question banks spread your time thin. These are the 48 questions SDET interviews keep coming back to, each answered properly, so you prepare what you are most likely to be asked instead of skimming hundreds.

Is it really free?

Yes. Enter your details and download it right away.

Who is it for?

Testers preparing for Playwright TypeScript or SDET interviews.

Do I need Playwright experience?

Basic TypeScript helps. Each answer explains the idea first, then shows code.

Will I get updates?

Yes. Download the latest version anytime from My purchases.

Why is it free?

So you can judge the quality before you spend anything. If it helps, the Coding Round Playbook and the Last-Minute Notes are the next steps.

Reviews

5 out of 5

The content is very good to understand.

Vidyasagar N.D, verified owner

5 out of 5

Consistently Outstanding Content

"The content was exceptionally well-structured and very helpful. It provided immense support for my interview preparation and continues to be a great resource. I have used similar content from you before as well, and the quality is consistently top-notch. The questions are interviewer-friendly, and the answers are detailed and easy to understand. Highly recommended!"

Kamal, verified owner

4 out of 5

It was good and very knowledgeable just asking if I only get subscription for playwright with JS and TS videos?

Harsh, verified owner

5 out of 5

Hi Jatin, Interview questions were so real time and scenario based. That is good part of playbook. Just a small suggestion, now a days in interview they are asking questions related to - AI with your test automation framework. How if you can add similar kind of questions it will supercharged us. At last, genuinely, playbook is awesome. Thanks

Dheeraj, verified owner

Get it free

Enter your name and email and the PDF comes to your inbox.