Profile
About me
This page covers the background, how I make decisions, and an employment history you can check.
In short
Who does this work
I came into IT through network cabling, not through a slide deck.
My vocational school specialisation was Computer and Network Engineering, and the first piece of work I was genuinely proud of was building a school-wide local network so digital exams could actually run. My way of working has not changed much since: the problem has to be genuinely solved, not made to look solved.
From there I moved to the less visible side: the servers, storage and networks that let everything else run. I learned that most of this work is about making a system maintainable by someone else — not about who types a command fastest.
Today I work on hybrid cloud infrastructure: virtualisation and storage clusters spread across more than one data center, container platforms for a product sold to clients, and automation for the work that should never have to be done manually twice.
If you want to know how my technical decisions get made, the Approach section below summarises it. For the employment and study history, the About page has it.
Approach
How I work
Four habits that decide how I make technical calls. These are not company values — they are things you can judge me on from the work itself.
01The problem first, the tool later
Most requests arrive as an already-chosen solution. I always trace back to the original problem, because the answer is often much cheaper — or turns out not to need building at all.
02A system that can be explained is easier to maintain
The cleverest solution is useless if only one person understands it. When the benefit gap is small I choose the simpler design, and write down the reasoning so the decision can be revisited.
03Measure before and after, not during the presentation
An improvement without a number is an opinion. I decide what will be measured before starting, and I still report the result when the number is not the one I hoped for.
04Translate, do not simplify
A technical explanation for a non-technical audience does not need a misleading analogy. It needs the right order: what the impact is, what the constraint is, and only then how it works.
Experience
Where I have done this work
Written as outcomes, not as a list of responsibilities. Every figure here can be traced to a case study on the Work page.
May 2024 – present
System Administrator & DevOps EngineerPT. Gema Teknologi Cahaya Gemilang (Thrive — IT consultant)West Jakarta
Designing and operating the infrastructure behind a new product line: a container platform sold to clients, two virtualisation clusters across data centers, and a production hosting fleet.
- Architected an 11-node Docker Swarm cluster from scratch — 1 dedicated Traefik ingress, 3 managers and 7 workers — to launch a Container-as-a-Service product line running around 300 active containers.
- Integrated the Portainer API with n8n workflows, so provisioning an application instance for a new client runs automatically with no manual setup.
- Ran two Proxmox VE clusters, each paired with a Ceph distributed storage cluster, across two physical data centers (IDC and Biznet TechnoVillage), totalling 56 TB of raw capacity.
- Provided S3-compatible distributed object storage with MinIO, alongside clustered PostgreSQL databases.
- Provisioned, hardened and maintained 12 WHM/cPanel servers — bare-metal and virtual — serving more than 1,000 active user accounts with zero critical downtime.
- Maintained production AWS infrastructure across multiple Availability Zones (EC2, VPC, ALB, IAM, Security Groups, CloudTrail) for enterprise accounts.
- Worked alongside the Security Operations Center: turning incident reports and Wazuh SIEM alerts into server hardening, firewall rules, IP mitigations and operating-system-level vulnerability fixes.
- Built distributed internal DNS with PowerDNS (1 primary, 2 secondary), routed internal traffic through HAProxy and Nginx Proxy Manager, secured the perimeter with Cloudflare, built WireGuard VPN gateways, and handled HPE ProLiant DL380 Gen10 hardware installations as tier-three escalation.
November 2023 – April 2024
IT Network & System AdministratorPT. Siscom ERP SoftwareWest Jakarta
Keeping client-facing ERP systems running while cutting recurring cloud spend by moving workloads back on premise.
- Repatriated 5–6 production workloads from AWS back to on-premise Proxmox virtualisation, cutting recurring cloud operating costs while keeping services online.
- Administered production Linux and Windows Server environments alongside multi-gigabyte Microsoft SQL Server databases serving many concurrent desktop ERP users.
- Kept office bandwidth, routing and VPN connectivity stable using MikroTik routers.
- Wrote Bash cron jobs for scheduled database dumps and system-state backups to self-hosted Nextcloud storage, removing the manual backup routine.
Education
Where the foundation came from
One vocational path that was hands-on from the start, and one academic path now under way.
2026 – present
BSc Information SystemsUniversitas Terbuka (Indonesia Open University)
Studying how technical infrastructure decisions connect to the wider organisational and business systems — the part whose absence is usually felt only when a budget has to be defended.
2020 – 2023
Computer & Network EngineeringSMKN Rajapolah (vocational secondary school)
Built a school-wide distributed LAN architecture for official digital examinations, and set up Linux web hosting environments with WHM/cPanel.
Areas of work
The areas I work in
Each area is explained by its impact first. Technical detail is available if you need it.
01Systems & infrastructure
Keeping the machines that run a service alive, secure, and unremarkable when something breaks.
Tools and technical terms9 items
02Virtualisation & storage
Pooling many machines into shared resources, so that one machine failing does not take a service down with it.
Tools and technical terms8 items
03Containers & automation
Making an application run and update the same way every time, without a manual step in the middle.
Tools and technical terms10 items
04Networking & service delivery
Designing the paths data travels, and keeping those paths fast and correct.
Tools and technical terms9 items
05Cloud & operational security
Using cloud services safely, and stopping the payment for the parts that turn out to be unused.