

01 / Enterprise experience
Building and maintaining enterprise web platforms where accuracy, reliability, and collaboration matter.


Chapter 000Issue #0Prologue —
A story about building software, solving real problems, and keeping things in production.
Full-Stack Software Engineer
Somewhere between the interface and the database, the work begins.


I build production-ready products that connect polished interfaces, reliable APIs, and real business workflows.


Working across product, engineering, and business domains…
…I turn requirements into reliable systems that deliver real impact.






Now, let’s dive into the projects, the journey, and the thinking behind them.
Next chapter —001 The works

Chapter 001Issue #1
The engineer behind the build.
I’m a full-stack software engineer building reliable, maintainable, and business-aligned web applications.
Scene 01 — The beginning


It started with a simple curiosity — how software solves real problems in the real world.
Scene 02 — What shaped me


Building and maintaining enterprise web platforms where accuracy, reliability, and collaboration matter.


Translating business requirements into product features, data-heavy interfaces, and reliable backend services.


Connecting user experience, frontend implementation, backend behavior, and business logic into one cohesive solution.
Scene 03 — My arsenal




More than just tools — they’re the building blocks I use to turn ideas into real, impactful products.


Products, systems, and experiments shipped.
Projects shipped13
A focused set of projects that represent my full-stack product engineering approach across interfaces, APIs, workflows, and reliability.

AI image generation app inspired by DALL-E workflows.
Built a full-stack image generation app with focused React UX and API-backed generation flow.

News feed and discussion UI with GraphQL-driven data.
Implemented a Hackernews-style interface with Apollo Client and React query lifecycle control.

Electronic medical record interface for capstone delivery.
Designed and shipped a healthcare-focused record UI for Generasi Gigih capstone scope.
The disciplines used to move products forward.
What I bring

Draw it first, then build it.
Full-stack engineering strengths I apply across product interfaces, APIs, workflows, and production systems.
Build React and Next.js interfaces that stay maintainable across complex product flows, role-based access, and reusable component systems.


Develop and integrate REST APIs, Go service layers, DTOs, repositories, and database-backed business logic.


Translate financial and operational rules into reliable product flows, including approvals, settlements, journals, reporting, and retries.


Investigate issues through logs and tracing, improve observability, write unit tests, and reduce regression risks in production-facing systems.


Production lessons earned in real teams and systems.
Roles and teams

Roles where I shipped production-facing web products across frontend interfaces, backend services, financial workflows, and cross-team delivery.
Built full-stack financial ERP features for KlikTemas Beyond across Go services, React UI, PDF generation, settlement flows, and production tracing.


Built Qlola Cash Management features for BRI across Account Receivable, Mass Transfer, RBAC interfaces, micro-frontends, and service reliability.


Built the Mitreka dashboard frontend with Next.js, combining UI/UX analysis, API integration, and real-time data interaction.


Built client-facing frontend applications for robot control and web polling systems with scalable UI implementation and documentation.


Principles that keep the work dependable.
Working principles

I care about building software that is clear to use, maintainable to extend, and reliable enough for real production workflows.
Prefer clear component boundaries, explicit data contracts, and predictable state flow over one-off implementations.
Use typed content modules, reusable primitives, and composable section structure to keep the codebase evolvable.


Build interactions that remain understandable with keyboard navigation, semantic structure, and assistive technology.
Keep essential information available without motion and preserve semantic text even when decorative animation is used.


Treat performance as a product requirement by default, not post-launch optimization work.
Prioritize lightweight rendering paths, one-time viewport reveals, and strict control over heavy animation dependencies.


Use motion to clarify hierarchy, transitions, and state changes, not to decorate every element.
Centralize motion primitives, provide reduced-motion fallbacks, and avoid looping effects that distract from content.


The next story starts with a message.
Let's talk

Other ways
to reach me