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.
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.
Not slogans — just the habits that keep my work grounded when projects get complex.
I separate the rule that must stay true from the implementation that can change. That makes architecture less dramatic and easier to evolve.
The best code is often the code a tired teammate can read safely. I prefer clear naming, direct flows, and tests over clever shortcuts.
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.
I do not over-engineer for imaginary scale. I focus on boundaries, contracts, and data flow so real growth has somewhere natural to go.
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.
Good systems make accepted, denied, and edge cases explicit. That clarity helps developers, testers, stakeholders, and AI tools work safely together.
Production work across fintech, healthcare, social, ERP, and custom business platforms — with lessons carried from one domain into the next.
A practical stack shaped by production work: strongest in .NET, relational data, modular backend design, and full-stack delivery.
I use modern AI tools where they help, but the responsibility for architecture, logic, and quality stays with the engineer.
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.
Open to senior full-stack / .NET-focused roles, hybrid or remote, with teams that value clear thinking, steady delivery, and practical ownership.