About
I build web products end to end: the data model, the APIs, the background jobs and real-time layers, and the interface people actually touch. My work spans healthcare, e-commerce, education, transportation, esports and media.
A product doesn't stop at the API boundary, so neither do I.
Full-Stack Developer building digital products across multiple industries. I work on both sides of the stack, using modern tools, considered architecture and practical problem-solving to turn complicated requirements into software people can rely on.
Most of my work lives in React, TypeScript and Node.js, with Bun.js and Elysia.js on newer backends. I'm comfortable owning a product from both sides: understanding the requirements, designing the system, implementing it and getting it deployed.
Frontend
Responsive interfaces and frontend architecture in React and Next.js.
Backend & APIs
REST APIs and modular services on Node.js, Bun.js, Express.js and Elysia.js.
Data
Relational and document models in PostgreSQL, MySQL and MongoDB.
Real-time & async
Live updates, event-driven flows and background jobs.
Admin systems
Dashboards, approval workflows and role-based access control.
Product
From understanding requirements through to deployment.
The record so far.
Projects
Education
Patan Multiple Campus, Tribhuvan University
Pick a technology. See where it was used.
Every technology links to the projects it was part of, so you can check the claim against the work.
Languages
Frontend
Backend
Databases
ORM & Query
Real-time & Async
Auth & Validation
Tools
What I care about when nobody's looking at the code.
Clean architecture
Clear module boundaries, so a change in one place doesn't surprise another.
Maintainability
Code gets read far more often than it gets written. I write for the next person, who is often me.
Performance
Do the slow work outside the request where you can, and measure before optimizing.
Reliable APIs
Validate at the boundary, return predictable errors, and treat the contract as part of the product.
Database design
The schema outlives most of the code around it, so it deserves the most thought.
Security
Authorization belongs on the server. The frontend's opinion doesn't count.
User experience
Loading, empty and error states are part of the feature, not cleanup for later.