Senior .NET Engineer — Fintech · ERP · Healthcare
Open to senior remote roles · UTC+5:45 · overlaps EU mornings & APAC afternoons

Senior .NET engineer.I ship fast becauseI think the problem through first.

Four-plus years across lending platforms, ERPs, healthcare systems, and social products. Teams hand me the messy requirements; those leave as clear flows, clean module boundaries, and shipped software.

See the proof ↓ CV Start a conversation →
Kushal Tiwari
.NET · 4+ yrs
UTC+5:45 · remote-ready
0+
Years shipping
0+
Production systems
0
Companies + independent clients
UTC+5:45
Remote-ready · EU/APAC overlap
// 01 — Proof of work

Systems where mistakes
are expensive.

Three engagements across fintech, social, and healthcare — shown as they happened: the problem, the call we made together, what it traded away, what it bought.

Case 01 FintechCurrent engagement

Credit Lending Platform

Xmartpoint Technologies · microservices + modular monolith · .NET / MS SQL / Redis
“We treated the reporting server like a back office — month-end jobs go there so the teller windows never queue.”
Problem

Disbursement, repayment, and regulatory reporting (NTA, BSVR) where an incorrect figure is a compliance event, not a bug ticket. Hot paths had to stay sub-second under daily transaction load.

Decision

Kept a monolith core and extracted services only where isolation paid its operating cost. A standalone .NET reporting server absorbs month-end aggregation so heavy queries never contend with live lending.

Trade-off

Full microservices would turn a small team into its own ops department; a pure monolith queues reports behind live disbursements. Each cost is paid only where it buys something.

Result

Sub-second hot paths sustained under daily load; reporting off the critical path; module boundaries that let changes ship with less regression risk.

.NETASP.NET CoreMS SQLRedisMicroservicesReact
Case 02 SocialCompleted 2025

Pairable — Social Platform

Plab Productions · greenfield, international client · 3-person team · .NET Web API / Flutter
“Modules drawn like apartment walls — one lease per team, and walls come down cheap if the tenant outgrows the room.”
Problem

A greenfield social platform for an international client, built by three engineers across onboarding, profiles, learning, matchmaking, events, and notifications.

Decision

One deployable .NET backend with hard internal module boundaries and clear ownership per area; JWT + refresh auth; real-time notifications; Flutter client on PostgreSQL and Redis.

Trade-off

Microservices at that stage would have made a 3-person team its own ops department. Seams were drawn so any module could be extracted later if scale demanded it.

Result

Delivered end-to-end through matchmaking and notifications with moderator role-based access; engagement completed in 2025 with the client operating independently.

.NET Web APIFlutterPostgreSQLRedisDocker
Case 03 Healthcare

Medical & Manufacturing ERP

DTRG Network → Neosoftware · full-cycle ERP · .NET / MS SQL / Angular
“We stopped asking the app to remember the rules and made the database refuse to forget them.”
Problem

Double-booked clinicians, scheduling logic scattered across client apps, and high-volume month-end payroll runs for clinical and manufacturing clients.

Decision

Pushed scheduling invariants into the data layer — SQL constraints plus state machines so the database refuses invalid states no matter which client writes.

Trade-off

App-layer rules are easier to change; data-layer guarantees are impossible to bypass. In a clinic, the guarantee wins.

Result

Zero double-bookings since launch; month-end payroll processed within its window at high record volume; later extended into modular ERP areas that grew without monolith-wide rewrites.

.NET Framework MVCMS SQLAngularHealthcare
// 02 — Experience

Four-plus years of
shipping real systems.

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

NOV 2025 — PRESENT
Xmartpoint Technologies
Senior Full-Stack / .NET Engineer · Bakhundole
  • Returned to the credit lending platform I previously helped build; contributing across production-critical financial modules
  • Built and maintain financial, NTA, BSVR, workflow, and approval modules with attention to correctness and auditability
  • Improved module boundaries across lending, reporting, and integrations so changes ship with less regression risk
  • Introduced MCP-enabled coding workflows for review support, migration scripting, and design-decision documentation
.NETMicroservicesMS SQLRedisMCP
APR 2025 — OCT 2025
Neosoftware Private Limited
Full-Stack / .NET Developer · Lalitpur · between two stints at Xmartpoint
  • Led backend delivery for ERP rollouts across manufacturing and hospitality clients
  • Shaped a modular ERP so teams could extend business areas without monolith-wide rewrites
  • Built reporting & MIS modules; integrated Angular frontends with .NET APIs for cohesive UX
.NETAngularPostgreSQLERP
2023 — MAY 2025
Xmartpoint Technologies · first stint
Full-Stack / .NET Developer · Bakhundole
  • Helped build a large-scale credit lending system on a microservices + monolith hybrid for real-time financial workflows
  • Tuned MS SQL stored procedures, query plans, and the Redis caching layer for sub-second response across hot paths
  • Built a standalone .NET reporting server that offloaded heavy aggregation from the transactional core
  • Delivered React dashboards used daily by ops, risk, and collections teams
.NETWeb APIReactMS SQLRedisFintech
2024 — 2025 · REMOTE FREELANCE
Plab Productions — Pairable
Project Lead & Full-Stack Engineer · Remote · 3-person team · completed 2025
  • Led backend delivery for a greenfield social platform (.NET Web API + Flutter) for an international client
  • Structured backend areas for onboarding, profiles, matchmaking, events, and notifications with clear module ownership
  • Built auth (JWT + refresh), real-time notifications, and role-based access for community moderators
