About me
I'm Benjamin — a software engineer from Malaysia with 5+ years of professional experience building enterprise software. Most of my career has been spent at tech companies in Kuala Lumpur, where I worked across the stack on HR management systems and point-of-sale platforms — from React and Vue frontends to Laravel and Node.js backends.
At my most recent role at TalentCloud AI, I spent three years as a Senior Full Stack Developer — leading a frontend migration to a Nuxt.js monorepo, building complex features like Excel-like shift management systems, and mentoring junior developers. Before that, I was the sole frontend developer at Platinum Code, where I architected a POS system for the F&B industry from scratch.
In 2025, I moved to Cambodia and took a deliberate sabbatical to upskill and build independently. I've been designing Baguette POS — a point-of-sale system built for the Cambodian market with dual-currency payment handling and offline-first ordering — and launched The Eco Garden Cat Project, a community platform I initiated to help care for stray cats in my neighbourhood.
I work primarily with TypeScript, React, and Next.js, but I've shipped production code in Vue, Nuxt, Angular, and Astro. On the side, I tinker with network security tools like Nmap and Burp Suite — not as a career pivot, just because I like understanding how things break.
I'm looking for a remote role — ideally with a product team where I can own features end-to-end and work closely with users.
Frequently Asked Questions
Can you work across different time zones?
Absolutely. I'm based in Cambodia (GMT+7) and have worked with teams and clients across Southeast Asia, Europe, and North America. I'm comfortable with async communication and overlap hours — most of my remote work has been with teams where we share a few hours of real-time availability and handle the rest through structured updates.
Do you work with existing codebases or only greenfield projects?
Both. I've built projects from scratch (like Baguette POS and this portfolio) and I've also inherited and improved existing codebases. I'm comfortable diving into unfamiliar code, refactoring where it matters, and shipping incremental improvements without breaking what already works.
What's your approach when starting a new project?
I start by understanding the actual problem — not just the feature request. That usually means talking to the people who'll use the product. From there, I scope a lean first version, ship it quickly, and iterate based on real usage. I'd rather launch something focused that works than a feature-packed app that doesn't get used.
Skills & Technologies
Technologies I've used professionally — in enterprise products, independent projects, and everything in between.