Time to Get Linux
-
@thanksajdotcom Some one in the comments mentions
The biggest Linux-related demands right now are for people with experience with Puppet (or Chef), Jenkins, and Amazon Web Services. None of these are hard to learn for an experienced Linux or Unix sysadmin, but unless you have production experience with them, it will be a hard sell to hiring managers, no matter how much Linux or Unix experience you have. Good luck.
Do you think this is true?
-
@lance said:
@thanksajdotcom Some one in the comments mentions
The biggest Linux-related demands right now are for people with experience with Puppet (or Chef), Jenkins, and Amazon Web Services. None of these are hard to learn for an experienced Linux or Unix sysadmin, but unless you have production experience with them, it will be a hard sell to hiring managers, no matter how much Linux or Unix experience you have. Good luck.
Do you think this is true?
Linux experience is Linux experience. If you are just running a few basic commands from the CLI and claiming you're some sort of guru, that's one thing. But if you're building out Linux servers in your spare time for various purposes that are just as easily applied in a business environment, then that's perfectly good experience.
The fact you have to have had a job where you used it is BS. How are you supposed to get a job without experience to begin with? Internship? Maybe. But a job? Building in your own dev environment and playing around with things is the best way to gain experience.
-
That being said, I'm sure @scottalanmiller could offer some insight on this.
-
@lance said:
@thanksajdotcom Some one in the comments mentions
The biggest Linux-related demands right now are for people with experience with Puppet (or Chef), Jenkins, and Amazon Web Services. None of these are hard to learn for an experienced Linux or Unix sysadmin, but unless you have production experience with them, it will be a hard sell to hiring managers, no matter how much Linux or Unix experience you have. Good luck.
Do you think this is true?
I would agree you have to be able to prove you can do it in an actual production environment. That might mean they grill you hard in the interview with real world tests (which every job I have gotten has been like that). Or give you a 60-90 tryout period or likely both. Most will chose someone with IT experience in the real world if they can get it - even if it's not actual Linux experience. Most Linux Admins I know started off as Interns.
-
@lance said:
@thanksajdotcom Some one in the comments mentions
The biggest Linux-related demands right now are for people with experience with Puppet (or Chef), Jenkins, and Amazon Web Services. None of these are hard to learn for an experienced Linux or Unix sysadmin, but unless you have production experience with them, it will be a hard sell to hiring managers, no matter how much Linux or Unix experience you have. Good luck.
Do you think this is true?
I don't think that this is overly true. Puppet and Chef are DevOps and tons and tons of Linux work remains that is not DevOps. Certainly DevOps is shifting workloads and is an important player but the DevOps space has had special concerns always. Certainly Puppet and/or Chef experience will help you.
I don't feel that production experience matters. Get a Chef server at home, go crazy. That's all people care about. Absolutely no one has long term or deep skills on this stuff yet, it is so new and so uncommon. And it isn't SMB or Enterprise that does it, it is "modern west coast" that does it and "traditional east coast" that does not.
AWS is very easy to get without doing it in a business. It's just a service, having "experience" on it is an odd thing. Unless you do something really different like write the certification for it, all experience is about equal.
-
@thanksajdotcom said:
Linux experience is Linux experience. If you are just running a few basic commands from the CLI and claiming you're some sort of guru, that's one thing. But if you're building out Linux servers in your spare time for various purposes that are just as easily applied in a business environment, then that's perfectly good experience.
This is broadly true, I would say. But there are things that businesses do that home experimenters often do not. But if you overcome those, like using a Jump server for example, and can talk intelligently about how you treated your home like an enterprise, then I think you are covered and actually in better shape.
-
@thanksajdotcom said:
The fact you have to have had a job where you used it is BS. How are you supposed to get a job without experience to begin with? Internship? Maybe. But a job? Building in your own dev environment and playing around with things is the best way to gain experience.
My big leap from doing normal UNIX to huge UNIX was because I volunteered and ran a full UNIX environment for a private school, designing and building every single system.
-
@thecreativeone91 said:
Most Linux Admins I know started off as Interns.
I actually know relatively few who started off as Linux interns. For example, I started as a development intern.
-
@scottalanmiller said:
@thecreativeone91 said:
Most Linux Admins I know started off as Interns.
I actually know relatively few who started off as Linux interns. For example, I started as a development intern.
None of them I know started as an Linux Intern... Just an intern at the company then became really good at Linux and was given a full time job.
-
@thecreativeone91 said:
None of them I know started as an Linux Intern... Just an intern at the company then became really good at Linux and was given a full time job.
Then yes, I'd agree with that being the most common path that I see.
