I’ve been a software engineer for 10 years now but want to work with Linux more in a professional setting (not to mention the number of layoffs in the the dev industry has me thinking a backup plan might be a good idea). I have been using Linux exclusively on my personal machine for about 15 years now so I’m not too worried about passing the LFCS but I’m wondering of its worth it. What kind of job opportunities would it open for me? Should I focus more on dev ops? Security? Straight SysAdmin?
It’ll really depend on your local job market. I was on a serious job hunt earlier this year and I couldn’t find a single Linux job which asked for LFCS certs. There were a couple which asked for Red Hat certs though. Of course, this could be specific to where I live, so I’d recommend looking at some popular job sites for where you live (+ remote jobs too) and see how many, if any, ask for LFCS, and you’d get your answer.
From what I’ve seen so far, the days of “traditional” Linux sysadmin roles are numbered, if not long gone already - it’s all mostly DevOps-y stuff. Same with traditional security, these days it’s more about DevSecOps.
As a modern Linux sysadmin, the technologies you should be looking at would be Ansible, Kubernetes, Terraform, containers (Docker mainly, but also Podman/LXD), GitOps, CI/CD and Infrastructure as Code (IaC) concepts and tools.
Some Red Hat shops may also ask for OpenShift, Ansible Tower, Satellite etc experience. IBM shops also use a lot of IBM tools such as IBM Could Paks, Multicloud Management, and AIOps/Watson etc.
And finally there’s all the “cloud” stuff like AWS, Azure, GCP specific things - and they have their own terminologies that you’d need to know and understand (eg “S3”, “Lambda” etc) and they have their own certs to go with it. I suspect a “cloud” cert will net you more jobs than LFCS.
So as you’d probably be thinking by now, all of the above isn’t something you’d know from just using desktop Linux. Of course, desktop Linux experience is certainly useful for understanding some of the core concepts and how it all works under the hood, but unfortunately that experience alone just isn’t going to cut it if you’re out looking for a job.
As I mentioned before, start looking for jobs in your area/relevant to you and look at the technologies they’re asking for, note down the terms which appear most frequently and the certs they’re asking for, and start preparing for them. That is, assuming it’s something you want to work with in the future.
Personally, I’m not a big fan all this new tech (I’m fine with Ansible and containers, but don’t like the industry’s dependency on proprietary techs like Docker Desktop, Amazon or Red Hat’s stuff). I just wanted to work on pure Linux, with all the all standard POSIX/GNU tools and DEs that we’re familiar with, but sadly those sort of jobs don’t really exist anymore.
Really great answer, I feel too like the focus is more on “cloud” tooling now.
I must have missed some news, when did it go proprietary?
Sorry, I guess I meant Docker Desktop, and some of their other proprietary business/enterprise tools (like Docker Scout) that companies have started to use, the stuff that requires a paid subscription. The Docker engine itself remains opensource of course, but a lot of their stuff that’s targeted at enterprises isn’t. These days when companies say “Docker” they don’t mean just the engine, they’re referring to the entire ecosystem.
Also, I have a problem with Docker itself. My main issue is that, on Linux, native container tech like Podman/LXD work, perform and integrate better (at least, from my limited experience), but the industry prefers Docker (no surprises there). As a Linux guy, naturally I want to use the best tool for Linux, not what’s cross-platform (when I don’t care about other platforms). But I can understand why companies would prefer Docker.
Ah I see what you mean, that stuff is pretty annoying.
Well at least the core tech remains open, though I agree, I would like to see more agnosticism from the industry in regard to the tool implementing the containers, since they’re pretty much all interoperable to a certain extent, as I understand
Docker is questionable open-source and depends on Dockerhub that isn’t open.
Dockerhub isn’t a hard requirement though, there are other container registries out there
No, but that’s what everyone ends up using and the thing is designed to work really well with dockerhub and not so much with others.