I started my career staging routers in a warehouse in Muscat. No playbook, no senior engineer watching over my shoulder — just equipment, documentation, and the expectation that it would work when customers plugged it in.
That was 2008.
What Changes
The gear changes. The protocols evolve. Cloud replaced a lot of what used to live in racks.
But the problems that actually matter — the ones that wake you up at 2am, the ones that require a calm voice and clear thinking when everything is on fire — those don’t change much at all.
What Stays the Same
Diagnosis is everything. The engineers who can quickly separate correlation from causation, who know when to follow the data and when the data is misleading them, are the ones who solve the hard problems. Tools and certifications help. Pattern recognition built over time helps more.
Communication is the skill nobody teaches. Technical depth gets you in the room. The ability to translate what’s happening for customers, leadership, and engineering teams simultaneously is what keeps you in the room. I’ve seen brilliant engineers fail at this repeatedly.
The field rewards people who stay curious. The CCIE wasn’t my endpoint. Neither was joining Cloudflare. The moment you decide you know enough is roughly the moment you start becoming obsolete.
Where It Lands
I’m now a Customer Reliability Engineer, working with some of the world’s largest organisations on the reliability of infrastructure that serves a meaningful fraction of global internet traffic.
The problems are different in scale. The fundamentals are the same ones I was learning in that warehouse in 2008.
Start with what you actually know. Work from evidence. Communicate clearly. Stay curious.
That’s it. That’s most of it.