Remote — Singapore
Senior engineering, based in Bangkok, available remotely for Singapore.
Based in Bangkok, Thailand — one hour behind Singapore — available remotely for Singapore-based teams.
Bangkok (UTC+7) is one hour behind Singapore (UTC+8), so the working day overlaps end to end.
What I bring to Singapore engagements
- High-concurrency systems (Node.js, TypeScript, Redis, MongoDB, AWS)
- Applied AI: RAG pipelines and LLM agent integrations
- Full-stack product engineering
Evidence
national-scale admissions platform on Redis/MongoDB/AWS supporting millions of concurrent requests
AI agent-to-storefront integration layer
A worked example
- The problem
- Thailand's national university admission system has no average day. Traffic is close to nothing for most of the year, then every applicant in the country arrives inside the same few hours when results open. Falling over on that day is the only failure that matters.
- What I built
- I engineered the platform on Node.js and TypeScript with a Vue.js front end, TypeORM over MongoDB for the data layer, Redis for the read paths that take the brunt of a results-day spike, and AWS ECS and EKS underneath so capacity is a scaling decision rather than a rebuild.
- Outcome
- The system is designed to absorb millions of concurrent requests on those peak days. It runs in production at student.mytcas.com.
Questions Singapore teams ask
Have you worked with Singapore clients before?
Not yet. Every role on my CV has been with a Bangkok-based employer, so I have no Singapore client list to point at. What I can show is the work itself: production systems with public URLs and open repositories, listed on this page and on the home page. I would rather you judge those than take a claim about local presence on trust.
How much of the working day do we share?
Effectively all of it. Bangkok is one hour behind Singapore, so a 9 to 6 in Bangkok is a 10 to 7 in Singapore. There is no async compromise to design around and no need for either side to take calls outside normal hours.
Can you handle the concurrency our platform needs?
That is the specific thing TCAS was built for: a national admissions system that sits idle most of the year and then takes the entire country's applicants at once. Redis on the hot read paths, AWS ECS and EKS for scaling. Whether it maps to your load depends on your shape of traffic, which is worth an actual conversation rather than a claim here.