Manual work, removed
Billing and inventory ran on paper and memory. I instrumented a baseline first, automated the highest-cost processes, then measured the delta rather than asserting it. Month-end went from a scramble to audit-ready.
Turning messy operational reality into measured outcomes — global retail analytics at NielsenIQ, then rebuilding an entire business on automation and applied AI. I don't ship slideware. I ship the thing, then I measure what changed.
Usually replies within a day · Pune, India · Remote-ready across APAC, EMEA & partial US overlap
Every number here has a system behind it that someone still uses today. That is the only standard I hold work to.
Billing and inventory ran on paper and memory. I instrumented a baseline first, automated the highest-cost processes, then measured the delta rather than asserting it. Month-end went from a scramble to audit-ready.
Multi-market retail analytics for international FMCG accounts across North America, Europe and APAC. Concurrent multi-million-dollar contracts, sustained 95% CSAT, and a full cloud migration with zero client escalations.
Built a retrieval system over internal documents running entirely on local models — a deliberate cost, privacy and latency trade-off against hosted APIs. Staff query SOPs and vendor terms in plain language; nothing leaves the building.
Mechanical engineering taught me to model before building. Analytics taught me that the hardest part is agreeing what the number means. Operations taught me that neither matters unless someone actually uses it.
Claims are cheap. These are public, and the code is there to read.
The system behind the 70% figure. Scripted validation and reporting over a SQLite store, replacing a manual paper process and eliminating a recurring class of transcription errors.
View repositoryRAG over SOPs, vendor terms and product specifications, running on local models with MCP-connected tooling. Knowledge that lived in individual heads became queryable in plain language.
Explore GitHubFinal-year capstone: an automated mechanical handling concept designed to cut manual intervention and turnaround time. Mechanism design, functional reasoning and full technical documentation.
Ask me about itI use AI tools heavily and I'm precise about where they help and where they don't. That distinction is the job.
A number you didn't measure before the change isn't an outcome, it's a story. I instrument first so the delta is defensible when someone senior pushes back on it.
A system nobody uses is a hobby. I train, document, and iterate against real objections from non-technical staff until the thing is genuinely in daily use.
I build with AI daily. I also know exactly where it produces confident nonsense — and I design the verification step before I trust the output on anything workflow-critical.
Most delivery failures are definitional, not technical. Years of sitting between clients, delivery teams and engineering taught me to fix the disagreement before writing the query.
I'm looking for senior analytics, operations, or AI enablement work where ownership is real and the outcome is measurable. If that's the role you're filling, I'd like to hear about it.