Django-focused developer building APIs, web platforms, and mobile-connected systems
from requirements to delivery.
Bharatpur, Chitwan, Nepal · NPT (UTC+5:45)
I’m a full-stack developer with a backend center of gravity and 4+ years of experience across Django APIs, Next.js products, Flutter applications, data design, and delivery.
I currently lead full-stack product delivery at Sampreshan Media, working across requirement discovery, backend architecture, frontend coordination, and team execution. My work spans 12 products across web and mobile, from education ERP and healthcare operations to publishing and booking platforms.
Architecture is a sequence of trade-offs, not a stack list.
A cross-platform Flutter package for fetching web-page metadata and rendering responsive, customizable link-preview cards. It supports metadata extraction, caching, flexible thumbnail layouts, resilient error handling, and direct metadata access for custom interfaces.
v1.1.0 · 150 pub points · 13 likes · Android, iOS, Linux, macOS, web, and Windows
| Product | What I owned | Stack | Result |
|---|---|---|---|
| MeroVidya | Backend APIs, data design, and Flutter delivery | Django REST Framework, Flutter, PostgreSQL, Firebase | Live education ERP used by approximately 10–12 schools today |
| SanchoNepal | Technical direction and full-stack delivery | Django, Next.js, TypeScript, PostgreSQL, Redis, Docker | Live publishing MVP with an architecture prepared for later product phases |
| CDC Clinic | Complete solo frontend and backend build | Django, PostgreSQL, Tailwind CSS, django-unfold | Clinic management system delivered in approximately two months |
| Area | Technologies & strengths |
|---|---|
| Backend systems | Python, Django, Django REST Framework, JWT, Redis, Celery |
| Product interfaces | Next.js, TypeScript, Tailwind CSS, Flutter, Dart |
| Data & delivery | PostgreSQL, Docker, AWS, Firebase, Cloudinary, SMTP |
| Leadership | System design, requirement discovery, team coordination, mentoring |
- Discover the real workflow — clarify requirements before complexity becomes code.
- Design boundaries deliberately — separate clients, APIs, data, integrations, and operations.
- Ship in useful stages — protect a clear MVP while leaving room for the next phase.
Public GitHub activity only. Language usage reflects repository code, not proficiency.
Open to strong full-time opportunities and selected freelance work.
Start a conversation