AcadNet
Full-stack platformAn academic collaboration platform: students create study groups around a syllabus, share resources against its topics, and discuss them in per-group forums.
- Node.js
- Express
- React
- TypeScript
Kathmandu, Nepal · Open to work
Software Engineer.
I build backend systems, software products and AI-powered applications. The services, data models and infrastructure that sit under a product and keep it standing.
An academic collaboration platform: students create study groups around a syllabus, share resources against its topics, and discuss them in per-group forums.
The public website for Software Freedom Day Nepal, built and shipped for the Nepal Open Source Klub community event.
An AI-native development platform I'm building. It helps teams manage projects efficiently by integrating with their version control system.
Peer-to-peer file sharing between clients, with an Express service behind a React client.
A real-time chat application built on WebSockets, served from a Node.js and Express backend.
I work on the backend. Most of what I enjoy sits behind the interface: designing services, drawing the boundaries between them, deciding what a database should actually be responsible for, and making the whole thing observable enough that a failure tells you where it came from.
Lately that means AI-native development, treating models as another component in a system rather than the product itself, plus a steady interest in system design, microservices and distributed systems: replication, consistency, and what a service does when its neighbour disappears.
Outside paid work I spend time on developer tooling and infrastructure, and on the technical side of community events with Nepal Open Source Klub.
Built and led two projects: Digital Garage, and the integration of facial recognition into an existing system. I own the architecture on both, and handle operations alongside the build.
Continued work on the advertiser portal for dl.surf, letting advertisers run their advertising on the platform, and stayed responsible for its architecture.
Built the portal that lets advertisers advertise on dl.surf, and worked on its architecture.
Four roles at Nepal Open Source Klub between 2023 and 2025, from writing the technical side of events to leading the teams that ran them.
Led the team running NOSK events, managing the people involved and keeping the work moving across the event schedule.
Coordinated NOSK programs end to end, keeping schedules, scope and the teams behind them under control.
Led the technical team behind NOSK events, dividing up the technical work and supporting the people delivering it.
Contributing to managing events by handling the technical side of NOSK events, including developing websites, creating and handling registration forms, and managing and moderating Discord communities for smoother communication.
Topics I read about, build against and argue over. Each one is a slot that notes, experiments or write-ups can hang off later.
Building products where a model is a component of the system, not the whole of it.
Drawing service boundaries, picking the failure modes you can live with.
When splitting helps, when it just moves the coupling into the network.
Replication, consistency, and what happens when a node stops answering.
Task graphs, caching and keeping a multi-project repo fast.
Wiring models into existing services: inference paths, evaluation, and the failure cases.
Schema design, indexing, and reads that stay cheap as data grows.
Structure that survives the second and third feature request.
He is a software engineer who builds backend systems, software products and AI-powered applications. He currently works as an Associate Software Engineer at Workalaya.
Mainly Go, Python, JavaScript and TypeScript on the backend, with Node.js, Fastify, Express, Django and FastAPI, PostgreSQL, MongoDB and Redis for data, and React or Next.js on the frontend when needed.
Yes. He is based in Kathmandu, Nepal and open to software engineering roles, collaboration and interesting backend problems.
Email is the fastest way to reach him, at [email protected], or connect on GitHub and LinkedIn.
Software engineering roles, collaboration, open-source work, or any project with an interesting backend problem in it. Email is the fastest way to reach me.
[email protected]