Senior QA Automation Engineer - Bengaluru
Summary
Owns manual and automated QA across a startup's APIs, web apps, and AI agents: designing test coverage (Playwright-centric), hunting AI/LLM failure modes like hallucinations, managing defects in Linear, and owning release readiness. On-site role in Bengaluru for an early-stage AI household-management startup.
Own manual and automation testing across M’s APIs, apps, and AI agents. Build test coverage, hunt AI failure modes, and own release readiness.
Company Details
At M, we’re early, ambitious, and moving fast. We’re building a new category in how urban households function. We help households run smoothly through trained professionals, operational excellence, and technology-driven support systems.
Backed by Peak XV Partners, Blume Ventures and CRED, we’re reimagining how homes run, so people never have to think about chores again.
Website:
The Role
Break what we build before our customers can.
Manual & Automation Testing
Regular software either works or it doesn't. AI is murkier. It can be 95% brilliant and 5% confidently, spectacularly wrong. That 5% is your hunting ground.
We're building an AI copilot that actually runs households: ordering groceries, coordinating staff, juggling a hundred small daily decisions around the household. We need someone who reads "it works on my machine" as a personal insult, and who gets a little thrill from finding the bug nobody thought to look for.
Requirements
3+ years actually doing manual and automation testing.
A real grip on QA methodology, STLC, and the defect lifecycle.
Hands-on with Selenium / Playwright / Cypress, or API tools like Postman / RestAssured.
Enough Python, Java, or JavaScript to automate without waiting on anyone.
Comfort with Git, CI/CD, and SQL. You can read a pipeline and a query.
A working understanding of REST, JSON, and HTTP.
The instinct to ask "but what happens if…" before anyone else does.
Bonus Qualifications
You've tested AI / LLM or other non-deterministic systems.
You've built automation from a blank file, rather than just inherited someone else's.
You have strong opinions about flaky tests and how to kill them.
Responsibilities
You'll own quality across a real three-app system: APIs, apps and agents that don't always answer the same way twice.
Design test cases that bite: turn requirements and user stories into sharp, structured coverage, not checkbox theater.
Build and scale automation for web and APIs. We live in Playwright.
Run the full spread: functional, regression, integration, smoke and the exploratory testing where the juicy bugs hide.
Hunt AI failure modes: hallucinations, adversarial prompts, the "it did what?" moments.
Tame defects in Linear: log, track, reproduce, and pair with engineers through fix and verify.
Own release readiness: show up in sprint ceremonies like your name's on the box.
Level up our QA: push test strategy, coverage, and process forward instead of just following it.
Why Join M?
You'll be the quality bar for a product thousands of people lean on every day. Fast shipping, genuine autonomy and AI problems that don't have answers yet.
Work on diverse and challenging real-world problems.
Work alongside an ambitious team building a category-defining company from the ground up.
Build skills across customer experience, commerce, and operations.
Grow quickly in a high-ownership environment.
Job Details
Bengaluru, work from office.
Interview Process
Technical Discussion
QA Automation Round
Founder Discussion
Important Note
ClanX is a recruitment partner, helping TellM hire a QA Automation Engineer.
Skills
As published by recruitee · 17 questions · 6 written answers
Basics
Full name, Email, CV, Phone
Short answers (3)
- Please share your current CTC breakup, including Fixed, Variable, ESOPs, and other components, if any. Please stick to this format: Fixed: 15L, Variable: 3L, ESOPs: 5L with 4-year vesting
- What is your expected annual CTC? (INR)
- Help us with your LinkedIn profile link
Pick from a list (8)
- How many years of experience do you have as QA Engineer with Automation?
- Are you willing to relocate to Bengaluru?
- What is your notice period? (We are looking for candidates who can join within 30 days)
- Is your notice period negotiable?
- Do you have experience working at a product-based company?
- Are you a citizen of India and currently based in India?
- What does your current or most recent company mainly do?
- What is your current annual CTC range? (INR)
Written answers (6)
- Tell us about the product or services your current or most recent company offers. In 2–3 sentences, explain what it does, who uses it, and share the company/product website.
- [Mandatory] Share a Loom video walking us through test automation you personally built for a product or feature. Explain what you tested, your contribution, the tools and language used, how the automation was structured, and the key tradeoffs you made. Share the outcome and make sure the link is accessible. For confidential work, use a walkthrough without proprietary code or information.
- Describe one difficult bug you found through exploratory, integration, or regression testing. How did you uncover it, reproduce it, help engineers resolve it, and verify the fix?
- What makes your experience relevant to owning QA at TellM? Use a specific release to explain how you planned coverage and assessed readiness. Describe how you used Git, CI/CD, SQL, and your understanding of REST, JSON, and HTTP in that work, where applicable.
- Why do you want to leave your current role?
- Where did you find this job opportunity? (e.g., LinkedIn, Twitter, WhatsApp, etc). If someone referred you, please mention their name and contact number so we can thank them. (Write NA if not applicable).