Full Description

Role Overview

MyOperator is looking for a Senior QA Engineer (SDET) to strengthen automation coverage across our web, backend, and mobile surfaces — including the AI-driven flows that power our Business AI Operator platform. You'll join an existing QA team and take direct ownership of building and scaling Playwright-based automation, closing the mobile automation gap, and pushing backend/API testing rigour across the board.

This is a hands-on engineering role, not a manual-testing role. You'll be expected to write production-grade automation code, use AI tools like Claude to speed up test authoring and debugging, and work closely with engineering to catch issues before they reach customers running 12,000+ businesses on our platform.

About MyOperator MyOperator is a Business AI Operator platform that allows businesses, teams, and AI Agents to work in tandem for customer operations, i.e., handle Sales, Support, Escalation, Feedback, and Refund processes. With over 12,000+ businesses using our platform, we are the largest in the space.

MyOperator is built for people who want to work on ambitious problems at a meaningful scale. We value ownership, speed, critical thinking, and a bias for building things that create real customer and business outcomes. This is a high-expectation, high-learning environment where people are trusted to think independently, challenge ideas openly, move with urgency, and keep raising the bar as we build for long-term impact.

Key Responsibilities Design, build, and maintain end-to-end test automation frameworks using Playwright for web application regression, smoke, and release testing. Build and own mobile test automation (Android and iOS) using tools such as Appium, Espresso, or XCUITest — closing gaps where mobile flows currently rely on manual testing. Write and maintain backend/API test suites (REST/GraphQL) covering functional correctness, data integrity, and edge cases, including validation against the database. Use AI coding assistants (Claude and similar tools) to accelerate test case generation, script authoring, debugging, and test data creation. Instrument and use observability tools (Datadog, Lang fuse, or equivalents) to trace test failures back to root cause across services and AI-driven flows. Integrate automated suites into CI/CD pipelines, triage flaky tests, and keep pipeline signal reliable enough that engineering trusts it to gate releases. Partner with backend, frontend, and AI engineering teams during design and code review to catch testability gaps before code ships.

Requirements- Must Have 6–8 years in QA/SDET roles with hands-on ownership of test automation, not primarily manual testing. Demonstrable, hands-on experience building automation frameworks with Playwright — non-negotiable. Mobile test automation experience (Appium, Espresso, XCUITest, or equivalent) for Android and/or iOS — mandatory.

Strong backend/API testing skills: REST or GraphQL testing, request/response validation, and SQL for data verification. Practical experience using AI assistants (e.g., Claude, GitHub Copilot) in day-to-day test automation or debugging work. Comfortable working fully remote, Indian business hours, 5-day work week, with high individual ownership.

Requirements— Good to Have Experience with Lang fuse or similar LLM observability/tracing tools for testing AI agent or chatbot behaviour. Experience with Data dog or similar APM/monitoring tools to correlate test failures with production incidents. CI/CD experience (GitHub Actions, Jenkins, or similar) integrating and maintaining automated test suites. Prior experience testing conversational AI, chatbot, or voice bot products. Exposure to performance/load testing tools such as k6 or JMeter.

This Profile is Not For Testers whose background is primarily manual/exploratory testing with no hands-on automation coding experience. Candidates who expect a large, hand-held QA hierarchy — this role demands independent ownership within an existing but lean team. Anyone uncomfortable testing AI/LLM-based features where expected outputs aren't always strictly deterministic.