3 years building systems that stay quiet under load. I design REST APIs, break monoliths into microservices, and keep the part nobody sees behaving like it does.
On courtJava backend engineer from Jakarta. Government, finance, banking, insurance, healthcare — different domains, same job.
I'm a Java backend engineer based in Jakarta. Over the last three years I've shipped backend systems across government, finance, banking, insurance and healthcare. Different domains, same job: make the part nobody sees behave like it does.
My core stack is Java and Spring Boot, but the work I care about sits a layer above the language — designing REST APIs that don't need a wiki to use, structuring services with clean architecture and clear domain boundaries, splitting monoliths into microservices that talk over Kafka or RabbitMQ without losing messages, and locking it all down with proper RBAC and Spring Security.
I also care about what happens after the merge. Reliable CI/CD pipelines with Docker, Jenkins, GitLab and Kubernetes. Test coverage that actually catches things. Structured logging into Elasticsearch and Kibana, and Grafana dashboards that turn a 2am incident into a five-minute fix instead of a guessing game. Honest systems beat clever ones — every time.
Off the clock I'm easy to grab coffee with. Weekends are usually a tennis court or a basketball half-court — the best way I've found to reset after a production incident.
Current form — what's on the clock and what's off it.
Rebuilding the apps that take a patient end-to-end — from registration, to doctor consultation, to appointment tracking — with integrations that sync medical history across the systems that need it.
Weekdays for keyboards, weekends for racquets and rims. Still the best way I've found to reset the brain after a production incident.
Whether you want to talk system design, REST APIs and microservices — or trade tips on your tennis backhand — happy to chat either way.
Four clubs, four seasons. The scores are the numbers that actually moved.
7 reels. Open any row for the detail and the screenshots.
The number is years on the pitch. The line underneath is what it actually does for me.
Or you just want to swap notes on system design, Spring Boot, healthcare integrations — or your tennis backhand. Drop a line; I usually reply within a working day.