I like taking an idea from a rough concept to something that actually runs.
That means working across the frontend, APIs, data layer, integrations, deployment, and the problems that show up once everything is connected.
I'm especially interested in AI systems where the engineering goes beyond an LLM call: retrieval, evidence, evaluation, and figuring out why a system fails.
|
A retrieval and verification pipeline designed to keep generated answers tied to source evidence. The interesting part Semantic retrieval alone missed information hidden behind document cross-references. Anchor follows those references, gates weak evidence, and verifies claims in the final answer. Multi-hop retrieval after adding citation following.
|
Retrieval
Verification
|
|
A full-stack expense platform with live dashboards, debt simplification, OCR scanning, and AI insights.
|
Frontend Integration Deployment |
const stack = {
// ⚡ Full-Stack
fullStack: [
"React",
"Next.js",
"TypeScript",
"Node.js",
"FastAPI",
"PostgreSQL",
"Docker"
],
// 🧠 AI Systems
aiSystems: [
"RAG",
"LLMs",
"Embeddings",
"pgvector",
"Retrieval",
"AI Evaluation"
]
};IDEA → BUILD → SOMETHING BREAKS → FIGURE OUT WHY → MAKE IT BETTER
I prefer projects that leave me with a better mental model of how the system actually works.
The first version usually answers "can this work?"
The debugging usually answers the more interesting question: "why did it work that way?"


