I architect backend systems that don't fall over.

I care about scalable backend architecture — how a system is put together, why it holds up under load, and what breaks first when it doesn't. Concurrency, data integrity, and failure modes are more interesting to me than any single framework.

Recent work centers on Node.js and TypeScript for high-concurrency fintech systems and multi-seller digital commerce infrastructure — payment flows, inventory consistency, and APIs that stay correct under concurrent writes. I came up through PHP / Laravel and Spring Boot / Java, and those still shape how I model data, write migrations, and reason about race conditions. I've also worked with Go on smaller services, though Node.js/TypeScript is where most of my recent, production-grade work lives. PostgreSQL and MySQL both show up depending on what the problem needs.