Experience
Where the work shipped
June 2026 – Present
Forward Deployed Engineer
TrueFoundry , Bengaluru
Partner with customers to ship production AI apps on cloud-native LLM infrastructure.
Turn platform capabilities into adoption paths and measurable business outcomes, not
slide-deck demos.
July 2023 – May 2026
Machine Learning Engineer
Chubb
Engineering Center India, Hyderabad
LLaMA-3.1 70B with LoRA/QLoRA and RAG: +25% accuracy, −15% drift.
Multi-agent planner / retriever / verifier: +18% factual grounding.
vLLM on AKS (A100/H100): −40% p95, +50% throughput, 10K+ daily
requests.
Built HawkHire, an explainable AI hiring copilot for internal recruiting.
June 2022 – June 2023
NLP Research Intern
Speech Lab ,
NTU Singapore
English–Malay code-switched language models: +20% over baselines.
Published multilingual and code-switching work across ACL-adjacent venues.
2019 – 2023
B.E. Electrical & Electronics
BITS Pilani, Pilani Campus
Foundations in systems, ML coursework, and applied software projects.
Featured work
tracesage
Local-first tracing for LangChain and LangGraph agents: one callback, a live graph, no
cloud account.
Fig. 1 Live agent topology, drawn from a single LangChain
callback: agents, MCP tools, and LLM nodes with the run timeline beneath.
Problem Hosted tracers work well, but reaching for a cloud account to debug an
agent at your own desk is the wrong shape of tool.
Approach Capture the LangChain callback stream, store each run in SQLite, and
render a live graph and timeline locally. Prompts never leave the machine. A crash-safe
handler, MCP tool-source attribution, a pytest fixture, and optional OpenTelemetry export
round it out.
Outcome pip install "tracesage[langchain]" then
tracesage demo. MIT-licensed and in beta; picked up by
Python Weekly #750 .
Documentation
Source
PyPI
Python · LangChain · LangGraph · MCP · OpenTelemetry · SQLite
Writing
Notes on agents & tracing
Longer-form pieces on tracesage and local-first LangGraph observability.
Substack · 21 June 2026
Why local-first tracing matters for the desk-debug loop, and how two lines of
tracesage replace a wall of print statements without a cloud account.
Substack · 16 June 2026
A walkthrough of the product: topology, run trace, MCP attribution, the pytest
fixture, and when a hosted tracer is still the right call.
Python Weekly · 18 June 2026
tracesage listed under Interesting Projects, Tools, and Libraries.
Along the way
Earlier projects
Coursework and side projects that led into production ML and research.
Skills
Stack I reach for
Grouped by how I actually use it: model work, serving, and research.
Models & agents
Python, PyTorch, Transformers, LoRA and QLoRA, RAG, multi-agent systems, LangChain and
LangGraph, Hugging Face.
Serving & infra
vLLM, Kubernetes, AKS, Azure, AWS, Docker, OpenTelemetry, Databricks, CI/CD.
Research
Natural language processing, code-switching, evaluation benchmarks.
I care about systems that survive real traffic, and methods that hold up under scrutiny.
Ship
Production over theatre. Latency, accuracy, and grounding under load, not prototype
applause.
Prove
Measure what matters. Quantify the impact so a team can trust the system rather than
the pitch.
Publish
Sharpen the method. When a problem needs a better evaluation or a better model story,
write it down.
Open to collaborations on LLM tooling, production AI systems, agent observability, and
applied NLP. Best reached by email.
Kshitij Gupta
mailguptakshitij@gmail.com