LLM Product Engineering
End-to-end GenAI products on multi-tenant SaaS — from prompt design and structured outputs to streaming UIs, guardrails, and per-tenant token metering.
I’m Akshay, an AI Engineer. I design and ship LLM systems that hold up in front of real users — RAG systems, AI agents, and streaming LLM apps — with the evals, cost controls, and guardrails to match, backed by 9+ years scaling systems at Licious, Allo Health, and Practo.
9+ years of engineering across unicorns, health-tech, and 0-to-1 startups
About
Most AI demos never survive contact with real users. My work starts where the demo ends — the evals, cost controls, guardrails, and reliability that let a GenAI feature run in production in front of paying customers.
At Intellora AI I shipped five GenAI products across a multi-tenant SaaS platform, driving a 41% lift in lead precision and a 38% cut in LLM cost. Underneath it is 9+ years of distributed-systems engineering — the kind of foundation that turns an AI idea into something that actually holds up.
Prompts, RAG, agents, evals, and the streaming UI — I own the whole lifecycle, not a slice of it.
Golden datasets, CI regression gates, cost & latency tracking. If it can't be measured, it doesn't ship.
Unicorn-scale traffic at Licious, 0-to-1 at Allo Health, founding AI engineer at Intellora AI. The platform instincts are earned.
What I do
From the retrieval layer to the streaming UI — and the evals and cost controls that keep it reliable in production.
End-to-end GenAI products on multi-tenant SaaS — from prompt design and structured outputs to streaming UIs, guardrails, and per-tenant token metering.
Retrieval pipelines that stay grounded — hybrid BM25 + dense retrieval, semantic chunking, reranking, and answers with citations over Pinecone / pgvector.
Multi-step agents that actually finish the job — LangGraph state machines, function calling, tool use, MCP, and human-in-the-loop fallbacks.
The unglamorous work that makes GenAI reliable — golden-dataset evals, CI regression gates, model routing, prompt caching, and cost/latency tracking.
The platform under the AI — NestJS + Next.js services, event-driven Kafka / Pub-Sub, streaming over SSE / WebSockets, OAuth2 / JWT, and cloud-native AWS.
Shipping GenAI you can trust in front of customers — moderation, prompt filtering, output validation, PII & jailbreak mitigation, and read-only NL-to-SQL.
Approach
The process behind every product in the portfolio — the same one whether the deliverable is a chatbot, a retrieval pipeline, or a multi-step agent.
Every build starts with the user's job-to-be-done, the failure modes that would make it unusable, and a definition of "good" I can measure. The model choice comes last.
Retrieval, agents, structured outputs, and the streaming UI — a thin vertical slice in production early, then widened. I own the prompts and the platform alike.
Prompt and model changes go through golden-dataset evals and CI regression gates the same way code goes through tests. If it can't be measured, it doesn't ship.
Model routing, prompt caching, per-tenant budgets, and guardrails keep systems fast, safe, and affordable long after launch — on multi-tenant platforms serving real customers.
Selected work
Each one owned end-to-end — prompts, retrieval, agents, evals, and streaming UI. These are the outcomes, not the demos.
A conversational GPT-4o agent on the WhatsApp Business API with deep chat-session management — context persistence, token optimisation, and per-tenant metering — orchestrating tools via LangGraph.
An LLM lead-scoring agent that fuses structured CRM features with conversation embeddings in pgvector, using JSON-mode structured outputs and a custom eval harness on a 5K-row golden dataset.
A Claude Sonnet pipeline over long, multi-day customer conversations — hierarchical map-reduce summarisation, topic extraction, sentiment scoring, and action-item generation.
A multi-step planning agent on LangGraph state machines that decomposes intent, calls flight / hotel / POI APIs as tools, validates with Pydantic, and streams the itinerary over SSE.
LLM features woven across the CRM — auto-drafted follow-ups, deal summaries, next-best-action, and a natural-language query interface that generates guarded, read-only SQL.
The evaluation and cost backbone under every product — model routing across Haiku / Sonnet / Opus, prompt caching, structured-output retries, per-tenant budgets, and CI regression gates.
Curious how any of these are built? I write about the patterns on the blog
Track record
Nine-plus years across consumer platforms, real-time systems, and founding-engineer builds — the hard-won foundation under every GenAI system I ship.
Toolkit
Deep in the modern GenAI toolchain, grounded in production backend and frontend engineering.
Signal
Akshay took our AI lead-qualification from a rules-based guess to a system we actually trust. The 41% precision lift showed up directly in sales-accepted leads.
He shipped our entire telehealth platform from zero to production in four months and grew the team around it. Rare combination of speed and engineering discipline.
The LLM cost and reliability work paid for itself almost immediately — 38% off our model spend with no drop in quality, backed by evals we could actually see.
Feedback from teammates and stakeholders across the projects above.
FAQ
The things people usually ask about my work and how I build.
End-to-end GenAI product work: RAG and knowledge assistants, multi-step agents on LangGraph, streaming LLM apps, and the evals, cost controls, and guardrails that keep them reliable in production. I own the whole lifecycle — prompts, retrieval, orchestration, platform, and UI.
A feature real users depend on, not a demo. Concretely: golden-dataset evals wired into CI, structured-output validation, guardrails and PII handling, cost and latency observability, and per-tenant budgets on multi-tenant platforms. Reliability is designed in, not bolted on.
Golden-dataset evals wired into CI, model routing across model tiers, prompt caching, structured-output validation, and per-tenant token budgets with cost/latency observability. Every prompt or model change is gated the same way code is.
Claude, GPT-4o, and Gemini through LangGraph, LangChain, and the Vercel AI SDK; Pinecone and pgvector for retrieval; LangSmith and Langfuse for evals and tracing. Underneath: Next.js, NestJS and FastAPI, PostgreSQL, Kafka, and AWS — the distributed-systems foundation from 9+ years before GenAI.
The blog. I write about the patterns behind the work — retrieval design, agent orchestration, eval harnesses, LLM cost engineering — including the trade-offs I actually hit. It's the best way to see how I think.
Email is best. I'm based in Bengaluru and reply to every genuine message — whether it's a technical question about one of these systems, a collaboration, or something I wrote that you want to argue with.
Get in touch
A question about one of these systems, notes to compare on RAG or agents, or something I wrote that you want to argue with — tell me what you’re working on. I reply to every genuine message.