Published 2026-04-22
Role Overview
My Operator's platform handles billions of real-time interactions — cloud call centers, IVR flows, Whats App APIs, AI voicebots, and a unified communication suite. As Manager QA, you will own quality across this entire product surface: from defining the QA strategy and automation architecture to taking accountability for production escapes and release confidence. This is not a sign-off role. You define what "good" looks like, build the systems to enforce it, and lead a team that treats quality as a product outcome — not a checkpoint.
You will work directly with Engineering, Product, and Dev Ops to embed quality at every stage of the development lifecycle. If you've scaled automation frameworks, reduced defect escape rates measurably, and built QA cultures where the team doesn't wait to be told what to test — this role is built around you.
About My Operator
My Operator 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. My Operator 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 Responsibility Areas
Own and enforce the quality bar across My Operator's full product suite — Cloud Call Center, IVR & Call Flows, Whats App API, AI Voicebots, and Unified Communication Platform — from sprint planning through production
Architect and scale automation frameworks across UI (Web/Mobile), REST and Graph QL APIs, and end-to-end integration flows; integrate these into CI/CD pipelines for continuous testing
Define, track, and improve quality metrics including defect escape rate, automation coverage percentage, test cycle time, flakiness rate, and Mean Time to Detect (MTTD)
Lead performance and load testing strategies using JMeter, k6, or Locust to validate system behavior under production-scale traffic conditions
Drive Root Cause Analysis (RCA) for production incidents and implement systemic fixes to prevent recurrence — not just mitigation
Lead, mentor, and scale the QA team; set clear performance expectations, run regular calibrations, and build an ownership-driven, bias-for-action team culture
Establish and maintain release entry/exit criteria, test environment parity with production, and structured test data management processes
Requirements — Must Have
5–8 years in QA with at least 2 years in a lead or ownership role managing a team of 3 or more
Hands-on expertise with one or more automation frameworks: Selenium, Cypress, Playwright, or Appium — with demonstrated ability to build or significantly scale a framework from the ground up
Proficiency in Python, Java, or Java Script for writing and maintaining automation code
Strong hands-on experience in API testing using Postman or Rest Assured, and CI/CD integration using Jenkins, Git Hub Actions, or Git Lab CI
Demonstrable track record of reducing defect escape rates or improving automation coverage — with numbers to back it
Experience with performance/load testing tools (JMeter, k6, or Locust) in a real production context
Requirements — Good to Have
Prior experience at a Saa S, CPaa S, or Cloud Telephony company; understanding of SIP, IVR, Vo IP, or Web RTC
Exposure to AWS, GCP, or Azure in the context of test environment management or deployment pipelines
Experience testing microservices and event-driven systems, including webhooks, async flows, and message queues
Familiarity with contract testing (Pact) or AI/ML-specific testing — chatbots, voicebots, NLP output validation
Knowledge of basic security testing principles, OWASP top 10, or chaos/resilience testing
This profile is not for
Someone whose primary mode is reviewing test cases and delegating execution rather than building and owning the automation stack themselves
Someone who treats QA sign-off as the finish line — this role is accountable for customer experience, not just green test runs
Someone who waits for complete requirements before starting and escalates ambiguity upward instead of driving clarity
