Amrit Sapkota

Amrit Sapkota is a frontend developer based in Pokhara, Gandaki Province, Nepal. He has been on the frontend team at YHHIT since July 2024, building the interface of an e-commerce platform in React, Next.js and Tailwind CSS, and previously interned at Imark Pvt. Ltd. He holds a BSc.IT from Infomax College of IT and Management in Pokhara.

Yes. Amrit Sapkota takes client projects alongside his role at YHHIT and keeps the number small so both stay finished. The availability badge at the top of this site is maintained rather than decorative — when he is at capacity it says so. Enquiries go to amritsapkota010@gmail.com or through the contact form on this page.

React and Next.js are the daily tools, App Router included, with TypeScript on anything meant to be maintained and Tailwind CSS for styling. Also HTML and CSS, Node.js and Express for route handlers and server actions, MongoDB and PostgreSQL through ORMs like Prisma and Drizzle, Git, Figma, and VPS deployment. He uses LLM tooling for boilerplate and reviews it before a pull request.

Frontend is the paid track record — React, Next.js and TypeScript — but Amrit Sapkota is a modern frontend developer with full stack knowledge rather than a frontend-only one. He works across the MERN stack (MongoDB, Express, React, Node.js), is comfortable with PostgreSQL and ORMs such as Prisma and Drizzle, and is confident with VPS deployments, having handled deployment, server maintenance and monitoring at YHHIT. He is hired to own a frontend, and that backend knowledge is what stops the handover between the two from becoming your problem.

Yes — actively. Amrit Sapkota takes remote work outside Nepal, including the United States and the United Kingdom, on freelance, contract or full-time remote terms. Nepal Time is UTC+5:45, which overlaps almost completely with India and the Gulf, and comfortably with the UK, Central Europe, Singapore and Sydney. The US is the narrow one — a Pokhara evening is a US morning — so he holds fixed evening slots each week for those calls rather than claiming to be online around the clock.

There is no rate card. Amrit Sapkota scopes before quoting and bills per project, in NPR for clients in Nepal and USD for clients abroad. What moves the number: how many screens, how settled the design is, whether the API already exists or is being built alongside, whether content needs a CMS, and what performance targets have to be hit. A quote itemises those so you can see what changes if the scope does.

Every claim on this site has something attached you can open. The projects link to live sites you can load on your own phone. Run PageSpeed Insights on this page — a developer who sells performance should be willing to be measured on their own domain. The code is on GitHub under amrit-sapkota, the dated roles are on LinkedIn, and the blog is long-form writing that is hard to fake. Ask and he will put you in touch with a reference.