Backend Engineer / Bangkok / Available 2026

I rescue messy backends & ship clean ones ↗

Ten-plus years writing production code across .NET, Laravel, Node.js, and Python. I help founders ship MVPs in weeks, fix legacy systems nobody else wants to touch, and connect APIs that weren't designed to talk.

10+ Years Shipping
4 Core Stacks
.NET
PHP
NODE
PY
~15 HRS/WK FREELANCE
[ what i do ]

Three things I do
well — all backend.

i

Legacy Rescue

Inherited a slow .NET 4.x monolith? A tangled Laravel codebase nobody understands? I diagnose root causes and ship clean fixes — not band-aids.

ii

MVP Sprint

Founders: I'll turn your idea into a working product fast. Auth, payments, database, deployment — done. A real MVP you can show users and investors.

iii

API Glue

Connect anything to anything. Webhooks, scheduled jobs, scraping pipelines, third-party integrations. If two systems need to talk, I'll make them talk reliably.

[ selected work ]

Open-source case studies.

Node.js TypeScript BullMQ
01

Webhook Orchestrator

A reliable webhook ingestion and fan-out service. Receives events from upstream systems and routes them to multiple downstream services with retry, idempotency, and dead-letter handling.

View on GitHub
Highlights
  • HMAC-verified ingestion
  • Exponential backoff retry
  • Dead-letter with replay
  • Docker compose ready
Laravel 11 Stripe Postgres
02

Multi-tenant SaaS Starter

A production-ready Laravel boilerplate for B2B SaaS. Skip 2–3 weeks of plumbing — multi-tenancy, team invites, Stripe billing, audit logs, and role-based access work out of the box.

View on GitHub
Highlights
  • Workspace-scoped queries
  • Stripe webhook idempotency
  • Audit log auto-redaction
  • Tenant isolation tests
.NET 8 EF Core C# 12
03

Legacy .NET → Modern .NET 8

A side-by-side case study showing how to take a typical "enterprise" .NET Framework 4.x API and modernize it to .NET 8 — with measurable improvements and a phase-by-phase migration playbook.

View on GitHub
Highlights
  • Realistic legacy code
  • Modern minimal API rewrite
  • 6-phase migration playbook
  • 16 tests proving correctness
[ how i work ]

Async-friendly. Tested. Documented.

i.

Read first, write second

For legacy work, I spend the first hours reading code and asking questions before touching anything. Most bugs reveal themselves before you start typing.

ii.

Tests before refactors

If we're changing behavior, we need a way to verify it. I add the smallest possible test before any non-trivial change.

iii.

Honest estimates

I'd rather quote longer and deliver early than over-promise. If I'm unsure, I'll say so and propose a small spike to find out.

iv.

Docs that future-you thanks

Every project ships with a README that explains what it does, why decisions were made, and how to run it. Knowledge transfer matters.

[ get in touch ]

Got a backend mess to clean up?

Email thee.kavi@gmail.com
Code github / theekavi
Hours Mon - Fri / GMT+7