Zedfo
Multi-vendor e-commerce platform
A multi-vendor marketplace built to support multiple store registrations, product listings and order management.
Achyut Thapa, Full-Stack Developer
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.
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.
Responsive interfaces and frontend architecture in React and Next.js.
REST APIs and modular services on Node.js, Bun.js, Express.js and Elysia.js.
Relational and document models in PostgreSQL, MySQL and MongoDB.
Live updates, event-driven flows and background jobs.
Dashboards, approval workflows and role-based access control.
From understanding requirements through to deployment.
Multi-vendor e-commerce platform
A multi-vendor marketplace built to support multiple store registrations, product listings and order management.
A full-stack spiritual platform connecting devotees with temples in Uttarkashi, India, and Dolpa, Nepal.
An administrative platform for managing online PUBG and Free Fire tournaments.
Every technology links to the projects it was part of, so you can check the claim against the work.
Patan Multiple Campus, Tribhuvan University
Clear module boundaries, so a change in one place doesn't surprise another.
Code gets read far more often than it gets written. I write for the next person, who is often me.
Do the slow work outside the request where you can, and measure before optimizing.
Validate at the boundary, return predictable errors, and treat the contract as part of the product.
The schema outlives most of the code around it, so it deserves the most thought.
Authorization belongs on the server. The frontend's opinion doesn't count.
Loading, empty and error states are part of the feature, not cleanup for later.
Hiring, a product to build, or a system that needs untangling. Send a note and I'll reply by email.
achyut777thapa@gmail.com