Full-stack engineer
Fintech payments and core banking. I design the system, secure it to financial-grade standards, and operate it in production.
Works in
Go · Swift · Kubernetes · PostgreSQL · System design · Monitoring and observability
Secures with
FAPI 2.0 · mTLS · OAuth 2.0
Three engagements, three different ways of working. I architect and lead the build, implement the security standards, and advise the organisations adopting them.
Architect and lead
Bank-integration logic was being re-implemented for every provider. I rewrote the boundary so it could not be.
Account-to-account payments for Southeast Asian merchants. I restructured the Go service layer around SOLID boundaries so bank-integration logic stopped being re-implemented per provider.
Go · NATS JetStream · gRPC · Kubernetes · OpenAPI
Security specialist
The bank's REST surface stops at my boundary. Downstream services never see a provider change.
Banking-as-a-service in the Philippines. I implement the Financial-grade API security profile, mutual TLS in both directions, and the webhook delivery the bank exposes to its clients.
Go · FAPI 2.0 · mTLS · OAuth 2.0 · gRPC
Advisor
I graded where they stood, mapped it against FAPI and SNAP, and wrote the path between.
Advisory engagement with a state-owned Indonesian financial institution. I graded API and security capability against a maturity model, mapped the gaps against FAPI and SNAP, and wrote the roadmap.
FAPI · SNAP · OAuth 2.0 · mTLS · API governance
Native iOS
An AI barista trainer built at the Apple Developer Academy. Speech to text and text to speech drive a role-play that runs against a cafe's own standard operating procedure.
Swift · SwiftUI · Speech · AVFoundation
Game development
A detective game built at the Apple Developer Academy on SpriteKit, with a GameplayKit entity-component system and custom particle work.
Swift · SpriteKit · GameplayKit
A board is the contract. It holds who is working on what, and ticket comments are the only channel agents talk through. Anything a downstream agent needs has to be written onto the ticket, because the ticket is all it can see.
The model that builds is never from the same family as the models that test, verify, and review it. Same-family review repeats the same blind spots, so a gate that shares the builder's training is not really a gate.
Independence goes on the spec, capability goes on the code. Checking code against a written contract is objective, so the strongest model does it. Judging whether the spec matches what the user actually asked for has no gate below it, so a second model reviews it before work starts. A wrong spec passes every later gate green and ships the wrong feature.
When the orchestrator takes over a build, it cannot also be the gate on its own work. An independent reviewer has to pass the change first, on the acceptance criteria alone.
Loops are bounded on the record itself, with attempt counts, leases, and a spend ceiling, rather than by instructions written in prose. Infrastructure failures never consume the retry budget: an empty response from a flaky runner is not a failed attempt.
Jun 2021 to present · Jakarta, remote
Technical Lead
Mar 2023 to present
Promoted
Software Engineer
Jun 2021 to Mar 2023
Dec 2019 to Jun 2021 · Tangerang Selatan
Full-Stack Engineer
Dec 2019 to Jun 2021
Sep 2018 to Dec 2019 · Jakarta
Formerly Arkademy Edu Tech. Part of Amoeba, Telkom Indonesia.
Front-End Engineer
Sep 2018 to Dec 2019
2023
The Linux Foundation
2026
iOS Development Program, Indonesia
Native iOS and Swift under Challenge-Based Learning: problem framing, research, lo-fi prototype validation, and feasibility scoping to tight deadlines. Frequently led teams and drove delivery.
2025 to 2028 expected
Bachelor of Computer Science, Surabaya
Returned to complete the degree while working full time as a software engineer.