Twenty-odd years of keeping servers boring.
I last touched my résumé in 2018. I'd rather point you at working tools than a PDF, so here's the honest version instead.
I've been doing this since 2003. Long enough to watch the same problems come back wearing new names, and long enough to have written a script for most of them. The control panels changed, the virtualization stacks changed, the job never did: keep it up, keep it fast, keep it secure.
The long version.
I started in Kerala in 2003, fresh out of a Bachelor's in IT from CUSAT, and taught myself into hosting support back when "the cloud" was still just a shape someone drew on a whiteboard. The early years were a run through the hosting trade. Support Resort, then Crystal Clear, where I went from a level-one agent to running the support team, then a stretch of smaller shops. All of it living inside cPanel, Plesk and DirectAdmin, learning servers the way you only can when you're the one who has to fix them at 2am.
Then a decade as a senior systems analyst at Virtacore, managing a couple hundred mixed Windows and Linux VMs and holding the line on five-nines uptime, followed by a move to Zone Networks in Sydney doing much the same at scale on Hyper-V. Virtuozzo gave way to OpenVZ gave way to VMware and Hyper-V and, eventually, LXD and a bit of Kubernetes. The logos on the dashboard kept changing. The actual work (availability, performance, security, and being the person other people escalate to) stayed exactly the same.
Since 2019 I've been at BigScoots. I came in as a support tech, made shift supervisor within a year, and by 2022 was the support manager for evening hours. The focus narrowed to WordPress, managed and shared hosting, across the support desk, live chat and Slack. On nights I'm the point of contact the team escalates to, and I sit on the support committee that handles shift scheduling and how everyone's actually holding up. Most of what I resolve still comes down to the same two things: a well-aimed bash script, and knowing which plugin is lying.
I've always built my own tools.
This is the part a résumé can't show. Back in 2005 I was installing port-scan detectors, system-integrity monitors and brute-force detection across server fleets, because if I had to do a thing twice, it became a script. Twenty years later that instinct hasn't changed; it's just wearing better clothes. The bash one-offs grew up into proper Go programs I build and maintain in the open:
sysmon-gov is a real-time terminal dashboard for LEMP and WordPress servers, for the moment you SSH into a misbehaving box and need an answer in five seconds. wpscan is a WordPress security scanner that enumerates what's exposed across a fleet, because most WordPress compromises are an unpatched plugin nobody was tracking. Same job I was doing in 2005 with a portscan detector. Better tools now, and out where anyone can use them.
Off the clock.
Still tinkering, mostly. I script Roblox games with my kid, wire up Arduino projects that play melodies they were never meant to, and spend an unreasonable amount of time making my terminal look nicer than it strictly needs to. The habit that started this whole career never really switched off.
Want to talk?
I am not on the market. I am settled at BigScoots and happy there. That said, I read every message, and a genuinely interesting infrastructure problem is hard to turn down. The résumé is out of date. The tools aren't. Start with either.