I build deterministic test systems for AI-era products.
Telecom-grade reliability with agent-shaped tooling. Currently keeping a T-Mobile US MVNE (Smartless Mobile) green for Lotusflare. Previously led a 6-engineer mobile-automation pod for L&T Technology Services.
role: QA Automation Engineer / SDET
stack: Playwright · Appium · MCP · Codex · Gemini 3
at: Lotusflare · ex L&T
based: Delhi, India
The numbers, in one row.
What changed for the teams I shipped with. Numbers a PM, lead, or CTO can use.
Selected case studies.
Tools, frameworks, and AI agents I built (or rebuilt) to remove manual toil from QA.
Notes from the QA console.
Industry POV and lessons from production. Long-form on Medium.
Working surface.
Things I'd reach for on a project today.
QA Automation Engineer / SDET · Delhi, India · 2.5y.
I'm Anmol — currently QA Engineer at Lotusflare working on a T-Mobile US MVNE (Smartless Mobile). Before that I led a 6-engineer iOS/Android/web automation pod at L&T Technology Services, covering two T-Mobile MVNE clients.
I gravitate toward the problems where QA stops looking like QA — building agents, designing test-data infrastructure, defining evaluation rubrics for LLMs, getting deterministic CI from non-deterministic upstream. The kind of work that doesn't have a Stack Overflow answer.
If you're at an AI-first company and need someone to make your release flow boring in the good way, say hi.
// passed in production · 2023–present describe('anmol', () => { it('ships AI tooling for QA', () => { expect(stack).toContain('MCP'); expect(agents).toBeProduction(); expect(toil).toHaveBeenReducedBy(0.67); }); it('leads QA pods', () => { expect(team.size).toBeGreaterThanOrEqual(6); expect(careerGrowth).toBeOwnedByLead(); }); it('survives outages', () => { expect(outages).toBe(7); expect(suite.color).toBe('green'); }); }); // ✓ 3 passed · 0 failed · time: 2.5y