What certs should I cop (serious question)

[Rekeita's Kidneys]

I'm (attempting) to become a systems administrator/devops, whatever the fuck buzzwords corpofags use, and I am wondering what certifications I should get.
Currently I have my (rather useless) A+, and I've been staring at the RHCSA and whatever other bullshit security/networking certifications there are.
I'm getting a feeling I should just outright skip the "babby just started tech" shit and hop on to higher level stuff.

Anyone in here work that sort of line of work? I'm pretty damned knowledgeable regarding a lot of the related bullshit, just cannot figure out what direction to go.

 

[clara red bottoms]

Well, you could start with copping a feel of deez nuts.

 

[Rekeita's Kidneys]

Well, you could start with copping a feel of deez nuts.

goteeemmmm!!!!

 

[YHWH's Strongest Soldier]

Find vacancy notices for companies that you would like to be employed by. Make a list of certification required for the positions that you are interested in. The exact requirements regarding certification depend on your country of residence and desired career path.

 

[Rekeita's Kidneys]

Find vacancy notices for companies that you would like to be employed by. Make a list of certification required for the positions that you are interested in. The exact requirements regarding certification depend on your country of residence and desired career path.

Not a bad idea, I'll have to try and not become super specialized to the point of being locked into a single position tho lol.

I'm just directionless atm and everyone I've asked IRL has been useless (they all work in entirely different fields, eg welding)

 

[Disdainer of the Plebs]

Unserious answer: why bother? GPT is gonna crush you.

Serious answer:
There's a difference between a certificate and actually knowing what the fuck you're doing and applying that to a novel situation. The former is good, the latter is better. In my experience, most firms will hire a "devops" guy to cover up for the fact that they've hired a couple hundred barely-sentient pajeets with keyboards, and they can barely write javascript with the help of an AI. This means you have to be able to do a lot of just about everything to keep whatever it is you're maintaining online, because as soon as the pajeets fuck up, they will try to blame your infrastructure, especially when its obviously an application problem. ( Pajeet: "But saar, the application will be dying of out of memory code, platform is too small please do the needful." Me: "If the platform were out of memory, the whole thing would be dead. Besides, our EKS cluster autoscales to meet resource requests, stop underprovisioning your app, dipshit")

That being said, when it comes to devops, public cloud provider certs like AWS generally go over well, understanding containerization (like docker) would also serve you well. Learn a pipeline tool like github actions or jenkins. Knowledge of linux, shell scripting and a programming language (i prefer go, but python is also quite popular) are also important. If you want to go hard mode, learn Kubernetes, its almost impossible to find competent engineers with Kubernetes experience and not run deep into 6-figure salary (at least in America).

Finally, communication skills are paramount. A fully production ready infrastructure environment and CI/CD ecosystem are useless if you can't explain to devs how to use them. Figure out how to identify a good tech lead and get friendly with them, systems are meant to be used by people, so having people you can trust as leading users is incredibly useful in devops.