Healthcare Platform · 2025
EMR Information System
Electronic Medical Records platform for healthcare facilities
Open to new opportunities
Full Stack Software Engineer with hands-on experience building scalable web applications. Focused on designing secure, maintainable, and high-performance systems that solve real business problems.
Indonesia · Currently at PT Gajah Nusantara Raya · Open to new opportunities

A few products I've built end-to-end — from initial architecture through production.
I build systems that are secure, maintainable, and built to scale — not just to ship. Every architecture decision should make the next feature easier to add and the next bug faster to find.
Clean code and clean architecture aren't opposites of speed — they're what makes speed sustainable. I apply modular patterns and proper separation of concerns so teams can move fast without breaking things.
Real business problems deserve real solutions. I focus on understanding the domain first — whether it's financial transactions, medical records, or training systems — then engineer the right abstraction, not the most impressive one.
The problem, the architecture decisions, and what actually happened after shipping — not just a screenshot gallery.
Where I've worked and what I was responsible for.
Feb 2026 — Present
Indonesia
Developing full-stack web applications and scalable REST APIs with authentication, role-based access control, and third-party integrations. Responsible for backend performance, server deployment, and production reliability.
May 2024 — Jul 2025
Indonesia
Responsible for developing features in the Electronic Medical Records (EMR) Information System and mentoring web developer interns.
Sep 2023 — Dec 2023
Indonesia
Investigated existing issues and collaborated with the Training (Diklat) Team to design and develop a web-based training information system.
Mar 2023 — Jul 2024
Universitas Kuningan, Indonesia
Responsible for developing the skills and academic knowledge of all members through structured learning-with-doing programs in the field of Information Technology.
Tools and technologies I reach for most, grouped by where they fit in a system.
The same seven-step loop, whether it's a weekend project or a system a team depends on.
Understand the actual problem before touching a design tool or an editor — talk to the people who will use it, map the constraints, and question the assumed requirements.
Break the problem into shippable increments. Define what "done" means for the first increment before writing the second line of the plan.
Decide what needs to be durable, what needs to be fast, and what can be simple. Most systems fail from complexity added too early, not too late.
Build in vertical slices that are demoable end-to-end, not horizontal layers that only come together at the very end.
Test the failure paths as deliberately as the happy path — most production incidents live in the code nobody wrote a test for.
Ship behind flags, roll out gradually, and make rollback boring. A deploy should never be the scariest part of the week.
Treat production feedback as the real spec. Monitor, listen, and keep the system legible enough that the next engineer — including future me — can safely change it.