I build systems that solve product problems.

I'm a Software Engineer who prioritizes user outcomes over clever code. I specialize in bridging the gap between complex technical constraints and business growth.

Next.jsReactNest.jsNode.jsTypeScriptPostgreSQLAI
Portrait photo

Selected Impacts

Rapid Telehealth MVP Deployment

We Lysn • 2024 - Present

MVP Launch in 2 Sprints

The Challenge

A mental health startup needed to move from concept to a functional workplace wellbeing platform within a highly compressed timeframe to validate the market.

The Solution

Architected the frontend using Next.js, tRPC, and Supabase. Collaborated in a 'feature trio' to drive rapid discovery and deployment of core telehealth features.

Technical Trade-off Matrix

DecisionProduct BenefitTech Trade-off
Direct Database-to-Frontend PipelineEliminate API layer maintenance for faster shippingCoupled deployment cycle
Continuous UI/UX IterationAllowed technical execution to pivot instantly based on user feedbackIncreased refactoring frequency during early discovery phases

Marketplace Performance & Reliability

Glints • 2022 - 2024

Optimized Web Vitals

The Challenge

The marketplace platform required better search visibility and extreme reliability to serve millions of career-seekers across Southeast Asia.

The Solution

Optimized Next.js performance for SEO and integrated Cypress/Playwright E2E testing into CI/CD to eliminate critical post-deployment regressions.

Technical Trade-off Matrix

DecisionProduct BenefitTech Trade-off
Design System MaintenanceEnsured UI consistency and boosted team shipping velocityOngoing overhead to maintain styled-components library
Automated E2E TestingReduced critical production bugs, protecting brand trustIncreased CI/CD pipeline execution time

Cloud Migration & UI Unification

Nintex • 2020 - 2022

+ Client Conversion

The Challenge

Facilitating complex client transitions from legacy O365 to proprietary cloud systems was a manual bottleneck slowing down revenue growth.

The Solution

Engineered a Node.js and NestJS-based migration tool to automate transitions while unifying UI/UX across multiple product suites using React and Angular.

Technical Trade-off Matrix

DecisionProduct BenefitTech Trade-off
Automated Migration ToolingLowered barrier for legacy customers to adopt new cloud systemsHigh initial development cost to handle legacy data edge-cases
WCAG Accessibility AuditEnsured legal compliance and inclusivity for global usersRequired significant refactoring of legacy component architecture

Personal Projects

Fitted In

AI Agents OrchestrationsLLM Streaming

A distributed AI pipeline optimized for zero-latency document synthesis. By fanning out resume processing to parallel agents, the system aggregates a tailored profile in real-time, streaming formatted Markdown directly to a copy-ready workspace for immediate use in Google Docs or Word.

VIEW_CODEBASE
Parallel_Agent_Synthesis_Map
Context A
Master Resume
Context B
LinkedIn Scrape
FAN-OUT AGENT ORCHESTRATION
Profile Agent
MD_HOOK_GEN
Exp Agent
BULLET_ALIGN
Skills Agent
ATS_FILTER_GEN
FAN-IN STREAMING
STREAMING_MARKDOWN_CHUNKS...
Final OutputFormatted Workspace View
Copy to G-Docs

My Flix

Affinity EngineStateful UI

A media discovery engine focused on the Reciprocal Loop of user behavior. By weighting sentiment across movie metadata, the system recursively updates a local preference state to re-rank search results and prune discovery feeds, ensuring the interface evolves with the user.

Sentiment Graphing

Links user 'Likes/Dislikes' to specific TMDB entities (Actors, Genres, Directors).

Discovery Pruning

Implicitly removes content from discovery lists based on cumulative negative affinity scores.

VIEW_CODEBASE
Affinity_Feedback_Loop_Logic
Like
Dislike
LOCAL_STATE_RECONCILER
Scoring Engine

Weights IDs based on sentiment frequency.

Filter Pruning

Excludes content matching negative IDs.

Discovery Feed Re-Ranked

"Build for the users, not the resume."

I believe that technical debt is often a business decision, not just a coding one. My approach focuses on Maintainable Pragmatism, building what we need today while architecting for tomorrow's scale.

01

Product First: If a feature doesn't move the needle, the code is a liability.

02

Observability: If you can't measure it, you haven't finished the feature.