+ years building.
Automation to enterprise.
Mumbai - and wherever the work is.
Currently a Solution Engineer at TestMu AI, working at the intersection of product, engineering, and customer success. I build things, fix things, and occasionally ship things that actually work.
About
I'm an engineer with + years in SaaS — working across automation, software development, and solution engineering. I've built internal tools, led teams, debugged production systems at 2am, and helped enterprise customers get real value out of complex products.
Currently at TestMu AI (formerly LambdaTest). Before that — PromptCue, SailPoint, BrowserStack, and Directi.
Resume
LambdaTest
PromptCue
SailPoint
BrowserStack
Directi
Driving adoption and technical success for enterprise clients — demos, integrations, and deep advisory across the product suite.
Built and led the engineering team from scratch. Owned roadmap, architecture, code reviews, 1:1s, and delivery cycles while managing a distributed remote team.
Forensic debugging across a complex SaaS architecture using OpenSearch, Grafana, and AWS. Cross-team escalation that actually worked.
Built 5 internal tools that improved team efficiency and visibility. Cut end-user tickets by 25% in 4 months. Named Subject Matter Expert for a key product area.
Front-end development, bug fixing, and documentation across Flock and Titan products. Where it all started.
Education
Projects
Tools and products built to solve real problems — mostly things I wished already existed.
An AI platform for interacting with multiple LLMs from a single interface. Built and led the engineering team from zero to launch.
Automated monthly shift scheduling for an entire support team, publishing directly to Google Sheets. Replaced a manual process that took hours each month.
Monitors support tickets blocked on other teams and auto-syncs their status based on linked Jira state — keeping SLA compliance without manual checks.
Pulls and parses BrowserStack session logs across test frameworks, highlighting the exact lines that caused failures. Saved hours of manual log digging per week.
Three-mode monitoring for support tickets — new SLA breaches, stale open cases, and cross-team blockers. Escalates automatically when thresholds are missed.
Off the clock
Flight simulators. Specifically the moment just before touchdown when everything either goes right or spectacularly wrong. I've logged more virtual flight hours than I'd like to admit.
Aviation. Not flying yet — but reading about it, watching it, understanding how a 400-tonne metal tube stays in the air. The engineering is quietly extraordinary.
Either deep in a side project I told myself would take an hour, or completely offline. There's rarely a middle ground.
Most automation problems are people problems in disguise. The script is usually fine. The process it's automating is the issue.
Contact
If you're hiring, building something interesting, or just want to connect — I'm reachable on any of the channels below. I try to respond within a day.