Playwright Automation Tester

Burgeon It Services Pvt Ltd

INFull-timeMidPosted Jun 24, 2026

PlaywrightPostmanJenkinsJavaScriptTypeScriptAzureSQLCI/CD

Best fit for

This role is best for mid-level QA engineers with hands-on experience in Playwright, Postman / Newman, Jenkins, GitHub Actions open to working from IN.

Skills you need for this role

Detected from the job title, description, and tags.

Automation skills

Playwright — Modern cross-browser automation with auto-waits — increasingly the default at product companies.

API / backend testing

Postman / Newman — Standard tool for API exploration and shareable collections.

CI/CD and DevOps

Jenkins — Legacy CI still widely deployed — expect pipeline-as-code questions.
GitHub Actions — Default CI for teams on GitHub — YAML workflows and matrix builds.
Azure — Common in enterprise / Microsoft-shop QA roles.

Programming languages

JavaScript / TypeScript — Required for Playwright, Cypress, and modern front-end test tooling.
SQL — Data validation and back-office QA rely on solid SQL.

Domain & process

Agile / Scrum — You'll be expected to describe how you fit QA into short iterations.

Job description

Job Summary : We are looking for a skilled Playwright Automation Tester with experience in designing, developing, and maintaining automated test frameworks for web applications. The candidate should have strong programming skills, hands-on experience with Playwright, and a solid understanding of software testing methodologies.Roles and Responsibilities : - Develop, execute, and maintain automated test scripts using Playwright.- Design and implement robust automation frameworks for web applications.- Collaborate with developers, business analysts, and QA teams to understand requirements and create test scenarios.- Perform functional, regression, smoke, integration, and end-to-end testing.- Identify, track, and report defects using defect management tools.- Integrate automation scripts with CI/CD pipelines.- Analyze test results and prepare test execution reports.- Ensure test coverage and improve overall software quality.- Participate in Agile/Scrum ceremonies, including sprint planning, stand-ups, and retrospectives.- Optimize and enhance existing automation frameworks.Required Skills : - Strong hands-on experience with Playwright.- Experience with JavaScript or TypeScript.- Good understanding of software testing concepts and SDLC/STLC.- Experience with API testing tools such as Postman.- Knowledge of Git version control.- Experience with CI/CD tools like Jenkins, GitHub Actions, or Azure DevOps.- Knowledge of SQL and database validation.- Experience working in Agile environments. (ref: hirist.tech)

Job highlights

•Role: Playwright Automation Tester
•Company: Burgeon It Services Pvt Ltd
•Location: IN
•Type: Full-time
•Experience: Mid
•Seniority: Mid
•Posted: Jun 24, 2026

Key skills: Playwright · Postman · Jenkins · JavaScript · TypeScript · Azure · SQL · CI/CD

How to prepare for this interview

A 5-step prep plan tailored to this job's stack.

1Revise Playwright deeply — locator strategy, waits, parallelisation, and how you'd structure the framework from scratch. Playwright interview Q&A →
2Practice API-testing scenarios — auth flows, contract validation, and running collections in CI. API testing Q&A →
3Warm up on SQL joins, group-bys, and window functions — most QA rounds include a data-validation query. SQL Q&A →
4Do at least one AI mock interview end-to-end so you're comfortable narrating your answers under time. AI Mock Interview →
5Run your CV through the ATS review so it clears keyword filters for this role before you apply. Resume ATS Review →

Likely interview questions for this role

Tuned to the stack we detected on this job.

Q1.How does Playwright's auto-waiting differ from Selenium's explicit waits?
Q2.Walk through how you'd parallelise Playwright tests in CI with sharding.
Q3.How would you run a Postman collection inside a CI pipeline?
Q4.Write a SQL query to find duplicates across two columns and how you'd fix them in test data.
Q5.Walk me through a bug you found that shipped anyway — how did you handle it?