CSGJava Software Engineer, Product R&DFull-timeAug 2025 – present
Product R&D — configuration and validation systems
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 on backend systems, integrations, and automation. Much of the job is tracing how services interact, finding where a fix affects another path, and making those changes easier to review.
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
A few engineering problems I've spent real time understanding, changing, and improving.
InfinIDBackend EngineerFull-timeSep 2024 – May 2025
Backend & platform engineering
Backend services, API gateways, deployment tooling, and integrations for a loan platform.
Bank Central AsiaSoftware Engineer, General LedgerFull-timeOct 2019 – Aug 2024
Ledger systems and data pipelines
Backend and batch-processing work for General Ledger systems in a large retail bank.
02 / Featured writing
Case studies behind the work.
A closer look at the problems, constraints, and decisions behind the implementation.
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. Testing a policy change often required an engineer to run a script or interpret spreadsheet changes before analysts could compare the result.
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 limit 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 migration stayed incremental: jobs moved only after the required tests and sign-off process were ready.
contextconstraintsapproachtrade-offsoutcomes
Open case study ↗03 / Engineering habits
Recurring engineering patterns
Related work, projects, and writing are grouped below.
Separate what changes from what stays the same
Make the differences that affect behavior visible instead of burying them in special cases.
Seen in
Product R&D — configuration and validation systems · KrakenD infrastructure-as-code toolkit · Applied computer vision thesis system
See related work ↗Make the next change easier
Turn one-off delivery steps into documented, tested steps people can use again.
Seen in
Product R&D — configuration and validation systems · Repeatable API-gateway delivery across environments · Legacy batch jobs to SQL pipelines
See related work ↗Keep ownership clear
Make it clear which service owns what, how the interfaces work, and where each decision belongs.
Seen in
Product R&D — configuration and validation systems · Repeatable API-gateway delivery across environments · System assessment before commitment
See related work ↗04 / Projects
Independent projects and experiments.
Portfolio publishing pipeline
Astro portfolio site with Markdown-backed content and a typed publishing workflow.
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 from the work and its edges.
Case studies and shorter notes on the decisions, constraints, and lessons behind the work.
System assessment before commitment
Why a short system assessment helps before a team commits to a rewrite.
ReadOpen ↗
Configuration playground for domain experts
An internal playground where analysts could test assessment-rule changes without production access or one-off engineer scripts.
Case studyOpen ↗
Legacy batch jobs to SQL pipelines
Moving COBOL-era batch processing toward observable, idempotent ETL while keeping the remaining mainframe work in view.
Case studyOpen ↗
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)
58Mentoring 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.
Want to talk?
If something here overlaps with what you're working on, feel free to get in touch.
Email me ↗