🎁 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 →
JD:SDET 3(4-6yrs exp) Location-Pune, India | Full-Time We are looking for an experienced SDET 3 to drive automation strategy, engineering quality, and release excellence across products. What Youll DoAutomation & Engineering Quality - Design and build scalable automation frameworks for web, mobile, API, and backend systems. - Establish tools and practices for automated integration, regression, and performance testing. - Ensure CI/CD pipelines enforce quality gates and automated validations. - Track and report metrics such as: - Test coverage - Defect leakage - Regression stability - Automation effectiveness - Release quality trends - Drive production readiness and release confidence. System Debugging & Reliability - Perform debugging and root cause analysis for production issues. - Troubleshoot databases, APIs, logs, and infrastructure-level issues. - Collaborate with support and engineering teams during production incidents. - Improve observability, reliability, and quality monitoring practices. Collaboration & Execution - Partner with Engineering and Product leadership to align on release quality and delivery timelines. - Collaborate cross-functionally with Backend, DevOps, Support, and Product teams. - Participate in architecture discussions, code reviews, sprint planning, and release governance. - Mentor engineers on clean coding, testing practices, and quality engineering principles. What Were Looking ForMust-Have Skills - 46 years of experience in SDET/QA engineering with leadership responsibilities. - Strong coding skills in Java, JavaScript/TypeScript, or Python. - Proven experience designing and scaling automation frameworks. - Strong understanding of backend systems, APIs, and distributed architectures. - Experience with: - API testing - Database validation - Logs and infrastructure troubleshooting - CI/CD pipelines - Strong debugging and root cause analysis capability. - Excellent stakeholder management and communication skills. - Strong mentoring and team leadership experience. Strong Technical Signals - Experience with WebDriverIO, Selenium, Playwright, Appium, or similar frameworks. - Exposure to K6, JMeter, or performance testing tools. - Solid SQL fundamentals; NoSQL familiarity is a plus. - Experience with Kafka, Redis, Kubernetes, Docker, or AWS. - Understanding of: - Distributed systems - Scalability - Fault tolerance - High-throughput systems - Production support and incident management readiness. Nice to Have - Experience scaling QA/SDET teams. - Exposure to fintech, ride-hailing, or consumer-tech platforms. - Experience working on high-throughput, low-latency systems. Compensation: 2,000,000.00 - 3,300,000.00 per year Work Location: Hybrid remote in Pune, Maharashtra (Pune, Pune District) .
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.