DevOps, SRE, and platform work from Jakarta
I lead infrastructure and reliability work for a multi-brand fintech operation in Jakarta. Most days that means AWS, deployments, migrations, and making sure real-time trading systems stay steady when the pressure is on.
I did not get into infrastructure through some neat master plan. I started with networks, Linux boxes, and the usual "can you just fix this one thing" work. That turned into cloud engineering, SRE, and eventually the kind of role where a quiet weekend usually means the prep was good.
Right now I lead infrastructure and platform reliability for a fintech operation with multiple brands and multiple AWS accounts. I spend a lot of time around Kubernetes, ECS, Terraform, CI pipelines, and observability tooling, but the real work is usually about safer change, clearer rollback paths, and fewer surprises in production.
The part I care about most is turning messy operational knowledge into something a team can actually use. Runbooks people trust. Migration plans with real stop points. RCAs that explain what actually happened instead of just satisfying a template.
Notes from infra work, usually written after the deploy is done and the pager is quiet again.
If a platform or DevOps interview wants to test real skill, it should look more like debugging, trade-offs, and change management than a whiteboard binary tree exercise.
Teams ask for calmer deploys, safer infra, and fewer incidents, then try to squeeze that work into somebody else's sprint. That arrangement usually breaks.
The useful skill is not memorizing Kubernetes YAML. It is understanding the system, knowing what to look up, and staying comfortable with the docs.
An uptime target sounds simple in a meeting until you turn it into downtime minutes, breach conversations, and the engineering work needed to support it.
Tools I touch often enough to have opinions about. Not everything, just the ones that show up in the real work.
AWS Still where a lot of my week goes · Terraform Useful until state reminds you who's in charge · CloudFormation I use it when the job calls for it · AliCloud Part of my MIFX years · Ansible Still handy when the servers are not containerized · Secrets Manager A better home for credentials
Kubernetes Powerful, but not a place to bluff · K3s Nice when you want less ceremony · Docker Still the quickest way to explain a runtime problem · Portainer Helpful when a simple UI saves time · ECS A calmer container story for some workloads · ECR Plain, reliable, does what it needs to
GitHub Actions Where a lot of release discipline lives · GitLab CI/CD Used it long enough to know its habits · OIDC Roles Better than passing credentials around
Prometheus Great once the alerts earn their keep · Grafana Useful when the dashboards stay honest · CloudWatch Basic, noisy, still unavoidable · Uptime Kuma Simple and honest · EventBridge More useful than it looks at first
Cloudflare Helpful at the edge, especially on bad days · WireGuard Fast and clean · OpenVPN Not pretty, but dependable · Tailscale Saves a lot of setup time · Nginx Still the reverse proxy I reach for first · Traefik Good when discovery matters
PostgreSQL The database I trust most · Aurora Managed convenience with trade-offs · TimescaleDB Very nice when time-series fits the problem · MySQL/MariaDB Familiar territory · Redis/Valkey Fast until everyone treats it like a database · Memcached Perfectly fine when simple is enough
Bash Still the fastest path from idea to automation · Python My usual glue language · Go What I reach for when the tool should feel solid
Incident Response Calm matters more than heroics · Runbooks Best written before the page · Root Cause Analysis Where the real learning should happen · On-call Teaches you what is actually brittle
The short version of how I got here, working backward.
Fulk Tech
Promoted into the lead role and now own the infrastructure side of a fast-moving fintech platform.
I look after infrastructure, CI/CD, and reliability across more than five AWS accounts. A lot of the work is technical, but a lot of it is coordination too: internal engineers, consultants, and business teams all touching the same production path.
MIFX (Monex Investindo Futures)
This was where I built a lot of the migration and monitoring muscle I still rely on.
I worked as an SRE on a multi-cloud fintech platform running across AWS and AliCloud. The job touched reliability, Kubernetes operations, databases, monitoring, and the kind of migration work that can quietly take over your weekends.
PT Maha Karya Perwira
This was the stretch where infrastructure stopped being abstract and became daily practice.
I worked across cloud and on-prem infrastructure, set up CI/CD around self-hosted GitLab and Nexus, handled migration work with Ansible, and built out monitoring with Prometheus and Grafana.
PT Transformasi Mindset Indonesia
This is where I realized I liked infrastructure work more than anything else in IT.
I managed network infrastructure and worked on system upgrades that improved transfer speeds by about 40%. More importantly, this was where I figured out what kind of work I actually wanted to keep doing.
BINUS University, Jakarta - 2017 – 2023
If you have an infrastructure problem, a role to discuss, or something interesting to build, send me a note.
Jakarta time
Loading local time...
UTC+7 --:--
The best emails tell me what you're building, what feels risky, and where you want help.
You found the secret! Try the footer quips too.