Agentic-RAG
● completeEvaluation-driven retrieval and reasoning system over arXiv cs.AI papers.
AI Systems Engineer • Backend Engineer • Agentic AI Builder
I build AI systems and backend workflows that decide what to do next — not just what to say next.
Agentic AI development infrastructure for turning prompts into structured technical systems: architecture plans, API specifications, database schemas, orchestration flows, and engineering workflows.
A short preview of the work. The full project page goes deeper into architecture, tradeoffs, and implementation notes without making the landing page a long scroll.
Evaluation-driven retrieval and reasoning system over arXiv cs.AI papers.
Autonomous multi-agent orchestration framework for goal-driven execution.
Prompt telemetry, ETL, warehousing, and analytics platform.
I prefer agentic systems with explicit state over one-shot prompt chains. The useful part is not that a model can answer; it is that a system can decide whether to retrieve, clarify, use a tool, refuse, or continue a workflow.
The most underrated path in retrieval systems is the one that does not answer. Good AI infrastructure needs refusal paths, ambiguity handling, memory boundaries, and traces that make failure cases inspectable.
I run ablations on my assumptions. In Agentic-RAG, heavier reranking added latency and complexity without improving the benchmark. That kind of result matters because evaluation is how systems stay honest.
I optimize for systems I can reason about, debug, and evolve long-term.
Short engineering fragments behind the projects: what I pay attention to when a workflow needs to last longer than a single model response.
The UI can be minimal if the system underneath has clear routing, durable state, and recoverable execution steps.
A reranker, agent team, or memory layer is only useful when it improves behavior under real test cases.
Conversation, episodic, semantic, and domain memory should stay distinct so the system can explain what it used and why.
Prompt logs, node traces, activity logs, and audit trails are what make long-running AI workflows debuggable.
Not everything I've touched — what I reach for when I'm building.
Streak and contribution details render from the live GitHub streak endpoint.
I'm open to AI engineering roles, backend engineering roles, research collaborations, and serious technical problems.