Lead Software Engineer building resilient, multi-region Kubernetes platforms and shipping 100+ production apps. I work across DevOps, SRE, AI infrastructure, and full-stack delivery.
Production apps
▸ deployed & maintained
Years of engineering
▸ shipping at scale
Platform uptime
▸ multi-region SLO
02 — stack
The toolbox. From bare metal to LLMs.
DevOps & Cloud
Kubernetes & Containers
CI/CD & GitOps
SRE & Observability
AI / ML Infra
Backend
Frontend
Data & Storage
03 — experience
Ten+ years. Six teams. One throughline.
Lead Software Engineer / DevOps
Jun 2023 — PresentWebpoint Solutions, LLC · Kathmandu, Nepal
- ▸Architect & maintain highly-available, multi-cluster, multi-region Kubernetes platform serving 3M+ MAU
- ▸Design geo-distributed traffic routing and failover strategy across regions
- ▸Lead platform engineering org — observability, reliability, deployment velocity
Senior Software Engineer / DevOps
Jun 2022 — Jun 2023Webpoint Solutions, LLC · Kathmandu, Nepal
- ▸Deployed & maintained 20+ production applications across AWS
- ▸Built React / Next.js / NestJS apps end-to-end
- ▸Mentored 10+ interns and junior engineers
Software Engineer
Jan 2021 — Jul 2021Signetic · Kathmandu, Nepal
- ▸Built HL7-formatted vaccination submission pipeline to Immunization Information Systems (IIS)
- ▸Converted HL7 streams into human-readable reports for clinical staff
Software Engineer / DevOps
Jul 2020 — Jul 2021Leapfrog Technology, Inc. · Kathmandu, Nepal
- ▸Deployed multiple projects across AWS / Azure
- ▸Set up CI/CD pipelines with GitHub Actions, CircleCI, TravisCI, Azure DevOps
Associate Software Engineer
Jun 2019 — Jul 2020Leapfrog Technology, Inc. · Kathmandu, Nepal
- ▸Foundations in full-stack delivery and cloud automation
Front-end Developer
Dec 2017 — May 2019Yarsha Studio Pvt. Ltd. · Kathmandu, Nepal
- ▸Built multiple React.js production sites
- ▸Engineered a real-time GPS-tracking backend over TCP sockets with D3.js visualization
05 — case study
From git push to ten clusters in seconds.
A live walkthrough of the platform I lead — GitOps continuous delivery wired through ArgoCD Image Updater, with HashiCorp Vault, Karpenter autoscaling, and DNS-level failover keeping it reliable.
stage 01 / 08
git push origin main
▸ fleet · 10 production clusters
Auto-restart on env change.
Vault rotates → Reloader detects → Rolling update: new pods spin up, old pods drain.
kv/prod
DB_PASSWORD
ttl 15m
api-1
v1 · Running
api-2
v1 · Running
api-3
v1 · Running
Right-sized nodes. In seconds.
Provision the cheapest, fastest fit per workload.
▸ 3 active nodes
Geo-aware traffic. Zero downtime.
Health-checked failover to the secondary cluster.
healthy · 142ms
standby · warm
▸ how it works
Developer commits
git push triggers GitHub Actions on the application repo.
CI builds image
Multi-stage Dockerfile produces an immutable image tagged with the commit SHA.
Push to ECR
OIDC-auth login to AWS, image pushed to a region-replicated ECR repo.
Image Updater scans
ArgoCD Image Updater watches ECR and detects the new tag matching semver/regex policy.
GitOps bump
Updater commits a values.yaml change to the gitops repo — single source of truth.
ArgoCD syncs
App-of-apps detects drift, runs sync waves with PreSync hooks (db migrations, smoke checks).
Fleet rollout
Progressive delivery across 10 clusters — canary → 25% → 100%, with automatic rollback on SLO burn.
Observability loop
Prometheus + Loki feed Grafana SLO dashboards; PagerDuty fires only on error-budget burn.
04 — selected work
Things I’ve built. Things that ship.
06 — open source
Live from GitHub. Updated as I push.
▸ public repos
▸ followers
▸ stars (top 4)
05 — let’s build
Got something
ambitious?
I’m always up for a chat about platforms, reliability, AI infrastructure, and the messy space in between.