About me

Full-stack developer and Head of IT at Route2Uni International Group. I build backend-heavy CRM platforms and run the cloud they live on.

  • 50+staff on the systems I run
  • 30+university partner integrations
  • 7professional certificates
Hemraj speaking at a podium
Speaking at a student event

Part Developer. Part IT Lead.

Developer

  • Next.js, React, TypeScript & Tailwind CSS
  • Node.js, NestJS & FastAPI backends
  • PostgreSQL, Prisma, MongoDB & Firestore
  • Redis & BullMQ queues, REST API design
  • CRM architecture with RBAC & auth
  • iOS apps in Swift

IT Lead

  • IT strategy and roadmap for 50+ staff
  • AWS EC2, S3, IAM, VPC, CloudWatch, Route 53
  • Windows Server & Active Directory
  • Microsoft 365 & Google Workspace
  • Docker, CI/CD, Git & Linux
  • L1/L2 helpdesk on a 2-hour SLA
About me

I build software
teams use every day.

I'm a full-stack developer and Head of IT at Route2Uni International Group, building backend-heavy CRM platforms and the cloud infrastructure they run on.

I architect Node.js, NestJS and Next.js systems on PostgreSQL, Firebase and MongoDB, exposed through REST APIs, and run them on AWS. Right now I lead the CRM platform rebuild at Route2Uni (50+ staff, 30+ partner integrations) and a CRM and compliance portal for Dreams Care Homes in the UK, as both engineer and technical lead.

I started in IT support in 2023, joined Route2Uni in 2025 as IT Officer for the UK and Nepal teams, and have led its IT department since February 2026.

CRM architecture Full-stack development Cloud (AWS) IT infrastructure RBAC & MFA Project management NestJS & PostgreSQL Data & reporting
Hemraj Adhikari working on a laptop in a navy blazer
Hemraj AdhikariHead of IT · Route 2 Uni
Kathmandu, NP
30+university partner integrations
2+ yrsbuilding full-stack CRM platforms
7professional certificates, Google & IBM
50+staff using the CRM I built
How I work

Three habits behind every build

Start from the workflow

Before designing a screen I sit with the people who will use it. Most software problems turn out to be process problems nobody wrote down.

Ship small, then harden

A working version in weeks rather than months. Access control, backups and monitoring go in before it grows, not after something breaks.

Leave it maintainable

Plain code, written documentation and accounts in the organisation's name, so the next person can pick it up without me.

Beyond the screen

A few moments off the keyboard

Speaking to students, travelling and time outdoors. Click any photo to see it larger.

Next pageServices