Active— open the full certificate imageCertified Kubernetes Administrator
The Linux Foundation · CNCF
Credential IDLF-qjayrafsqi
Verify with issuer Certified Kubernetes Administrator credentialDevOps Engineer · CKA Certified
I automate infrastructure, and I like knowing exactly what's happening underneath it.
I'm a DevOps engineer. Most of my day is CI/CD, infrastructure-as-code, and observability: the plumbing that lets a team deploy without holding their breath. What I actually enjoy is the layer below the tools: what happens after `kubectl apply`, why a node went NotReady, where a request goes after it leaves the load balancer. I find systems a lot easier to run once I understand them down to that level, so that's where I tend to spend my time.

Money saved, apps moved, people taught — the six results I can put a number against. Hover, drag or arrow-key a statue to read its plaque.
Drag to spin · ◀ ▶ to step through
The same six statues, in a dungeon you can walk around.
Kubernetes, Terraform and AWS. The certificate and credential ID are on each card, so you can check them at the source.
Active— open the full certificate imageThe Linux Foundation · CNCF
Credential IDLF-qjayrafsqi
Verify with issuer Certified Kubernetes Administrator credential
Active— open the full certificate imageHashiCorp
Credential ID51077bf6-864b-4303-adfe-58093adbbd47
Active— open the full certificate imageAmazon Web Services
Credential ID27e1b14d0c004dfc9459fcc6974b7dcc
Verify with issuer AWS Solutions Architect – Associate credential
Active— open the full certificate imageAmazon Web Services
Credential ID4e28c0854c614f75893e9fafce884841
Verify with issuer AWS Certified Cloud Practitioner credentialWhat I did in each role, and what changed because of it. Hover or tap a scroll to unroll it.
I'm based in the Indonesia office on a hybrid setup, working with a local team under an Austrian manager, on platform work for products that mostly serve Europe. I own that platform layer (provisioning, CI/CD, and observability), so the product teams can deploy on their own instead of routing every release through me.
Moved the internal apps off Docker Compose onto a production Kubernetes setup with GitOps delivery, sitting behind an API gateway with proper auth in front of it.
Taught Linux, networking, and the systems basics the rest of my work builds on to a bit over a thousand students, and kept the lab machines running while I was at it.
A whole Kubernetes cluster built from code, hypervisor and all, so I can tear it down and get the exact same one back.
Going from a bare hypervisor to an HA Kubernetes control plane entirely from code. No clicking through UIs, no nodes I configured once and could never reproduce.
Every time I wanted a Kubernetes cluster to test something, I'd end up clicking through the hypervisor UI, wiring up networks and storage by hand, and bootstrapping nodes one at a time. It worked, but no two clusters were ever quite the same, and with a single control-plane node, one bad reboot could take the whole thing down. I wanted a cluster I could destroy and rebuild from code and get the exact same thing back.
Declares libvirt domains, networks & storage pools
Bootstraps OS, container runtime & kubeadm
Reproducible VMs from a single golden image
kubeadm-joined control plane + workers
Virtual IP with load-balanced failover
Coursework and side projects, older than everything above. I was writing software before I was running it, and this is the software.
A Traveloka clone: fuzzy search across flights and hotels, bookings, transaction history, and then a WebSocket multiplayer layer and an image-location classifier I added because I wanted to know whether I could.
An arena RPG where three characters defend a crystal from golems. You control one and swap between them mid-fight; the two you are not driving run A* to intercept whatever is closing in. Each map is generated from Prim's algorithm crossed with binary space partitioning, so the obstacles land somewhere different every run.
A flashcard app built around SM-2. Every review session gets summarised and handed back to the algorithm, which reshuffles the deck for the next pass instead of showing you the same cards in the same order forever. Decks are shared, so you can search and study someone else's.
An automated clipping server I wrote because I got deep into the Valorant Champions Tour. It pulls highlights out of the live streams while they are still running, funnels them through the file system to a pool of worker nodes, and cuts them into something short-form that YouTube will take. The worker pool is switched off these days.
An airline operations desktop app covering planes, flights, logistics, finance and HR. Twenty-two roles is where the work actually was: every screen has to know who is looking at it before it decides what they are allowed to do to the record.
A forum for corruption cases: anyone can open a thread and the votes decide what rises. Behind it sits a Black Box that keeps those records immutable, so what gets posted stays on the record.
The tools I reach for to provision, ship, monitor and secure things.
Provisioning and codifying cloud and on-prem estates.
Running workloads reliably at scale.
Automated, auditable paths to production.
Metrics, logs, and uptime in one place.
Ingress, identity, and access control.
Automation, tooling, and services.