Backend Architecture
Distributed Systems Platform
Backend services for event intake, queue processing, and basic monitoring so the team could see what was happening under load.
TypeScriptNode.jsPostgres
Queues and monitoringContact ->
Software engineer / full-stack builder
Amirul
I build web apps that are clear to use, easy to maintain, and steady in production.
I work across frontend and backend: React and Next.js on the interface side, Laravel, APIs, databases, and AWS behind it.
System Snapshot
Portfolio runtime
ServicesLive
Pipeline
pass typecheck
pass lint
watch p95.latency
Signal quality94%
Frontend
React / Next.js
Building responsive screens with reusable components and the App Router.
Backend
Laravel
My main backend stack for APIs, business logic, and integrations.
Cloud
AWS
Hands-on with EC2, RDS, S3, ALB, and CloudWatch in production work.
Database
MySQL
Designing schemas, improving queries, and supporting reporting features.
Learning
In Progress
Currently learning more Docker, Kubernetes, system design, and AWS architecture.
Beyond Code
Runner & Gamer
Morning runs, story-driven games, and time behind a camera.
Portfolio
Engineering projects
A few examples of the kind of work I enjoy: useful dashboards, backend services, internal tools, and systems that need to stay understandable as they grow.
Frontend Engineering
Product Operations Dashboard
A dashboard for product metrics, support cases, and handoffs, built for daily use by people who need quick answers.
Next.jsReactTailwind
Daily team workflowsContact ->
$ pnpm test:contracts
pass workflow.graph.ts
pass release.pipeline.ts
generating typed client...
done 18.4s
Internal Tools
Developer Workflow Tooling
Small tools and automation for repeated engineering tasks, with faster checks during reviews and releases.
APIsCI/CDDX
Review supportContact ->
Toolkit
Tools I use often.
Next.js App Router
React UI systems
TypeScript contracts
API integration
PostgreSQL models
Auth flows
Performance budgets
CI/CD hygiene
Observations
Photography, after hours
A hobby, not the main act. I use photography to slow down, notice light, and get better at composition.
Street light
Kuala Lumpur
Quiet water
After hours
Hard edges
Concrete study
Open sky
Travel notes
Profile
MY / UTC+8A
Software engineer who enjoys clear systems, tidy interfaces, and photography after work.
UI
Product surfaces
API
Service contracts
About
I like building the useful parts first, then making them easier to use.
I care about software that makes sense from the first screen and still behaves well after release. Most of my work is a mix of planning flows, building components, connecting APIs, and fixing the rough parts that users notice.
Start with the structure
I like to understand the flow, the data, and the failure cases before polishing the screen.
Keep screens readable
I prefer interfaces that are easy to scan, especially for dashboards, forms, and admin tools.
Do the small things properly
Loading states, empty states, access checks, and edge cases matter once real people start using the work.