Map the input
Understand resumes, schemas, documents, or user intent before a model touches it.
AI Engineer | Retrieval, agents, backend systems
I build AI tools around retrieval, agent workflows, FastAPI services, and clean product interfaces. The Projects page stays connected to GitHub, so new public repos can appear without rewriting the portfolio by hand.
Build style
I like building the parts where models meet real software: the data path, the service boundary, and the interface that makes the result easy to inspect.
Understand resumes, schemas, documents, or user intent before a model touches it.
Split the system into retrieval, planning, validation, and service boundaries.
Turn the backend into a product surface people can read, test, and trust.
Toolchain
Research notes
Research Note 01
An applied RAG system for resume analysis, ATS scoring, and job-fit feedback using local model components and retrieval.
Research question: How can an AI resume analyzer provide useful ATS feedback while keeping recommendations grounded in the user's actual resume and target role?
Research Note 02
A database copilot that frames natural-language analytics as a guarded planning, SQL generation, validation, and explanation loop.
Research question: How can a natural-language SQL assistant reduce friction for analytics while making generated queries safer and more explainable?
System thinking
Grounded answer flow for retrieval-first LLM applications.
Planner-tool-memory loop for multi-step intelligent automation.
Typed API surface around model orchestration and persistence.
Live GitHub corpus
SyncingNew public repositories can show up in Projects automatically. The strongest builds still keep extra notes for architecture, tradeoffs, and results.
Latest repository signalATS Resume AII focus on the practical layer: retrieval that finds the right context, agents with understandable steps, APIs with clear contracts, and interfaces that make the work easy to review.