Open to senior engineer roles · hybrid & remote

I build practical systems,
keep them clear,
and help teams ship.

I’m Kushal Tiwari, a full-stack engineer from Kathmandu with 5 years of experience building lending platforms, ERPs, healthcare systems, social products, and custom business websites. I care about clear requirements, clean module boundaries, and software that teams can operate with confidence.

Kushal Tiwari
Kushal Tiwari · engineer · systems thinker
5
Years engineering
5+
Production systems
4
Companies · 3 verticals
Refactors in progress
Scroll
// 01 — Who I am

Full-stack range,
grounded in practical delivery.

I work across backend, frontend, data, and product flow — but the goal is always the same: make the system easier to understand, change, and trust.

My best work sits at the intersection of product needs and engineering detail. I can move from database schema and API contracts to frontend behavior and mobile flows, while keeping the business rule visible through every layer.

I like simple architecture that earns its shape from the problem. Before choosing a pattern, I try to understand what must stay true: the workflow, the data rules, the user expectation, and the operational risk. Once that is clear, the code can stay modest, predictable, and easier for a team to improve.

Across fintech, healthcare, ERP, social, and biotech projects, I’ve worked with .NET, React, Flutter, Angular, Node, PostgreSQL, MS SQL, MongoDB, Supabase, Firebase, Redis, and Docker. The stack changes from project to project; the discipline stays the same: understand the problem, ship the useful slice, then improve the seams.

I’m useful to teams that need more than tickets completed. I help turn messy requirements into clear flows, make trade-offs visible, and leave behind code that the next engineer can understand without guesswork.

Role
Senior Software Engineer
Experience
5 years
Current
Senior Full-Stack / .NET Engineer · Xmartpoint
Location
Kathmandu, Nepal 🇳🇵
Work Style
Hybrid & Remote
Process
Agile · Sprints · MVP · Vertical Slices
Coding Agents
MCP Integrated
Cloud
AWS Cloud Practitioner
// 02 — How I think

Working principles
I try to practice daily.

Not slogans — just the habits that keep my work grounded when projects get complex.

I.

Start with
the real problem.

I separate the rule that must stay true from the implementation that can change. That makes architecture less dramatic and easier to evolve.

II.

Predictable
over clever.

The best code is often the code a tired teammate can read safely. I prefer clear naming, direct flows, and tests over clever shortcuts.

III.

Abstract when
the pattern is real.

I avoid abstractions that exist only to look architectural. When a repeated shape proves itself, I turn it into a shared tool the team can rely on.

IV.

Scale through
clean seams.

I do not over-engineer for imaginary scale. I focus on boundaries, contracts, and data flow so real growth has somewhere natural to go.

V.

Think across
the whole flow.

A backend decision affects the UI. A database rule affects support. A loading state affects trust. I try to keep the whole user journey in view.

VI.

Be clear about
the rules.

Good systems make accepted, denied, and edge cases explicit. That clarity helps developers, testers, stakeholders, and AI tools work safely together.

// 03 — What I've built

Five years of
shipping real systems.

Production work across fintech, healthcare, social, ERP, and custom business platforms — with lessons carried from one domain into the next.

NOV 2025 — PRESENT
Xmartpoint Technologies
Senior Full-Stack / .NET Engineer · Bakhundole
  • Returned to a credit lending platform I previously helped build, contributing to ongoing improvements across familiar production-critical modules
  • Built and maintain financial, NTA, BSVR, workflow, and approval modules, with attention to correctness, auditability, and operational clarity
  • Improved module boundaries across lending, reporting, and integrations so changes can be tested and released with less risk
  • Introduced MCP-enabled coding workflows for code review support, migration scripting, and design-decision documentation
  • Stack: .NET · ASP.NET Core · MS SQL · Redis · Microservices · MCP
.NETMicroservicesMS SQLRedisMCP
APR 2025 — JAN 2026
Neosoftware Private Limited
Full-Stack / .NET Developer · Bhanimandal, Lalitpur · On-site
  • Led backend delivery for ERP rollouts across manufacturing and hospitality clients
  • Helped shape a modular ERP so teams could extend business areas without turning every change into a monolith-wide rewrite
  • Built reporting & MIS modules; integrated Angular front-end with .NET APIs for cohesive UX
  • Stack: .NET · Angular · PostgreSQL · Docker · Redis
