🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
This is a remote position. We are looking for a QA Engineer (Playwright) Senior II who is not just an automation engineer, but also a robust coder and critical thinker. This role requires a solid foundation in programming fundamentals and fluency in TypeScript/JavaScript, with a proven record of implementing clean, maintainable, and scalable test automation frameworks. You will work on mission-critical systems in a fast-paced Agile environment, collaborating with cross-functional teams to ensure seamless quality delivery. The role involves designing and optimizing modular automation frameworks, automating tests across APIs and backend systems, integrating automation pipelines into CI/CD, leading test strategies, maintaining test stability, owning release documentation, and mentoring junior engineers on best practices. Note: We are looking for an immediate joiner. Candidates who can start right away or within a very short notice period will be given preference. Requirements - 7+ years of total experience in Quality Assurance - Strong programming background with expertise in JavaScript/TypeScript, including core concepts, design patterns, data structures, and debugging - Minimum 1-2 years of hands-on experience using Playwright with TypeScript/JavaScript - Proven ability to write well-structured, production-quality automation code - Experience designing, building, and optimizing scalable automation frameworks - Practical experience in API testing using Playwright, Axios, or similar libraries - Backend validation expertise with SQL/PostgreSQL/MySQL - Experience integrating automation pipelines with CI/CD tools such as GitHub Actions, Jenkins, or CircleCI - Strong problem-solving skills with the ability to take ownership in dynamic product environments - Proven experience maintaining test stability, debugging failures, and driving continuous improvements - Ability to lead test strategy discussions and contribute proactively in Agile ceremonies - Ownership of test plans, strategies, and release documentation - Experience mentoring junior team members on coding, automation, and testing best practices - Deep understanding of QA methodologies, Agile principles, and the software test lifecycle - Nice to have: experience with cloud environments (AWS preferred) - Nice to have: familiarity with Docker/Kubernetes and microservices - Nice to have: exposure to performance and security testing tools and strategies. Disclaimer : This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.