Software Engineer · Jakarta, Indonesia
I'm at my best when a feature has to stretch across more than one codebase and somebody needs to make the seams not leak. Payments, communication platforms, AI automation — the kind of work where the interesting bug is always at the boundary.
Currently building at Luce SG.
- System design across boundaries — drawing the right lines between services, data, and teams so future change stays cheap.
- End-to-end feature ownership — from spec and stakeholder alignment through architecture, rollout, and the post-launch debugging nobody volunteers for.
- Reliability and observability — making it possible for a small team to operate a system that punches above its weight.
- Platform and tooling thinking — the multiplier work that compounds across everyone else's velocity.
AI assistants are a real part of how I work. They shorten the loop between idea and prototype, take care of the mechanical parts, and let me spend more time on the parts that actually need judgment — architecture, tradeoffs, and knowing what "done" really means.
Used well, they raise the ceiling of what a single engineer can ship.
- event_timeline — replay every method call from any Rails request. The closest thing I have to "but it works locally" insurance.
- redacted — secret-redacting proxy for AI coding assistants.
