I am a technical lead based in Pune, India, and my background is deliberately unfashionable for someone working in AI: distributed systems, data pipelines, and production support. I learned what reliability means by being the person who got paged.
The largest system I have architected processes 520 million telecom parameters every fifteen minutes on Golang, Kafka, Kubernetes and PostgreSQL. Not because throughput is impressive on its own, but because a fixed cycle time teaches you something a demo never will: a system that accepts more work than it can finish does not slow down, it collapses. That lesson turns out to be the single most useful thing I know about AI agents.
Since 2022 I have been building AI products — conversational analytics over sensitive multi-tenant data, multi-agent systems on CrewAI and Model Context Protocol, text-to-SQL engines, retrieval pipelines, an agentic voice assistant, autonomous lead-generation agents. Some of it worked immediately. More of it worked after I stopped trusting the model with things a model should not be trusted with.
What I noticed across all of it: the teams struggling with agents were rarely struggling with AI. They were missing validation at boundaries, bounded resources, traceable failures, and any way to tell whether yesterday's change made things better. That is ordinary engineering discipline, and it iswhat I now do for a living — infour domains I have actually shipped in.
On working independently: this is a deliberate choice, not a gap between jobs. Reliability work is the part of AI engineering that consistently gets deprioritised inside a company, because features have an owner arguing for them and reliability does not. Working from outside means I get handed the problem directly, with a scope and a deadline, and I am not competing with a roadmap for attention. I take a small number of engagements at a time for the same reason.
I also work at the business end of things, which is unusual for an engineer and occasionally useful: I have led an initiative analysing customer data to find expansion opportunities, built AI systems aimed directly at pipeline and retention, and presented enterprise positioning strategy to a CEO. I mention it because it means I will ask what a reliability problem costs you, not just how to fix it.