I ship the parts of AI systems that don't demo well.
Dhanush P — AI Software Engineer at Caasdi Global, Bengaluru. I build the retrieval pipelines, agent infrastructure, and data plumbing that keep AI products running after the demo ends.
How I got here
Math and statistics first, then software, then the parts of AI systems that don't show up in a tutorial.
I studied computer science, math, and statistics at Christ University, then went deeper into applied computing with an MCA at PES University. Somewhere in between, the math stopped being an abstraction and became the thing that decides whether a retrieval system returns the right six passages or a confident, wrong answer.
At Caasdi Global, a construction-tech startup in Bengaluru, I usually end up owning both ends of a problem: the AI system that reads a tender document, and the pipeline that gets it there reliably. I've built RAG pipelines and agent workflows, and spent just as many hours on the unglamorous parts — feasibility studies, competitive intelligence reports, invoice and payslip generators. Understanding a business well enough to automate its paperwork makes you better at the AI part too.
Outside work I'm building an agent observability platform from scratch — tracing, lineage, evaluation — mostly to understand what actually happens after agent.invoke() returns. I'm also working through the AWS and Databricks data engineering certifications, one gap analysis at a time.
What I actually work on
Six areas, none of them a skill bar.
Featured projects
Six builds. Flip through them, and open any one for the full breakdown.
Watch a request move through the stack
Three things I build, replayed as distributed traces. Pick one and watch which tools light up.
The path so far
How the pieces fit together
The pipelines behind the work above, simplified. They draw themselves as you scroll.
Let's build something intelligent.
Open to full-time AI, ML, and data engineering roles — and happy to talk shop even if there isn't one on the table yet.