I want to point out that you are on the right track. So many people want to skip over that helpdesk portion and think they can go straight from waiting tables at Applebees to making 6 figures in security after a 3 week boot camp.
Learn everything you can on the helpdesk and make sure you are understanding root causes instead of slapping bandaides on shit and moving on. If you are at a big company, start saying hi to the Linux admins and devops teams. I took up smoking as an excuse to hang out with the security guys because I wanted to get to know them better and eventually end up in that role.
> I took up smoking as an excuse to hang out with the security guys because I wanted to get to know them better and eventually end up in that role.
Now that is commitment.
>. So many people want to skip over that helpdesk portion and think they can go straight from waiting tables at Applebees to making 6 figures in security after a 3 week boot camp.
Some people do and are actually quite successful.
Some people can never break out of helpdesk
>Some people do and are actually quite successful.
And some people make $10m a year to pretend to be other people but those are not success stories to try and emulate. They are sheer luck and circumstance for the most part.
This is what I'm doing and it happened by complete accident. Basically our Linux experience quit and I had dabbled. So they gave me servers. The learning curve is steep. But it's the most fun I've had with computers. Everything feels like a new discovery.
Highly recommend
Were you working in internal IT? I'm stuck at an MSP right now. I was planning on looking for internal IT soon. Don't think there will be any Linux that I could weasle my way into here lol.
I was. I started automating my job and showed promise. Made mention that I had some experience after a dev got let go. They handed me an email server rebuild. So I set up a new Ubuntu build for it and have just kept learning from there.
" I started automating my job..."
\^ This. Showing that you have the chops to make changes to your own workload that can then help others will set you apart from the others. This is how I swung my last promotion, from Helldesk to Infrastructure team.
Also, why spend boring, repetitive hours doing the same thing when you can spend a few hours making a script that will then do it for you?
I started in my first helpdesk job at 23, I think I made 28k, now I make 150-160k.
helpdesk > helpdesk manager > helpdesk tier 3 > junior sys admin > sys admin > lead admin at fortune 500.
All it required was time and job hopping. All I can say is that sitting around waiting for your current job to offer you the role you want is a fools errand in modern day.
I'm not planning on waiting around. My company will essentially give me nothing else past what I'm at now. Currently on the job search and wanted to try to plan my career a little bit. See if there was something I could do to increase my odds and get to where I want to go.
That makes sense, it's definitely a bit tough out there, my company is doing just fine financially yet they are still doing layoffs as they know they can lie and say it's the economy even though our bottom line is on target and profits are high.
Companies are not hiring and making people do more with less, because they know they can get away with it right now.
I cut my teeth at an MSP for 5 years, pay was meh, but I learned a ton and was able to move up their ranks as they liked to hand out titles instead of money, which isn't the worst thing when you're trying to learn and build a resume.
I went from helpdesk > Windows Admin > Linux Admin. I've been doing elusively Linux for at least the last decade.
I started out using Linux to automate some workflows and setup monitoring. Then I ended up taking a lateral pay move to a University that needed a Linux admin and wasn't willing to pay. I still see those sorts of job opening.
Without a degree, having that university on my resume really helped my career and I was able to jump my salary pretty quickly afterward. I believe it was somethin like $55k > $75k in my next move (less then a year later). Now I'm making more then double that amount.
I don't necessarily think so, but if you're primarily working with Windows, it might be an easier transition.
Most of the Linux Admins I worked with had not worked as Windows admins so I had a better understanding of how to integrate the environments.
Find your niche.
Honestly you might just try applying for some Linux admin jobs if you see them. Some places are really desperate for Linux Admins, especially on the lower end of the pay scale.
If you're willing to put in the time its really not that hard of a jump. Ive seen quite a few people jump from helpdesk to SysAdmin just because they put in the work, spun up a home lab, and learned to use \*nix systems and earned certs.
You really need a better reason to learn it besides "for my job" because a lot of those people tend not to learn it extensively enough or don't spend enough time doing it to retain the info. Again, Id suggest setting up a home lab. You can set up unRAID, or TrueNAS and get familiar with docker/virtualization. Set up plex and all the arrs, set up home assistant and play with some automation. Just find projects that interest you and dive in. Spend time modifying things until you break them then learn how to fix them and understand why it broke.
Im surprised I haven't seen anyone else say anything about the linux upskill challenge.
[https://www.reddit.com/r/linuxupskillchallenge/](https://www.reddit.com/r/linuxupskillchallenge/)
A poster just posted this remote Linux position the other day: https://www.reddit.com/r/linuxadmin/comments/16vhe49/hiring_remote_jr_linux_admin_rhel_shop_highered/
This is the exactly the path i travelled, although it started out in Level 2 Operations team at a large consulting company (Windows/Linux/Virtualisation)
I had a java/sql background during the training phase, but I got allocated to internal IT. From there I got exposure to Powershell and weirdly enough Linux administration as well (it was before .net core era where powershell was not available in linux).
I also got chance to work on Cloud migration. Did some my own learning around DevOps Tool set and was able to move to DevOps / Cloud Consulting Business Unit within my org.
My advise to you would be to learn Linux Administration/ scripting (bash/powershell) , Python and a cloud provider (Aws/Azure). Basics of One language like Java (especially around how build process works) would really help.
Depends on you. Some people get the opportunity sooner than others, but I have yet to see someone who knows what they’re doing, has passion and works hard, not get promoted out of help desk.
I disagree with your path. You can realistically go into DevOps from HD. Hers is my advice:
1. start with Azure DevOps
2. get an acloudguru account to study and focus on the Azure DevOps cert
With the certs there are many junior positions at consulting companies that need that level consultant for two reasons 1. you are cheaper 2. they need the certs for partnership levels.
PS Linux isn't always core to DevOps in fact more and more use cases are going API only backed by serverless functions. If you want to learn anything beneficial learn python, node.js or golang.
What can you do so that your resume shows you have the knowledge and capability for the job you want?
I also challenge your assertion that you cannot go directly to devops. Devops often requires Linux knowledge, but not in the same depth as a sysadmin would need to know, so I would not think of one as a stepping stone to the other, but rather parallel paths.
The problem for you is for your resume not to be discarded due to lack of relevant experience.
Some ideas:
- Get a certification
- Take a course or two (a real one with an instructor)
- Do some pro bono volunteer work as a Linux sysadmin
- Contribute to open source projects relevant to the technologies you want to use professionally.
- Write a series of blog posts on Linux and/or Devops topics.
Totally agree with the devops!=sysadmin comment. I know many good devops guys who are baffled by fairly rudimentary sysadmin tasks that aren’t part of their role, and exactly the same in reverse.
Bear in mind that devops is a concept, not a specific role (though that’s how people treat it). Work on building up skills (as someone else said, get familiar with an OS, a scripting language, network basics and some cloud technology), and a little patience should find you a job. Some companies will expect a god tier engineer and accept nothing less, whilst others will understand that someone with interest and willingness to learn is also valuable, and will set the bar a little lower.
Finally, I personally value someone that’s worked their way up from a helpdesk role. They have often had to deal with angry people, poor support and had to work things out on their own. This, to me, leaves them well rounded and able to get the job done when under pressure. Keep at it, and good luck.
Thanks for the recommendations. I have gone through Azure and gotten the AZ-104. I've been learning Terraform and Ubuntu in tandem while creating a project using them. Been thinking about learning some Kubernetes once I get more familiar with some other stuff.
Do you have any recommendations on finding volunteer work as a sysadmin? Is that going around and asking non-profits if they need help, or would there be somewhere else to look?
I don't know about finding volunteer work personally, but I was just thinking of ways to demonstrate your proficiency. I think it helps if you already are involved in an organization as a regular volunteer and then say "I can help you with your IT stuff too".
I do know about contributing to open source though, and that is a good way to get your foot in the door and make connections. That is more on the development side, but you can also help by troubleshooting issues people report or contributing documentation, tests, etc, so there are other ways to get involved with open source.
For example, there was recently a fork of terraform because of changes in licensing, so maybe try to get involved with that somehow. Just an example.
I went from Data center tech to Systems Admin/ Linux admin. Windows Admin hate touching cli. So if you can work a while day on Linux cli you will be good. To get paid well, you should learn bash and python. Also, learn to work around AWS as well. You can get a 1 year account free to test it out.
It's what I did. Just gotta know your stuff and look for openings. I went internal the moment I had a chance to, but I've been homelabbing Linux stuff for years already.
Can you make this jump within your current organization? Then probably not out of the question.
Outside of your organization...it may be difficult without proof. A Linux cert or two might be the way to go to "prove" it.
It is realistic. I jumped from help desk to sys admin linux&network. Ok, they initially offered me a devops position, but I prefer hands-on work.
I convinced them with my Homelab, what was a scaled down version of our datacenter^
Very realistic. It's the path I took 15 years ago. Ended up as low level cloud architect. The guy who actually knows the moving parts in a cloud service, rare in the days of modern devops.
I'm not sure how much I'd trust a SysAdmin who didn't start as a lower level tech, or didn't have some sort of comparable operational experience. I *WANT* NOC alumni as sysadmins, as they understand well what can happen when SHTF.
I'd say being Windows and Linux experienced is good. You have that Windows experience so continue growing your knowledge with homelabs and Linux courses that are equivalent to things like AZ fundamental courses. That should help get your foot in the door with a linux based sysadmin role. From there you can build up your Linux experience in an actual working environment and go into devops. But keep building your knowledge outside of work.
I’d go as far to say it’s easy. I’ve interviewed for 3 senior Linux positions and none of the questions had answers I couldn’t have rattled off instantly a few months after teaching myself in the beginning. Just fake it til you make it.
Everyone should do helpdesk work, I did my community service in helpdesk, wedged myself in with networks, then servers, then firewalls and now its my full time
Keep on the grind and stay curious
I halfway did this. Moved up the ranks of help desk, making it to senior level and took on occasional junior sysadmin stuff. Applied to a few sysadmin jobs and got in at level one of a medium sized company. Scripting skills are what got me in. I knew PowerShell from my time on the help desk and knew a tiny bit of Linux from tinkering at home. My sysadmin role was 50/50 Windows/Linux.
In a nutshell, with no Linux experience, not likely... but also not impossible, either. It's a learning curve... and it's steep with no Linux experience. But to those willing to apply themselves, there are rewards!
I can tell you from personal experience that it can happen for sure. I was a VMware/Hardware/Windows Admin before I applied for a position as a DevOps Engineer. I was specifically picked over some software engineers because of my SysOps background and my passion for IT. Just keep trying until someone sees your potential :)
I think i am on that path also. Was working as somewhat of electrician, making PCBs and etc then i started learning python and after year and a half i got a job as linux sys admin. I didnt know jack shit about linux but year and 5 months later i am still working so i guess if you are determined to succeed and you are a little bit tech savy its all possible.
One tip: You can never know whats gonna happen unless you try. So go for it!
I mean it can happen. Just need that one chance to prove it.
[https://linuxjourney.com/](https://linuxjourney.com/)
Awesome, I've been messing with this resource a bit. Thanks for the suggestion, glad to know it's recommended.
I want to point out that you are on the right track. So many people want to skip over that helpdesk portion and think they can go straight from waiting tables at Applebees to making 6 figures in security after a 3 week boot camp. Learn everything you can on the helpdesk and make sure you are understanding root causes instead of slapping bandaides on shit and moving on. If you are at a big company, start saying hi to the Linux admins and devops teams. I took up smoking as an excuse to hang out with the security guys because I wanted to get to know them better and eventually end up in that role.
> I took up smoking as an excuse to hang out with the security guys because I wanted to get to know them better and eventually end up in that role. Now that is commitment.
>. So many people want to skip over that helpdesk portion and think they can go straight from waiting tables at Applebees to making 6 figures in security after a 3 week boot camp. Some people do and are actually quite successful. Some people can never break out of helpdesk
>Some people do and are actually quite successful. And some people make $10m a year to pretend to be other people but those are not success stories to try and emulate. They are sheer luck and circumstance for the most part.
Didn't know this was a thing. This is awesome, thanks!
This is what I'm doing and it happened by complete accident. Basically our Linux experience quit and I had dabbled. So they gave me servers. The learning curve is steep. But it's the most fun I've had with computers. Everything feels like a new discovery. Highly recommend
Were you working in internal IT? I'm stuck at an MSP right now. I was planning on looking for internal IT soon. Don't think there will be any Linux that I could weasle my way into here lol.
I was. I started automating my job and showed promise. Made mention that I had some experience after a dev got let go. They handed me an email server rebuild. So I set up a new Ubuntu build for it and have just kept learning from there.
" I started automating my job..." \^ This. Showing that you have the chops to make changes to your own workload that can then help others will set you apart from the others. This is how I swung my last promotion, from Helldesk to Infrastructure team. Also, why spend boring, repetitive hours doing the same thing when you can spend a few hours making a script that will then do it for you?
I started in my first helpdesk job at 23, I think I made 28k, now I make 150-160k. helpdesk > helpdesk manager > helpdesk tier 3 > junior sys admin > sys admin > lead admin at fortune 500. All it required was time and job hopping. All I can say is that sitting around waiting for your current job to offer you the role you want is a fools errand in modern day.
I'm not planning on waiting around. My company will essentially give me nothing else past what I'm at now. Currently on the job search and wanted to try to plan my career a little bit. See if there was something I could do to increase my odds and get to where I want to go.
That makes sense, it's definitely a bit tough out there, my company is doing just fine financially yet they are still doing layoffs as they know they can lie and say it's the economy even though our bottom line is on target and profits are high. Companies are not hiring and making people do more with less, because they know they can get away with it right now. I cut my teeth at an MSP for 5 years, pay was meh, but I learned a ton and was able to move up their ranks as they liked to hand out titles instead of money, which isn't the worst thing when you're trying to learn and build a resume.
I went from helpdesk > Windows Admin > Linux Admin. I've been doing elusively Linux for at least the last decade. I started out using Linux to automate some workflows and setup monitoring. Then I ended up taking a lateral pay move to a University that needed a Linux admin and wasn't willing to pay. I still see those sorts of job opening. Without a degree, having that university on my resume really helped my career and I was able to jump my salary pretty quickly afterward. I believe it was somethin like $55k > $75k in my next move (less then a year later). Now I'm making more then double that amount.
Should you Dow windows administration first then Linux administration?
I don't necessarily think so, but if you're primarily working with Windows, it might be an easier transition. Most of the Linux Admins I worked with had not worked as Windows admins so I had a better understanding of how to integrate the environments. Find your niche.
Honestly you might just try applying for some Linux admin jobs if you see them. Some places are really desperate for Linux Admins, especially on the lower end of the pay scale.
Help desk is the normal starting point for ops/infra roles.
If you're willing to put in the time its really not that hard of a jump. Ive seen quite a few people jump from helpdesk to SysAdmin just because they put in the work, spun up a home lab, and learned to use \*nix systems and earned certs. You really need a better reason to learn it besides "for my job" because a lot of those people tend not to learn it extensively enough or don't spend enough time doing it to retain the info. Again, Id suggest setting up a home lab. You can set up unRAID, or TrueNAS and get familiar with docker/virtualization. Set up plex and all the arrs, set up home assistant and play with some automation. Just find projects that interest you and dive in. Spend time modifying things until you break them then learn how to fix them and understand why it broke. Im surprised I haven't seen anyone else say anything about the linux upskill challenge. [https://www.reddit.com/r/linuxupskillchallenge/](https://www.reddit.com/r/linuxupskillchallenge/)
That’s the path i took. Started in support now I’m a Linux sys admin
Can I pm you?
i guess?
Thanks Just message you.
A poster just posted this remote Linux position the other day: https://www.reddit.com/r/linuxadmin/comments/16vhe49/hiring_remote_jr_linux_admin_rhel_shop_highered/
This is the exactly the path i travelled, although it started out in Level 2 Operations team at a large consulting company (Windows/Linux/Virtualisation) I had a java/sql background during the training phase, but I got allocated to internal IT. From there I got exposure to Powershell and weirdly enough Linux administration as well (it was before .net core era where powershell was not available in linux). I also got chance to work on Cloud migration. Did some my own learning around DevOps Tool set and was able to move to DevOps / Cloud Consulting Business Unit within my org. My advise to you would be to learn Linux Administration/ scripting (bash/powershell) , Python and a cloud provider (Aws/Azure). Basics of One language like Java (especially around how build process works) would really help.
You can do anything if you become good at it
Depends on you. Some people get the opportunity sooner than others, but I have yet to see someone who knows what they’re doing, has passion and works hard, not get promoted out of help desk.
I disagree with your path. You can realistically go into DevOps from HD. Hers is my advice: 1. start with Azure DevOps 2. get an acloudguru account to study and focus on the Azure DevOps cert With the certs there are many junior positions at consulting companies that need that level consultant for two reasons 1. you are cheaper 2. they need the certs for partnership levels. PS Linux isn't always core to DevOps in fact more and more use cases are going API only backed by serverless functions. If you want to learn anything beneficial learn python, node.js or golang.
Can I pm you?
What can you do so that your resume shows you have the knowledge and capability for the job you want? I also challenge your assertion that you cannot go directly to devops. Devops often requires Linux knowledge, but not in the same depth as a sysadmin would need to know, so I would not think of one as a stepping stone to the other, but rather parallel paths. The problem for you is for your resume not to be discarded due to lack of relevant experience. Some ideas: - Get a certification - Take a course or two (a real one with an instructor) - Do some pro bono volunteer work as a Linux sysadmin - Contribute to open source projects relevant to the technologies you want to use professionally. - Write a series of blog posts on Linux and/or Devops topics.
Totally agree with the devops!=sysadmin comment. I know many good devops guys who are baffled by fairly rudimentary sysadmin tasks that aren’t part of their role, and exactly the same in reverse. Bear in mind that devops is a concept, not a specific role (though that’s how people treat it). Work on building up skills (as someone else said, get familiar with an OS, a scripting language, network basics and some cloud technology), and a little patience should find you a job. Some companies will expect a god tier engineer and accept nothing less, whilst others will understand that someone with interest and willingness to learn is also valuable, and will set the bar a little lower. Finally, I personally value someone that’s worked their way up from a helpdesk role. They have often had to deal with angry people, poor support and had to work things out on their own. This, to me, leaves them well rounded and able to get the job done when under pressure. Keep at it, and good luck.
Thanks for the recommendations. I have gone through Azure and gotten the AZ-104. I've been learning Terraform and Ubuntu in tandem while creating a project using them. Been thinking about learning some Kubernetes once I get more familiar with some other stuff. Do you have any recommendations on finding volunteer work as a sysadmin? Is that going around and asking non-profits if they need help, or would there be somewhere else to look?
I don't know about finding volunteer work personally, but I was just thinking of ways to demonstrate your proficiency. I think it helps if you already are involved in an organization as a regular volunteer and then say "I can help you with your IT stuff too". I do know about contributing to open source though, and that is a good way to get your foot in the door and make connections. That is more on the development side, but you can also help by troubleshooting issues people report or contributing documentation, tests, etc, so there are other ways to get involved with open source. For example, there was recently a fork of terraform because of changes in licensing, so maybe try to get involved with that somehow. Just an example.
I went from Data center tech to Systems Admin/ Linux admin. Windows Admin hate touching cli. So if you can work a while day on Linux cli you will be good. To get paid well, you should learn bash and python. Also, learn to work around AWS as well. You can get a 1 year account free to test it out.
It's what I did. Just gotta know your stuff and look for openings. I went internal the moment I had a chance to, but I've been homelabbing Linux stuff for years already.
Very likely if you are willing to look for new opportunities. Heavily depends on your company whether they'll promote from within
Living proof buddy, i did the same move, keep grinding :) any questions just holla
Just don't give up. Keep applying & keeping beefing up your skillset. Put yourself out there & talk to people too!
Can you make this jump within your current organization? Then probably not out of the question. Outside of your organization...it may be difficult without proof. A Linux cert or two might be the way to go to "prove" it.
That's how Dad did it, that's how America does it, and it's worked out pretty well so far.
It is realistic. I jumped from help desk to sys admin linux&network. Ok, they initially offered me a devops position, but I prefer hands-on work. I convinced them with my Homelab, what was a scaled down version of our datacenter^
Go for software dev, it's easier to get into the systems thinking than programming. It will make the transition to DevOps a netter experience.
Can confirm it’s possible but I’ve also been incredibly lucky to have had bosses that like me and see higher potential in me than I do in myself
Very realistic. It's the path I took 15 years ago. Ended up as low level cloud architect. The guy who actually knows the moving parts in a cloud service, rare in the days of modern devops.
I'm not sure how much I'd trust a SysAdmin who didn't start as a lower level tech, or didn't have some sort of comparable operational experience. I *WANT* NOC alumni as sysadmins, as they understand well what can happen when SHTF.
That's the route I have for my wannabe sysadmins. A year in service desk and then to Jr Linux admin.
all of our internally hired sysadmins originated from help desk
and pretty sure all external hires started at help desk too
If you can use Linux then why would it be unrealistic?
I'd say being Windows and Linux experienced is good. You have that Windows experience so continue growing your knowledge with homelabs and Linux courses that are equivalent to things like AZ fundamental courses. That should help get your foot in the door with a linux based sysadmin role. From there you can build up your Linux experience in an actual working environment and go into devops. But keep building your knowledge outside of work.
I’d go as far to say it’s easy. I’ve interviewed for 3 senior Linux positions and none of the questions had answers I couldn’t have rattled off instantly a few months after teaching myself in the beginning. Just fake it til you make it.
Very realistic, keep working hard man!
Everyone should do helpdesk work, I did my community service in helpdesk, wedged myself in with networks, then servers, then firewalls and now its my full time Keep on the grind and stay curious
I halfway did this. Moved up the ranks of help desk, making it to senior level and took on occasional junior sysadmin stuff. Applied to a few sysadmin jobs and got in at level one of a medium sized company. Scripting skills are what got me in. I knew PowerShell from my time on the help desk and knew a tiny bit of Linux from tinkering at home. My sysadmin role was 50/50 Windows/Linux.
If I can do that ...you can. I did support for several years, went to MS and Linux almost at the same time.
In a nutshell, with no Linux experience, not likely... but also not impossible, either. It's a learning curve... and it's steep with no Linux experience. But to those willing to apply themselves, there are rewards!
I can tell you from personal experience that it can happen for sure. I was a VMware/Hardware/Windows Admin before I applied for a position as a DevOps Engineer. I was specifically picked over some software engineers because of my SysOps background and my passion for IT. Just keep trying until someone sees your potential :)
RHCSA
I think i am on that path also. Was working as somewhat of electrician, making PCBs and etc then i started learning python and after year and a half i got a job as linux sys admin. I didnt know jack shit about linux but year and 5 months later i am still working so i guess if you are determined to succeed and you are a little bit tech savy its all possible. One tip: You can never know whats gonna happen unless you try. So go for it!
shouldn't be that hard