.NETFlutterPostgreSQLRedisDockerMobile
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
  • Enforced appointment scheduling with SQL constraints + state machines, eliminating double-bookings
  • Optimized stored procedures processing high-volume monthly records
.NET Framework (MVC)MS SQLHealthcare
2023 · INDEPENDENT CLIENT
National Biotech Company
Full-Stack Developer (Freelance)
  • Delivered a tailor-made corporate website end-to-end by mapping the real workflow with sales, operations, lab, product, and UI/UX teams before writing code
Full-StackCMSStakeholder Discovery
// 03 — Remote-ready

Working from
UTC+5:45.

Not an offshore compromise — a timezone that overlaps Europe's working morning and Asia-Pacific's afternoon, backed by habits built for async teams.

Your day (Kathmandu)EuropeAPACUS East
14:00 – 19:00Full morning overlapAfternoon—
08:00 – 11:00—SG morning · Syd afternoon—
18:00 – 21:00Late eveningEvening8 – 11 AM EST
Written-first async

Decisions land as short docs and PR descriptions, so answers survive timezone gaps instead of living in someone's morning stand-up.

Specs with explicit edges

Accepted, denied, and edge cases written down before implementation starts — reviewers and testers reach the same conclusion I did.

English — professional working proficiency

Comfortable owning specs, leading reviews, and running demos directly with international stakeholders.

Contractor setup

No sponsorship required, no relocation needed. Replies within 24 hours on weekdays.

// 04 — On unfamiliar problems

Understand first.
Then move fast.

Fast delivery isn't a personality trait — it's what's left once the unknowns are gone. This is the sequence I run before writing design docs or code.

01

Find what the system is actually for.

The invariant hiding under the requirements doc — the rule that must hold no matter how the implementation changes.

02

Chase the unknowns first.

Anything I can't explain yet gets investigated before design starts, because surprises get more expensive every phase later.

03

Test the shape against extremes.

If the design only works at today's volume, it's wrong. If it needs machinery we'll never use, it's also wrong.

04

Then move fast.

Once the problem is fully mapped, implementation speed takes care of itself — that's where the reputation for shipping quickly comes from.

// 05 — Stack

Depth over lists.
Earned in production..

Organized by how hard I've leaned on each tool in real systems above — not by confidence percentages.

Expert — carried production systems
C#ASP.NET CoreWeb APIMS SQL ServerEF Core / DapperRedis caching & pub/subStored procedure tuning
Proficient — shipped with
ReactAngularTypeScriptFlutterPostgreSQLMongoDBDockerGitHub Actions CI/CDAWS (Cloud Practitioner)
Working knowledge
Node.jsPythonNginx / LinuxMCP-integrated coding agents (daily drivers)

Every “expert” row above has a production case behind it — see Cases 01–03.

// 06 — How I think

Habits that hold
when projects get hard.

Not slogans — the working rules visible in every case study above.

I.

Understand before
architecting.

Separate the rule that must hold from the detail that can change. That makes architecture less dramatic and cheaper to evolve.

II.

Boring over
clever.

Code gets read by teammates at 6 PM on deploy day. Clear naming and direct flows beat shortcuts every time.

III.

Abstractions are earned
by repetition.

Extract shapes that have proven themselves twice. Skip speculative ones — they cost more than duplication.

IV.

Seams beat
scale plans.

No imaginary-scale machinery. Modules sized so features don't collide in a merge — growth then has somewhere natural to go.

V.

Own the
whole flow.

A schema decision is an API contract is a UI state is a support ticket. I keep the whole journey in view.

VI.

Make rules
executable.

Accepted, denied, and edge cases explicit enough that tests, reviewers, and future maintainers reach the same conclusion.

// 07 — Who I am

Engineer first,
always curious.

The short version of four-plus years, four companies, and one method.

I started in .NET Framework on a full-cycle medical ERP and have spent every year since closer to systems where mistakes are expensive: lending platforms under regulatory reporting, ERPs carrying payroll, products with real users on the other side of the API.

The constant across companies is how I work before code exists. I chase down everything I don't yet understand until the problem has a shape — then implementation goes quickly. Teams tend to hand me the requirements nobody has fully untangled yet.

Half my attention usually sits ahead of the current sprint — where the domain is moving, what the product will need next quarter, which seams to draw now so change stays cheap later.

Off-hours you'll find me on a football pitch, on a long ride out of the valley, or at an unhurried hangout with friends.

Role
Senior Software Engineer
Experience
4+ years
Current
Senior .NET Engineer · Xmartpoint
Location
Kathmandu, Nepal 🇳🇵
Work Style
Fully remote · contractor
Timezone
UTC+5:45 · EU AM / APAC PM overlap
Cloud
AWS Cloud Practitioner
Availability
Open — replies within 24h weekdays
// 08 — Contact

Have a system
that needs to ship?

Open to senior .NET / full-stack roles — fully remote from UTC+5:45. Contractor arrangement: no sponsorship required. Replies within 24 hours on weekdays.

Powered by Formspree · Or email me directly at work.kushal.tiwari@gmail.com