Software architect — Indonesia
Architecture for payment systems that can't go down.
8 YoE building payment platforms at Blibli, DANA and ALTO Network. I specialize in scalable, high-availability systems, and I lead the full lifecycle: requirements and technical design through development, testing and production support.
- 8 yrs
- payments, wallets, cards
- 8 teams
- led onto one SDLC
- +30%
- gateway throughput, circuit-breaker design
- 6×
- sequence-number generation under contention
- −45%
- container image size, faster CI/CD
Selected work
Systems, and the decisions behind them.
01 Wallet API Gateway revamp
Architect and lead
Rebuilt the gateway in front of the wallet platform around a circuit-breaker mechanism, so it holds up through peak traffic.
- Throughput up 30%
- High availability held through peak traffic periods
- E-money and e-wallet integrations with multiple external parties, secured and scalable
02 Seller Wallet and Seller Partner Wallet
End-to-end development
Two products that extended Blibli's fintech ecosystem and gave merchant partners a way to manage their funds.
- Fund management for thousands of merchant partners
- A core internal framework that cut project setup time
- Pre- and post-development architecture documentation that sped up onboarding
03 Transaction Orchestration Gateway
Senior Software Development Engineer
A unified API that standardizes payment flows across internal services and hands execution to specialized payment teams.
- A monitoring and dispute-resolution platform that reduced manual audit cycles
- High-latency code paths refactored to take more peak load at no extra infrastructure cost
- Technical Decision Records, plus end-to-end tests for payment state transitions
04 Card Management System
Senior Software Engineer, then Backend Development Associate Manager
Mission-critical card management systems for clients, built for uptime and PCI-DSS compliance.
- 6× faster sequence-number generation under high concurrency, with database contention removed
- Container images 45% smaller, giving faster CI/CD and lower cloud cost
- A standard Spring Boot boilerplate that keeps all 8 teams architecturally consistent
Experience
Eight years inside payment platforms.
2016–2021
Blibli.com
- 2016 Blibli Future Program
- 2018 Associate Software Development Engineer
- 2020 Software Development Engineer
- 2021 Senior Software Development Engineer
2021–2022
DANA Indonesia
- 2021 Senior Software Development Engineer
2022–now
ALTO Network
- 2022 Senior Software Engineer
- 2025 Backend Development Associate Manager
Method
How I keep systems legible.
- 01
Document before and after
Architecture documentation before development and after it, so a new engineer can onboard from the page.
- 02
Record the decision
Technical Decision Records capture each trade-off, so the team can revisit it later.
- 03
Standardize the path
Boilerplates, integration-test frameworks and observability that every team starts from.
The stack I work in.
- Backend
- JavaSpring BootReactive programmingPHPCodeIgniter
- Data and messaging
- PostgreSQLMongoDBRedisKafka
- Platform
- DockerKubernetesCloudELKPrometheusGrafanaDatadog
- Frontend
- JavaScriptVueAngularJS