About Me
I'm Ritesh
Full-stack engineer in Kathmandu. Four years shipping production web applications, most of it in Next.js, NestJS, and PostgreSQL. The last year has been LLM systems: retrieval, embeddings, document extraction.
I work with teams anywhere. What follows is how I work, where I've worked, and what I'm looking for next.
How I got here.
What followed was unglamorous. An unpaid internship at Lancemeup in Patan, a phrase that contains its own review. Tutorials at 1.5x. Stack Overflow answers from 2013. Typing out code I did not understand until one day I did, which is a thing nobody warns you about: comprehension arrives about six weeks after the muscle memory, and there's no ceremony. Nobody sends a certificate. You just stop googling the same thing.
Then Azminds, where I stopped being someone who could build a page and became someone who could ship a thing. I got handed Yacht Cloud, already built and thoroughly over-engineered. The frontend server bill alone was $500+ a month for a few hundred users. I rewrote it in React and got that number down to something you wouldn't bother mentioning in a meeting. I'd been hired as a frontend dev and ended up in the Spring Boot backend too, which is how most of my range got built: someone had to, and I was there.
Then Milo Logic, where I got to own things end to end. Search that actually understood the question, running on the same Postgres everything else already lived in. A website builder so the people who write the content can publish it without waiting on a developer. Multi-tenant SaaS from requirements through deployment, plus the support calls afterwards, which teach you more than the build does.
It's also where I found out the hard part was never the code. Every project has one decision buried in it that everything else hangs off. It gets made in week one by someone in a hurry, and the rest of the year is spent working around it.
Gradsy came through a friend of a friend, which is how most good work arrives. Grad school applications, nine statuses, a workflow that everyone involved understood differently. I built it end to end. It's the thing I'd show you if you only had time for one.
These days the work is mostly LLM features, which is a job with two parts. The demo takes a day. Everything after the demo takes four months and is the actual work. I have an AI that writes code faster than I can and is wrong with total composure. Catching that is the whole skill now, and the only qualification is having personally shipped the same bug in 2022 and remembering how it felt.
Four years in, my competitive advantage turns out to be that I spent a long time being slow. Not the pitch I'd have picked.
How I work.
I care most about the interface, the interaction details most people ship past, but I own the backend all the way down when the work needs it. Owning delivery end to end, from architecture through deployment on AWS and Cloudflare, is the part of the job I actually like.
I use AI for most of it now. It writes code faster than I can and it's wrong with total composure, so every decision still gets reviewed to the bar I'd hold a senior hire to. The only qualification for catching a confident wrong answer is having personally shipped the same bug in 2022 and remembering how it felt.
Start at the constraint
Before any code, I map the domain and the failure modes. What breaks under concurrency, what has to stay correct when a job retries, what the deadline actually protects. The constraint decides the design; the feature list does not.
Ship the thin slice
The smallest version that runs end to end, deployed, with the boring parts boring: typed, migrated, observable. No abstraction until the second time I need it. You see something working early enough to change your mind cheaply.
Own it in production
Deployment, the bugs after it, and the documentation written while I build rather than promised for later. If an estimate is going to slip, you hear it the day I know instead of the week it lands.
Where I've worked.
Freelance Full-Stack Developer · Independent
Dec 2025 - Present- Gradsy: sole engineer on a study-abroad application platform in Next.js, NestJS and PostgreSQL on AWS. Built three role-scoped dashboards — student, counselor, admin — behind a default-deny API, enforced booking concurrency with database constraints, and made jobs retry-safe.
- Noveon: site for a Hong Kong investment firm on Next.js and a self-hosted Strapi CMS. Every page is a CMS entry, so marketing and compliance edit regulator-facing copy without a developer, and six investor pages render from two templates.
- Marti China: corporate site for an engineering company on Next.js with Strapi.
Full-Stack Engineer · Milo Logic
Aug 2025 - Aug 2026- Built enterprise multi-tenant architecture serving multiple organizations from one deployment, with tenant scoping at the data layer and custom domain support so each organization serves on its own domain.
- Shipped a block-based website builder and a drag-and-drop form builder, letting non-technical users compose pages, define fields and validation, and publish without a developer.
- Built revenue and analytics dashboards and master data models that keep reference data centrally managed while each organization maintains its own overrides.
- Architected shared React and TypeScript component libraries and design-system primitives adopted across 7 products by a 9-person engineering team, and cut JavaScript bundle size to reduce page load times.
Full-Stack Engineer · Azminds Services
Aug 2024 - Jul 2025- Yachtcloud: live multi-tenant yacht booking platform where each operator runs as its own business under one admin panel. Built the remaining booking flows and third-party integrations, then used Hotjar recordings and funnel data to find checkout drop-offs and simplify the flow. Tripled sales.
- Driving School Wiz: multi-tenant platform serving 5 driving schools, each on its own subdomain, with subdomain scoping on every request so one owner can run multiple schools without data crossover. Real-time instructor scheduling and assignment tracking.
Associate Frontend Developer · Azminds Services
Apr 2023 - Jul 2024- Built pension and revenue management modules for the Nepal Agricultural Research Council (NARC), a Government of Nepal agency, giving staff a single tracked record of pension disbursements and revenue entries.
- Shipped production React and Next.js features with Redux Toolkit and Redux Saga for complex asynchronous flows, migrated JavaScript codebases to TypeScript, and optimized fetching and caching with React Query.
Junior Frontend Developer (promoted from Intern) · Lanceme Up
Jan 2022 - Mar 2023- Delivered 4+ client React applications with Redux Toolkit and Material UI from Figma designs, including multi-locale builds with i18n over REST APIs.
What I reach for.
Next.js and TypeScript on the front, Node and NestJS behind them, PostgreSQL underneath. That is less a preference than a default I have to be argued out of. I have shipped enough of it to know where it breaks, and knowing the failure modes of a boring stack is worth more than a marginally better fit I would be learning on your schedule.
What I actually pick per project is the part that decides correctness. Retrieval work gets pgvector sitting next to the relational data rather than a separate vector store, because the query I need most often is a join. Anything with concurrency and retries gets idempotent writes and a story for the second attempt before it gets a screen. A marketing page gets Astro and static output, because a page nobody logs into should not ship a runtime.
The rest is knowing when to stop. React Query instead of a cache I maintain. Redux Saga only where the async flow is genuinely a state machine, which is rarer than the pattern's popularity suggests. No abstraction until the second time I need it. The full list of what I have used in production is on the resume — this is the part of it I would defend.
What I want next.
Work where the hard part is the system rather than the ticket queue: retrieval and extraction pipelines that have to be right, products where the interface is the argument, teams small enough that owning a feature means owning it from schema to deploy.
I work remote from Kathmandu with hours that overlap the US and Europe. If that is the shape of your problem, I will tell you honestly whether I am the right person for it.
Tell me the constraint and the deadline.
Thirty minutes on what you're building, what's in the way, and whether I'm the right person for it. If I'm not, I'll say so on the call.