CSGJava Software Engineer, Product R&DFull-timeAug 2025 – present
Enterprise product engineering
Specification-driven services, shared validation, and quality practices in a large product R&D environment.
backend · integration · automation
I build software by figuring out how the pieces fit together.
I work mostly on backend systems, integrations, and automation. I like problems where there’s more to understand than the ticket itself—how the pieces interact, where things keep breaking down, and what can be made simpler.
Working note / delivery tracereviewable
follow the work from problem to release →
keep the important decisions recorded.problem → constraints
→ decision → documentation
keep the important decisions recorded.problem → constraints
→ decision → documentation
↻ feedback looprecord the trade-offs
01 / Selected work
Selected work experience.
A few engineering problems I've spent real time understanding, changing, and improving.
InfinIDBackend EngineerFull-timeSep 2024 – May 2025
Platform and integration engineering
API gateways, environment promotion, and delivery workflows that teams could review and change safely.
Bank Central AsiaSoftware Engineer, General LedgerFull-timeOct 2019 – Aug 2024
Ledger systems and data pipelines
General Ledger operations, ETL-style batch flows, and production discipline in a large retail bank.
02 / Featured writing
Writing about the decisions behind the work.
Case studies and notes from engineering problems I wanted to unpack further.
Featured writing · case study
Repeatable API-gateway delivery across environments
How I made API-gateway configuration easier to review and promote across environments.
Case-study summary
from the case study
Context
Gateway configuration had been handled differently in each environment. That made reviews manual and made it hard to see what changed during promotion.
Constraints
No customer data, internal hostnames, or unpublished architecture diagrams in public prose.
Approach
Separate environment-specific settings — put them in named configuration layers so reviewers could see what changed between environments.
The extra setup made sense because these routes changed often. For a route that rarely changes, lighter tooling may be enough.
contextconstraintsapproachtrade-offsoutcomes
Open case study ↗Featured writing · case study
Configuration playground for domain experts
An internal playground where analysts could test assessment-rule changes without production access or one-off engineer scripts.
Case-study summary
from the case study
Context
Loan assessment logic changes often start with analysts who understand credit policy but cannot safely experiment in production. Ad-hoc scripts and shared spreadsheets do not scale review, and every engineer becomes a bottleneck for “what if we changed this threshold?”
Constraints
No customer or production data in the playground; synthetic inputs only.
Approach
Keep policy exploration separate from execution — give analysts configurable scenarios with named inputs and expected outputs they could compare.
The playground was not a full staging clone, so some integration behavior stayed mocked. That was a deliberate limit: it let analysts test policy questions quickly without reproducing the entire core-banking environment.
contextconstraintsapproachtrade-offsoutcomes
Open case study ↗Featured writing · case study
Legacy batch jobs to SQL pipelines
Moving COBOL-era batch processing toward observable, idempotent ETL while keeping the remaining mainframe work in view.
Case-study summary
from the case study
Context
A General Ledger organization still depended on a large COBOL batch estate. Teams needed faster change cycles, better observability, and pipelines that could survive retries without corrupting accounting state.
Constraints
Financial correctness mattered more than migration speed; partial automation could be worse than slower automation with evidence.
Approach
Inventory the real batch graph — which jobs are pure transform, which encode business rules, which are safe to parallelize.
Not every job belonged in the first migration wave. Some stayed on legacy paths until the test harnesses and sign-off process caught up. The work established a way to move jobs safely over time, rather than trying to replace everything at once.
contextconstraintsapproachtrade-offsoutcomes
Open case study ↗03 / Engineering habits
A few habits I keep using.
Across different teams and problems, these habits have kept proving useful.
Separate what changes from what stays the same
Make the differences that affect behavior visible instead of burying them in special cases.
Seen in
Enterprise product engineering · Applied computer vision thesis system · KrakenD infrastructure-as-code toolkit · Repeatable API-gateway delivery across environments
See related work ↗Make the next change easier
Turn one-off delivery steps into documented, tested steps people can use again.
Seen in
Ledger systems and data pipelines · Enterprise product engineering · Platform and integration engineering · Containerized backend demos
See related work ↗Keep ownership clear
Make it clear which service owns what, how the interfaces work, and who makes each decision.
Seen in
Ledger systems and data pipelines · Enterprise product engineering · Platform and integration engineering · Accessible mobile engineering
See related work ↗04 / Projects
Independent projects and experiments.
Portfolio publishing pipeline
Astro portfolio site with Markdown-backed content and a clear split between private drafts and public pages.
astrocontent-pipelineportfolio
Open project ↗KrakenD infrastructure-as-code toolkit
CLI and templates for API-gateway configuration across environments, with container build and publish automation.
krakendplatformopen-source
Open project ↗Applied computer vision thesis system
Web-based physical-distancing detector using object detection and deep learning, later developed into a published thesis project.
computer-visiondeep-learningresearch
Open project ↗05 / Writing
Writing things down is part of how I think.
Some ideas need a full case study. Others are useful as a short note. Writing helps me explain the decisions clearly.
06 / Contribution
I also spend time teaching, mentoring, and reviewing technical work.
Courses, capstone teams, curriculum work, code reviews, and community programs alongside engineering.
40Instructional sessions(Teaching + tutoring · 2022–26)
54Mentoring and facilitation sessions(2023–present)
4.67–4.95 / 5 · avg 4.78Teaching/tutoring ratings(Recent ratings · averages include ratings above 4.5)
4.73–5.0 / 5 · avg 4.95Mentoring ratings(Recent ratings · averages include ratings above 4.5)
Instructor + advisor
Dicoding partner programs
Coding Camp, Bangkit, AWS Back-End Academy, Asah, and PIDI Digdaya.
Instructor + mentorRakamin · BNI ODP
DevSecOps instruction and final-project mentoring.
Student mentorStudent mentoring programs
Structured mentoring for vocational and university students through Microsoft Future Ready and Samsung Solve for Tomorrow.
Community contributionCode in Place · ADPList · community sessions
Introductory programming instruction, one-on-one mentoring, and community teaching.