SDET-I — Quality Engineering
Engineering · Platform Quality Engineering
📍 Noida · 5 days WFO 🕐 Full-Time · 2–3 Years
Hiring Drive · 31 October 2026 · On-site assessment and panel in a single day.
The team you're joining ships code that engineering teams at Wells Fargo, JPMorgan, Meta, Louis Vuitton, and Sephora run their tests through.
The QA tooling you build here isn't internal. It's the product.
That's not a stepping stone to a dev job. It's a career most engineers never get to have.
READ THIS FIRST
Three honest filters, because we'd rather tell you now than at the offer stage.
- If you're planning to use QA as a route into a dev role within the next 12 months — this isn't it. We invest heavily in people who want to own Quality Engineering as a long career, not a stepping stone. Dev-switch intent is a kind thing to flag early; we'll help you find a role that fits better.
- If your QA experience has been running scripted test cases on behalf of someone else's product at a services company — this role will be harder than you expect. We hire from product companies because the muscle is different: owning quality for your own company's product shapes the way you think.
- If you're excited about building test automation that becomes open-source tooling thousands of engineers rely on — keep reading.
THE MISSION
We aren't automating scripts — we're deprecating the era of manual-heavy testing entirely. TestMu AI is building the world's first AI-native platform where Agentic Intelligence autonomously plans, authors, and self-heals the entire Quality Engineering lifecycle.
The name "TestMu" comes from our community conference — our users and our team are the heartbeat of what we build, not an audience.
You're joining the Quality Engineering team that keeps the platform itself honest. You'll write the tests that catch bugs before customers do, build the frameworks the rest of engineering ships with, and over time, own a slice of the product end-to-end. The QA craft, done the way it should be done.
THE PILLARS OF IMPACT
🚀 Product QE Ownership (50%)
- Own test automation for a core product surface — write robust, maintainable tests that catch regressions before they ship.
- Debug the hard bugs. Not just the ones that fail CI — the ones that fail at 3am in production for a customer in Austin.
- Raise the quality bar for your surface quarter over quarter. Flakiness goes down. Coverage goes up. Confidence to ship goes up.
- Partner with engineers, product, and support to make quality a shared discipline — not a team QA inherits at the end.
⚙️ Platform & Tooling Craft (30%)
- Contribute to the internal QE frameworks the rest of engineering runs against. The code you write here is used by every team shipping product.
- Participate in our open-source work on Selenium and APM tooling. We're one of the few companies in India where "my pull request got merged into Selenium core" is a real line on your résumé.
- Build repeatable patterns — reusable fixtures, test harnesses, CI integrations — so quality compounds, not gets rewritten every quarter.
🧠 Learning & Growth (20%)
- Soak the product deeply. The best SDETs know what the product does better than most PMs. That's the bar.
- Get trained on the AI-native tooling we're building for the next generation of QE. You don't need to come in knowing LLMs — you need to come in curious and ready to learn.
- Grow into the next role. We hire SDET-I expecting you'll be SDET-II in 18 months, Senior in 3 years, and QA Lead or Manager QE after that — if you want it.
WHY THIS SEAT, RIGHT NOW
The real differentiators.
- Open-source credibility. We actively contribute to Selenium core and maintain APM tooling used by thousands of engineering teams around the world. Your work ships further than any product company you've worked at before.
- A product-first QE org. QA isn't an afterthought here. The platform we sell IS a quality engineering platform. Your craft is the company's core product.
- A clear growth path, promoted on merit. You'll see the full ladder on day one. Nobody at TestMu AI gets promoted on tenure — only on the work.
- Real training in AI-native QE. We're deploying Agentic Intelligence into our own QE lifecycle. The agents you learn to work with internally are the same agents our customers buy.
THE AI YOU'LL BE TRAINED ON
You do not need to come in knowing LLMs. You need to come in curious.
Over your first six months, you'll be trained on Claude, LLM-powered test generation, and the agentic workflows we're building into the platform itself. Our target is to agent away the repetitive parts of QE work — flaky-test triage, regression suite grooming, bug reproduction — so you spend your time on the hard, interesting problems that need an engineer's judgment.
The AI tooling is a multiplier for a solid QE foundation, not a replacement for it. If your QA fundamentals are strong, the AI side we'll teach you.
THE BAR
Signal: What you'll show us.
- QA fundamentals. You've written automated tests that actually caught bugs. You can tell us what makes a test flaky — and how you'd fix it.
- Product-company lens. You've worked on a product your own company sells to customers. You've felt the weight of a customer bug, not just a ticket in someone else's backlog.
- Career commitment to QE. You see Quality Engineering as a craft worth 10 years, not a stepping stone to Software Development Engineer. You can articulate why QE matters, and why you want to own it.
- Extreme Ownership: Takes full accountability for outcomes, not just tasks.
YOUR FIRST 90 DAYS
Structured. Specific. Honest about the ramp.
Days 1–30 — Soak.
- Deep onboarding on the product, the QE framework, and the open-source projects we contribute to.
- Shadow senior SDETs on real tickets. Learn how we debug, how we write tests, how we review PRs.
- Set up your dev environment, make your first (small) code contribution to the QE framework, raise your first bug.
Days 30–90 — Own.
- Pick up a core product surface. Own its test automation under senior guidance.
- Ship your first meaningful PR to one of our open-source dependencies — guided and reviewed.
- Begin training on AI-native QE workflows and start applying them in your day-to-day.
- Earn trust that lets you work with less oversight by day 90.
YOUR PATH
SDET-I → SDET-II → Senior SDET → QA Lead → Manager QE.
That's the ladder, written out so there's no guesswork. You move when the work moves — not when the calendar moves. Our best SDET-Is are SDET-IIs within 18 months. The ones who want to lead become QA Leads in 3–4 years. The end destination, if you want it, is owning the Quality Engineering function.
Click it. Be amazed. → testmuai-growth-path-beige.vercel.app/#/sdet-ii
