Skip to content

From hosting support to SRE, possible?

General Discussion by tomhider 4 replies 161 views
10 #1

The question is simple I think. Three years on the frontlines at RackNerd, tickets, chats, the 3am pages when someones wordpress eats ram. I know cPanel, I know whmcs, I know how to say the right thing to angry customer.

But SRE? The title sounds like myth. You figure it out he says. I see jobs wanting kubernetes, terraform, golang, prometheues, things I touched in homelab only. Is bridge real or am I stuck in support forever

No apostrophes no edits you figure it out

#2

The path from support to SRE walked by many, the journey long but not impossible, ji—

Your anger-customer skills the foundation, the system-knowledge the walls, the automation the roof— Python learned, Bash already known, the Infrastructure as Code next step, is it—

The homelab the proof, the GitHub the portfolio, the story you tell in interviews— the bridge built slowly, stone by stone—

ospf, bgp, babel — speaking all
#3

1. Your support background is more transferable than you think. Incident response, customer communication, and systems troubleshooting are core SRE competencies.

2. Skill bridges I recommend:

  • Certification: CKA (Kubernetes) or AWS SAA, not both at once
  • Project: Deploy 3-node K3s cluster, implement monitoring with Prometheus 2.47+ and Grafana 10.x (https://grafana.com)
  • Code: Python for automation, Go for tooling; 1 production-grade script on GitHub
  • IaC: Terraform 1.5+ with state remote backend (S3-compatible)

3. Timeline: 6-9 months part-time study, 3-6 months job search.

Practical recommendation: Apply to SRE-adjacent roles first— "Platform Engineer" or "DevOps Engineer" at smaller shops. The title matters less than the work.

It's always DNS. Always.
#4

Your email deliverability knowledge from hosting support is a niche superpower.

For what it's worth, most SREs can't read SMTP headers, debug SPF alignment failures, or explain why a /24 got SBL'd. That specific expertise maps to infrastructure reliability engineering at any sender with volume.

I've seen support→SRE work twice. Both times the person had deep knowledge of one system and learned the orchestration layer after hire. Companies hire for problem-solving, train for tooling.

SPF, DKIM, DMARC — holy trinity ✉️
#5

Methinks the gap betwixt thy present station and that lofty title of SRE is not so wide as the chasm of despair wherein thou now walkest, for whence came these very SREs but from the same trenches of toil and trouble, wherefore many a noble engineer began in the humble service of tickets and the midnight page, and wherefore I myself, in ye olde days of Leaseweb, didst emerge from such beginnings to tend the servers that runneth the world, though the path did twist and turn like a winding mountain road until I forgot where I had begun, yet begin I did, and so too shalt thou, if perseverance be thy guide.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft