Backend Engineer · Bangkok, TH · GMT+7

Aom KhamPhaung

Ships multi-tenant SaaS end-to-end — ambiguous requirement to production — for enterprise clients across Japan and Southeast Asia.

See the workGet in touch
Scroll
Now
Backend Engineer, Coosy — Japan, remote
Since
2022 · 3+ years shipping production
Core
Laravel · FilamentPHP · AWS · PostgreSQL
Status
Open to remote roles

Measuredimpact

10+ enterprise clients
0%

faster tenant onboarding — automated provisioning and access control on a multi-tenant CMS.

0%

less production downtime — systematic root-cause analysis across dev and production.

0%

fewer post-launch bugs — code review discipline and SOLID as a team standard.

What Iactually do

Three things, no filler
Ownership

Own it end-to-end

Ambiguous business requirement → technical spec → production deploy → post-launch monitoring. No handoff gaps, no waiting to be told.

Architecture

Build for scale

Multi-tenancy, RBAC, relational schema design, Redis and Cloudflare caching, Laravel queues, zero-downtime releases on AWS.

AI-native

Ship with AI in the loop

LLM APIs shipped inside client products, and AI coding tools in the daily workflow — faster output without dropping review standards.

Trackrecord

2022 — present
2024 — PresentCoosy
Japan · Remote

Backend Engineer

Multi-tenant SaaS CMS for enterprise clients

  • Architected a multi-tenant SaaS CMS in FilamentPHP and Laravel for 10+ enterprise clients — RBAC, REST integrations, automated provisioning. Onboarding time down 40%.
  • Took full product ownership: ambiguous requirements into technical specs, through deployment and post-launch monitoring.
  • Integrated LLM chatbot APIs into client applications for context-aware automation.
  • Established root-cause analysis and structured debugging workflows across environments. Downtime down 25%.
LaravelFilamentPHPAWSDockerRedisCI/CD
2022 — 2024ILBC
Myanmar · Onsite

Junior Software Developer

APIs, integrations and performance work

  • Designed and optimized relational schemas that held up as enterprise workloads grew.
  • Led REST API development and third-party integrations — Google APIs, OAuth, SMS gateways.
  • Shipped payment gateway integrations with transaction reliability and compliance as the bar.
  • Cut page load times and raised capacity with Redis and Cloudflare caching strategies.
PHPMySQLRedisCloudflareGit

Selectedwork

Two products, one platform
Flagship product · multi-tenantClient work · unreleased

AI Chatbot SaaS Platform

Backend engineer — architecture, APIs, background pipelines

A tenant-isolated chatbot service that answers from each customer's own knowledge base. Tenants ingest their material — uploads, documents, crawled pages — and the platform chunks and categorises it, then serves grounded answers through an embeddable widget with live streaming.

  • Knowledge ingestion pipeline: file, CSV, document and URL crawling, each on its own queued job so a large import never blocks the request cycle.
  • Chunking and category redistribution with recrawl support, so a tenant's corpus stays current without a full reimport.
  • Realtime widget messaging over WebSockets, with generation success and failure broadcast as events rather than polled.
  • Plan and usage metering per tenant, subscriptions, invitations and role-based access across tenant boundaries.
  • Media and document storage on S3-compatible object storage, with dashboard widgets prefetched and cached to keep the admin panel responsive.
Laravel 12FilamentPHP 4Reverb / WebSocketsQueuesLLM APIsAWS S3ReactDocker
ClientAPIWorkersData
Embeddable widget

A script tag a tenant drops onto their own site. Domain-restricted per tenant, so a stolen embed key will not answer from someone else's knowledge base.

ReactViteDomain allowlist
Companion product · same platformClient work · unreleased

Multi-Tenant Headless CMS

Backend engineer — content modelling, tenancy, integrations

The content side of the same platform. Each organisation manages its own sites, custom post types, taxonomies and field groups, then publishes through an API the chatbot and front-end clients both consume. Sign-in runs through a shared OAuth portal, so one account reaches every service.

  • Content modelling built for editors: custom post types, taxonomies, terms, and repeatable field groups rather than fixed schemas.
  • Organisation → site → user tenancy with invitations and per-site roles, so agencies manage many client sites from one account.
  • Single sign-on across all services via an OAuth portal, with impersonation for support staff and an audit trail behind it.
  • SEO metadata, previews, rich-text editing, PDF export and webhooks for downstream systems.
  • Billing surfaces — plans, invoices and line items — shared with the platform's other services.
Laravel 12FilamentPHP 4InertiaPassport / OAuthMySQLAWS S3Docker
ClientAuthAPIData
Editor panel

Where editors model and write content: custom post types, taxonomies, terms and repeatable field groups, rather than a schema fixed at build time.

FilamentPHP 4TiptapInertia
A note on these

Both are client products that have not shipped publicly, so they are described at architecture level only — no screenshots, client names or source. Happy to walk through the design decisions in a conversation.

Technicalwriting

Published · in Japanese
June 2025Coosy blog
Japanese

What changed from Laravel 11 to 12, and how to upgrade

Laravel 11から12への変更点とアップデート方法

A walkthrough of the Laravel 12 release for teams deciding whether to move: the new starter kits, concurrency and internal performance work, and the behavioural changes that actually break things — UUID generation, request handling, validation rules. Closes with a five-step upgrade path with code.

Laravel 12MigrationBreaking changes
June 2025Coosy blog
Japanese

What is Astro.js? The fast, lightweight next-generation framework explained

Astro.jsとは？ 高速・軽量の新世代フレームワークを詳しく解説

Written for decision-makers as much as developers: why partial hydration makes initial loads fast, how Astro compares against Next.js and WordPress for content sites, and which kinds of projects it suits — with the implementation workflow laid out end to end.

Astro.jsPartial hydrationPerformance

Both published on the company engineering blog for a Japanese audience — the same work as writing a technical spec, aimed at readers who have to make a decision at the end of it.

Thestack

Honest about depth

Backend

PHP · LaravelFilamentPHPNode.jsGolang · learningPython · learning

Frontend

ReactNext.jsVueTypeScript · learningTanStack · familiar

Data

PostgreSQLMySQLRedis

Cloud & DevOps

AWSDockerCI/CDGCP · familiar

AI & Tooling

LLM API integrationAI coding assistantsPrompt engineering

Practices

SOLIDREST designMulti-tenancyRBACSpec writingAgile / SCRUM

Filled = production depth · Outline = learning or familiar

WorkingAI-native

AI is in the loop every day, but it does not make the calls that matter. The split is deliberate.

  • AI draftsFirst-pass specs, scaffolding, test stubs, refactor sweeps, unfamiliar-API exploration.
  • I decideArchitecture, schema design, tenancy boundaries, and what ships to production.
  • ResultMore surface covered per sprint with review standards intact — bug reports still went down 30%.

Education

BSc Computer ScienceUniversity of the PeopleExpected Jan 2027
Associate Degree, Computer ScienceUniversity of the PeopleApr 2026
Computer Applications & ITArizona State UniversityJan 2024

Hiring backendor full-stack?

I reply within a day. Remote-ready from Bangkok, used to working across Japan and Southeast Asia time zones.

aomkhamphaung.dev@gmail.comGitHubLinkedInResume PDF
Bangkok, TH · GMT+7+66 8 0753 0723Open to remoteAurora / Nocturne