.NETAngularPostgreSQLERP
2023 — MAY 2025
Xmartpoint Technologies
Full-Stack / .NET Developer · Bakhundole
  • Helped build a large-scale credit lending system using a microservices + monolith hybrid for real-time financial workflows
  • Optimized MS SQL stored procedures, query plans, and Redis caching layer for predictable sub-second response across hot paths
  • Built a standalone .NET reporting server to offload heavy aggregation queries from the transactional core
  • Delivered React dashboards for ops, risk, and collections teams
  • Stack: .NET Core · React · MS SQL · Redis · Microservices
.NET CoreReactMS SQLRedisFintech
2022 — 2023
DTRG Network
Full-Stack / .NET Developer · Kathmandu · On-site
  • Built a full-cycle medical ERP — HR, payroll, appointments, MIS reporting — for a clinical client
  • Appointment scheduling logic with SQL-level constraints + state machines to eliminate double-bookings
  • Optimized stored procedures processing high-volume monthly records
  • Stack: .NET MVC · MS SQL · jQuery · Bootstrap
.NET MVCMS SQLHealthcareMVC
2023
National Biotech Company
Full-Stack Developer (Freelance) — Founding Engagement
  • Built a tailor-made website from scratch for a biotech company, covering product, corporate, and employee-facing needs within the real budget
  • Worked directly with sales, operations, and lab stakeholders to understand the workflow instead of designing from assumptions
  • Collaborated with product, manufacturing, UI/UX, and video teams to turn unclear requirements into a solution the business could operate
  • Delivered a responsive front-end and API-backed experience with practical attention to accessibility, maintainability, and handoff
Full-StackCMSInformation ArchitectureStakeholder DiscoveryGreenfield
// 04 — Stack

The tools.
Sharpened daily.

A practical stack shaped by production work: strongest in .NET, relational data, modular backend design, and full-stack delivery.

Backend & Systems

.NET / ASP.NET Core / Web APIEXPERT
C#EXPERT
Modular ArchitectureADV
Microservices / Event-DrivenADV
Node.js / Express / Python / PHPWRK

Frontend & UX

JavaScript / TypeScriptEXPERT
ReactADV
AngularADV
Flutter (Mobile)WRK
HTML5 / CSS3 / jQuery / AJAXEXPERT

Data & Backends

PostgreSQL / MS SQLEXPERT
MongoDB / Supabase / FirebaseWRK
Redis (caching & pub/sub)ADV
EF Core / DapperEXPERT
Query Tuning / Indexing / SchemaADV

DevOps & Cloud

DockerADV
Git / GitHub Actions / CI-CDADV
AWS (Cloud Practitioner)SLD
Linux / NginxWRK
// 05 — Craft & AI

Modern tools,
classical thinking.

I use modern AI tools where they help, but the responsibility for architecture, logic, and quality stays with the engineer.

Agentic AI & Coding Agents

AI helps most
when the rules are clear.

I use tools like MCP, Claude Code, OpenCode, Antigravity, Cursor, Windsurf, and Copilot to review code, explore migrations, generate tests, and document decisions. They work best when the system has clear boundaries and the engineer stays accountable for the logic.

  • /01MCP integration in my dev environment for codebase-aware agents and refactoring tools
  • /02Agentic debugging — surface root causes in seconds, not hours
  • /03Coding agents as serious pair-programmers — code review, test generation, trade-off analysis
  • /04Multi-agent orchestration for code migration, documentation, design-to-code flows
  • /05Daily drivers: Windsurf, Claude Code, OpenCode, Antigravity, Cursor, Copilot — knowing when to use which, and when to use none
// 06 — Contact

Let's build
something worth shipping.

Open to senior full-stack / .NET-focused roles, hybrid or remote, with teams that value clear thinking, steady delivery, and practical ownership.