I'm a software engineer who enjoys understanding systems from the inside out — how data flows, where bottlenecks form, and what it takes to make software fast and dependable at scale. I'm especially drawn to database internals and optimization: how queries are planned and executed, how data is stored and indexed, and what actually moves the needle on performance.
I care about writing code that is not only correct, but also intentional: clear architecture, thoughtful trade-offs, and solutions that hold up as complexity grows. Most of what I build lives on the backend — APIs, data layers, queues, caching, and the infrastructure that keeps them running smoothly.
Outside of shipping code, I'm usually reading, breaking things down to understand them better, or experimenting with ideas that push me to think more deeply about how great software is made.
Pinned repositories — newest first.
| Project | Description | |
|---|---|---|
| 1 | GraphScholar | Graph RAG knowledge base for research papers — Neo4j + MCP |
| 2 | lite-q | Persistent SQLite task queue for Node.js — zero external infra |
| 3 | property-listings-api | Production NestJS API with Redis caching & cursor pagination |
| 4 | Competitive-Programming | Algorithmic problem solutions in Java & C++ |
Open to collaborating on backend systems, database internals, and developer tooling.