Skip to content
Nikesh Khatri
Kathmandu, Nepal

Software engineer who ships systems that handle money, people, and rules.

System 01 — Retail SaaS · Independent product

01 / 03

Mero Pasal

  1. 01Every shop shares one PostgreSQL database.
  2. 02Middleware sets the tenant; row-level security draws the wall.
  3. 03A query that forgets its filter gets zero rows — not another shop’s sales.
Live at mero-pasal.online ↗The hard part: Tenant isolation that survives my own mistakes →

System 02 — ERP · Independent product

02 / 03

Garment Manufacturing ERP

  1. 01Every invoice posts a balanced journal entry, in the same transaction.
  2. 02Debits and credits land together, so the books cannot drift.
  3. 03A void posts a reversing entry. History is never edited.
The hard part: Making every money movement post itself →

System 03 — HR & Payroll · At Goodwish

03 / 03

Attendance & Payroll SaaS

  1. 01Fingerprint and RFID terminals push punches on their own schedule.
  2. 02Idempotent ingest: a duplicated punch never becomes a duplicated day of pay.
  3. 03Nepali tax slabs, SSF and SST apply — then an accountant signs off.
The hard part: Hardware that does not care about your API design →

04More systems

A robot that talks back, a paper registry gone digital, and parking that prints tickets.

All 10 projects ↗

05

How I work

Opinions I have paid for, in production.

01

Own the problem, not the ticket

Requirements, implementation, tests, deployment, and the 11pm production diagnostic are the same job. I follow features through to the point where someone is actually using them without complaint.

02

Correctness before cleverness

Payroll that is off by one rupee is broken. A ledger that does not balance is broken. In finance-sensitive and permission-sensitive code I would rather write the boring, obviously-correct version and cover it with tests.

03

Learn the domain, not just the schema

Nepal income-tax slabs, SSF deductions, Darta/Chalani registry conventions, garment SAM costing — none of these are in the framework docs. I read the actual rules and translate them into workflows people recognise.

04

Small, reviewable, reversible

Changes backed by tests, logs and reproducible debugging evidence. I prefer a stack of narrow pull requests over one heroic branch, because the second kind is where production incidents come from.

05

Treat the API as the product

Predictable contracts, useful errors, backward-aware changes, typed OpenAPI schemas and documentation. The frontend team, the mobile team, and future me are all consumers.

06

AI as an accelerator, not an author

I use AI-assisted tooling for research, scaffolding and test generation, then review every line. The accountability for what ships stays with the engineer.

06

Capabilities

The stack, and the domain knowledge that makes it useful.

Languages

  • Python
  • TypeScript
  • JavaScript
  • SQL

Backend & APIs

  • Django
  • Django REST Framework
  • NestJS
  • Node.js
  • Celery
  • REST
  • OpenAPI
  • JWT / OAuth
  • WebSockets

Frontend

  • React
  • Next.js
  • Vite
  • Tailwind CSS
  • Accessibility
  • PWA

Data & Architecture

  • PostgreSQL
  • MySQL
  • Redis
  • Prisma
  • Row-level security
  • Multi-tenancy
  • Relational modelling
  • Double-entry accounting

Quality & Delivery

  • Pytest
  • Vitest
  • Playwright
  • GitHub Actions
  • CI/CD

Cloud & Operations

  • Docker
  • Nginx
  • Caddy
  • Azure
  • Google Cloud Storage
  • Firebase
  • Background jobs
  • Backups & health checks

Domain knowledge

  • Nepal income-tax slabs
  • SSF / SST payroll
  • IRD & CBMS billing
  • Bikram Sambat calendars
  • Khata (customer credit)
  • Darta / Chalani records
  • Bilingual (Nepali / English) UI

AI-assisted engineering

  • LLM tool & function calling
  • Agent workflows
  • Claude Code / Codex
  • Prompt engineering
  • Output review & evaluation

07

Experience

Where the work happened.

Jul 2026 — Present

Kathmandu, Nepal

Software Engineer

Independent products

Two products of my own, designed, built and deployed end to end alongside my role at Goodwish.

  • Mero Pasal: multi-tenant retail SaaS for Nepali shops, with every shop isolated by PostgreSQL row-level security, an online storefront and IRD-oriented VAT billing.
  • Garment Manufacturing ERP: order to ledger for a factory floor, covering merchandising, production, piece-rate payroll, VAT billing and double-entry accounting.
  • Sole engineer on both: architecture, the Django and React code, Docker deployment, backups and health checks.

Aug 2024 — Present

Lalitpur, Nepal

Software Engineer (Contract since Jul 2026)

Goodwish Engineering Pvt. Ltd.

Full-stack delivery across multi-tenant attendance and payroll, parking, file tracking, education, public-information and content-management products.

  • Delivered production features across multi-tenant attendance/payroll, parking, file-tracking, education, public-information and content-management products using Django/DRF, React, Next.js, TypeScript and PostgreSQL.
  • Designed REST APIs, database models, background jobs, integrations and role-based workflows for payroll, billing, payments, document routing, notifications, reporting and device attendance.
  • Implemented and maintained finance-sensitive workflows including tax calculations, invoicing, payment allocation, inventory valuation, accounting entries, audit trails and permission-safe exports.
  • Integrated payment gateways, ADMS/RFID devices, SMS/email OTP, OAuth, cloud storage, file processing, scheduled tasks and external services.
  • Improved reliability and security through automated tests, JWT refresh, authorization and tenant scoping, throttling, transaction handling, secret management, backups and production diagnostics.
  • Collaborated with engineers, designers and project managers; reviewed code, clarified requirements, documented decisions and owned features from implementation through deployment and support.

2020 – 2025

Kathmandu, Nepal

Bachelor of Science in Computer Science and Information Technology

Prime College, Tribhuvan University

Foundations in programming, data structures and algorithms, databases, software engineering, web development, networking and artificial intelligence.

Languages

  • NepaliNative
  • EnglishProfessional working proficiency

08Contact

Hiring for something with real rules in it? Let’s talk.

Open to new opportunities. I am most useful on products where correctness matters — billing, payroll, permissions, reporting, anything where “roughly right” is not right.

khatrinikace@gmail.com
Based in
Kathmandu, Nepal (UTC+05:45)
Phone
+977 9861139971
Currently
Software Engineer (Contract), Goodwish Engineering