I’m trying to get a job in IT that will (hopefully) pay more than a usual 9 to 5. I’m been daily driving Linux exclusively for about 2 1/2 years now and I’m trying to improve my skills to the point that I could be considered a so-called “power user.” My question is this: will this increase my hiring chances significantly or marginally?
Learning Linux was probably the very best thing for my career.
The fact that I use Linux as my primary OS has been a positive in almost every interview I’ve been in as the interviewee. Linux has been used everywhere I’ve been, and that represents a huge amount of upskilling they can skip.
As an interviewer, I’d say that developers who use Linux generally understand their development stack better.
deleted by creator
- don’t call yourself “power user”
It might just be me but it gives off “I can set up a printer, yay!” vibes.
To give yourself a better chance, learn things like:
- Bash scripting
- Docker
- Docker Compose
- Kubernetes
- Oauth2 and and an authorization server like Keycloak
- Build and deployment tools like Jenkins
Also learn how to deploy database and web servers manually.
It sounds like a lot but they’re things you’ll be expected to use.
Deploy database? You mean something like SQL?
Yeah, or a nosql database. The point is to know how to deploy and manage servers manually as well as using the tools to do it.
Yep. You should absolutely know how all the pieces connect.
One IT responsibility is setting up servers. You should at least know how to get a website running off of a Linux machine at a basic level. But what we judge you on is your ability to manage and secure it.
No, dont learn docker, learn containerization and what tools can be used for it. No to Kubernetes that comes much later and/is VERY specific. No clue what keycloak is, but it sounds useful. Never hear about Jenkins. Id rather say get a grasp on python and skim what tools are used to administer servers -> ansible and puppet maybe.
I almost want to agree with parts of this but I cannot imagine the downvotes for supporting a comment that includes “never hear about Jenkins” and “don’t learn Docker”.
Jenkins has about 50% market share for anybody keeping score at home. In many verticals, the market leader has about 35% market share so 50% gives Jenkins enough domination in the market that saying “never hear about” them is going to hurt your credibility.
I think most organizations using Kubernetes should not. However, most of those would still benefit from containerization and so knowing Docker is a good thing even if you use a different tech ( Podman is the same thing ). While I think people should not be using Kubernetes as much as they do, it is still going to help you to know it when you are asking those people to hire you.
Knowing Python is fantastic advice for DevOps and IT in general.
Ansible and Puppet are solid recommendations. I think Ansible is the market leader ( probably about a third ).
Keycloak is great but it had less than 5% market share and so not knowing it is not going to hurt.
From wikipedia and their github it sounds like jenkins is mostly used for development/programming. So maybe thats why I never heard about it shrug.
Well you just got dismissed early in the interview
Yes if
- the environment you would work on is Linux based, obviously (which it often is when servers are involved, even with Microsoft due to Azure cloud and containers)
- you master the command line, i.e you know a bit of e.g bash, can write your own scripts that do basic functions
- you understand how the OS works, i.e permissions, services, package managers, etc
but not really if you are mostly clicking through buttons of the window manager and/or would work in a Microsoft environment with its own set of tools, conventions, etc.
Which brings up obvious suggestions :
- do improve your mastery of the command line
- apply to jobs that put Linux forward (but that might bias to a sysadmin position, which might not be what you prefer)
I had a job offered based on the fact that if you know bash, you can translate that to powershell, as translating knowledge is easier than learning from scratch.
True. Learning your first programming language (or scripting language) is usually the hardest.
Makes sense to me. I would also assume that if one can program in bash they can program in pretty much anything. Yes it will take some time to adapt but a lot less than somebody who can’t program in any language in any environment.
That being said, I would advise against starting in an environment that is possibly alienating and exclusive. Microsoft does everything it can in order to lock-in users but also developers. They find bridge, like PowerShell or WSL, then IT relies on certifications specific to their ecosystem. So if OP is fine with such practices they could start there but I’d suggest to keep that only if more direct alternatives are not available.
Depends on the job, a lot of places don’t use Linux
However Linux jobs tend to pay more than the non-Linux equivalent if you can find one
Most places deploy to Linux, and for those knowing Linux helps a lot. Also a lot of places will give MacBook pro, expect you to know the CLI so a lot of Linux knowledge will be useful there.
If your goal is to make yourself more valuable to employers/clients the best path is to specialize in some critical and niche enterprise tech. People that are good at stuff businesses were lured into using get paid very well. In my case it was SharePoint, but that’s just an example.
Knowing your way around the OS is taken for granted in these positions, so you have one piece of the puzzle, which is great, but you need the other pieces.
But be careful, if I have to choose between two experts, one with basic win+linux and the other only linux, I’m choosing the former.
Very bad advice, getting your niche might pay off for a certain job in a certain time period and makes you clueless and worthless in any other job other timeframe.
Rather focus on general overview and tools instead. I can imagine how you brain is melting away dealing your whole work day with only sharepoint, rofl.
Well, it was addressing the pay issue, and it is the most secure path to higher paid position fast. Moving on to new stuff comes naturally and the industry will push you to their next hotness, so not really a problem.
No, it won’t. Corporations in today’s time have this entitlement that you should know everything beforehand. You need a lot more than that. Oh, you don’t know Ansible? Don’t understand Terraform? Can’t fix a Docker config? Haven’t used AWS? Rejected, next?
It highly depends on the job. Some companies run fully on Windows, no exceptions. There it obviously would not help. But many still either host various services on Linux, or buy hosting/cloud commuting that is Linux based. There it might even be necessary.
It also depends on what you mean by “power user”. I would generally advise you to look into the server side of things. In my work, there are zero Linux machines that have a GUI of any kind installed. t The 50 or so Linux machines are all administered through SSH and Shell.
This! Also if you company only employs windows machines … run.
Or just start introducing Linux containers and VMs that run on Linux. You can use Docker Desktop and Putty from Windows.
the point that I could be considered a so-called “power user.”
There is no certain point. Power user is a rather vague description. It still includes “user” as opposed to admin or developer or guru etc.
If vague is good enough in your area, go for it. Otherwise look for a more formal qualification.
Good luck.
My personal experience: Absolutely!
I’ve always landed on jobs/projects that involve Linux server. Generally startups with not much expense to spare would go for this route. However, even bigger companies would opt for enterprise Linux.
I wouldn’t say that will work on every IT jobs out there, but when it does, you know you’re in for a fun ride!
I interview developers and information security people all the time. I always ask lots of questions about Linux. As far as I’m concerned:
- If you’re claiming to be an infosec professional and don’t know Linux you’re a fraud.
- If you’re a developer and you don’t know how to deploy to Linux servers you’re useless.
So yeah: Get good with Linux. Especially permissions! Holy shit the amount of people I interview that don’t know basic Linux permissions (or even about file permissions in general) is unreal.
Like, dude: Have you just been
chmod 777everything all this time? WTF! Immediate red flag this guy cannot be trusted with anything.If you’re a developer and you don’t know how to deploy to Linux servers you’re useless.
Welp, found your red flag
Can I ask if the reverse applies, eg is having no idea how to use non Unix like OSes (like Windows) any kind of red flag? Kinda been considering trying to go into a tech career so that I can have a 9-5 office job (I’ve until recently worked in what would be considered “blue collar” jobs, recently switched to an education job, would be nice to just sit down in an office and use computers for a living). I’ve used (GNU/)Linux from a very young age (parents had an Ubuntu laptop), as my primary OS/daily driver since I was 13, and exclusively (i.e. got rid of my Windows partition due to Windows enshittification) since I was idk maybe 16 ish? So I’m pretty comfortable doing things in Linux. But I have a reputation for being a tech person among my friends and they ask me to fix their stuff sometimes and whenever it’s a Windows problem I literally have no idea how to use the OS lol. So are Windows skills and knowledge also expected for tech jobs or just Linux/Unix-like?
There’s not much to learn in Windows land! Learn how to set file permissions, how the registry works (and some important settings that use it), and how Active Directory works (it’s LDAP) and you’ll be fine.
If you’re used to using Linux nothing will frustrate you more than being forced to use a Windows desktop. The stuff you use every day just isn’t there. You can add on lots of 3rd party tools to make it better but it’ll never measure up.
When you have to go out on the Internet to download endless amounts of 3rd party tools the security alarms in your head might start going off. Windows users have just learned over time to ignore them 🤣
If you’re used to using Linux nothing will frustrate you more than being forced to use a Windows desktop. The stuff you use every day just isn’t there.
Absolutely. I tried using Windows for gaming some years back when Wine wasn’t as good and it was such a struggle. I was used to thinking there’s more software for Windows since it’s more widely used, but I was shocked at both how much software I used was Linux (or POSIX-compliant) only, some of which had no Windows alternative. I remember struggling so much to just try and get some files off a LUKS-encrypted drive on Windows and was shocked that there was basically no option at the time. I also hate how Windows users just download random exes off the web for all their programs. I only ever used chocolatey to install anything for that brief Windows stint.
Depends on the tech job. A lot of corporate IT support jobs care a lot more about troubleshooting windows because that’s what the employees use
- What are basic Linux permissions?
- What does
chmod 777do?
“chmod 777 is opening your front door with a sledgehammer”
Quick and dirty: the basic permissions are read, write, and execute, and are applied to the owner, the group, and everyone else. They’re applied to all files and directories individually.
It’s represented by a 3 digit number (in octal, which is base 8, so 0 to 7). The first number is the permission given to the file’s owner, the second to the file’s group owner, and the third to everyone else. So, the owner of the file is the one user account that owns it, the group applies to all members of that group. User and group ownership are also applied to each file and directory individually.
Read, write, and execute are represented by the numbers 4, 2, and 1, respectively, and you add them together to get the permission, so 0 would be nothing, 1 would be execute but not read or write, 2 would be write but not read or execute (and yes there are uses for that), 3 would be write and execute but not read, 4 is read only, etc through to 7 which is basically full control.
This will take a little bit to make sense for most people.
chmod (change modifier, I think) is the program you use to set permissions, which you can do explicitly by the number (there are other modes but learn the numbers first), so chmod 777 basically means everyone has full control of the file or directory. Which is bad to do with everything for what I hope are obvious reasons.
chown (change owner) is the program you use to set the owner (and optionally the group) of a file or directory, and chgrp (change group) changes the group only.
It gets deeper with things like setuid bits and sticky bits, and when you get to SELinux it really gets granular and complex, but if you understand the octal 3 digit permissions, you’ll have the basics that will be enough for quite a lot of use cases.
(Additionally to the 3 digit number, permissions can be represented a bit friendlier where it just lists letters and dashes, so 750 (full control user, read and execute group) could be shown as rwxr-x—, where r=read, w=write, and x=execute, and what they’re applied to can be represented by the letters u for user (aka owner), g for group, and o for other)
This goes into more detail of those basics: https://opensource.com/article/19/6/understanding-linux-permissions
Thanks. Bookmarking for future reference.
Also, they didn’t mention it but you can always just do this (the easy way, thanks to GNU):
chmod a+x somefileto give it execute bits. It works intuitively like that forwandrpermissions too.It’s just quicker to type out
chmod 775than it is to do it the other way 🤷Juwt remember “man chmod”.
Read, write, and execute are represented by the numbers 4, 2, and 1, respectively, and you add them together to get the permission
Maybe I’m the weird one here but this seems like a counter intuitive way to remeber/explain it. Each octal digit in the three digit number is actually just 3 binary digits ( 3 bit flags) in order of rwx. For example read and execute would be 101 -> 5.
While that’s literally what it is, that’s not really how it’s represented and requires also understanding binary numbers.
Even knowing that, I’ve always found it easiest to get to the permissions the way I described, which when you think about it is actually the same as what you’d do to translate binary into decimal/octal if you don’t have them memorized: look at the values of each position that’s set to 1 and add them together. So, 101 in binary would be 4+0+1, or 5, which is the same as saying read is 4 and execute is 1 and add them together, the latter of which I think is easier to learn (and is how I’ve always seen it taught, though clearly YMMV)
Both get you to the same place though
That’s a fair point, I guess I used binary numbers so much i uni that I just know the small ones by heart and that’s why I find it easier. Following the example, I never convert 101 as 4+0+1, I just see it and know it’s 5.
Have you just been
chmod 777everything all this time?Oh man, I ran into a dev at a meetup who proposed this solution.
And I had to do a polite, “Oh wow maybe that works but I don’t think that’s a solution in my company” because YIKES.
sudo chmod 000 /Lol been there, and with the
-RtooSorry for your loss. I hit myself with the ‘rm -rf /*‘ several years back when I was actually trying to do ‘rm -rf ./*‘.
Now I do ‘ls’ instead of ‘rm’ just to make sure that what I’m deleting is what I’m intending to.
Figured I was very lucky that it was just on my own workstation and not on any of the servers I was tasked with maintaining. I lost a day or so of work. Had it been our dev server? Would’ve destroyed my team for a while.
Power User is a term invented by Microsoft but we get the idea
were takin it back
I did not know this. Thank you for the history lesson.
yes
Exactly this. Having an interest and a hobby to an open source system will make you better in your job and a much more interesting candidate to hire.
Source: started with linux in 1995 as a kid. Never having issues finding great jobs.
Edit: I did not mean being a devops here, but finding an interest in open source software and learning a highly lucrative programming language while going. You can get pretty far with Rust or Go in the modern startups, C or Java in enterprises. Being very good with Linux drives this interest.
Honestly, it depends on the business.
If I were the hiring manager we are a 80/20 split on win vs Linux servers. You may be top tier on 20% of our systems but we have automated about 85% of the tasks on those boxes. The other 15% is being covered by the windows people.
How do I justify hiring you to do 15% of the work of the others?In order to be paid above average, you need to be good at something others find hard. But don’t pigeon hole yourself to one thing.
Being good at windows and Linux will make you a more attractive hire. As a Linux daily driver you should have no excuse to not know virtualisation or containers. Run up some qemu VMS or some LXC containers to expand your skillset.
I make it a condition of my employment that I never touch windows servers, and I get paid very, very well.
Linux experience is far more important than windows experience, IMHO. Almost every company has Linux servers. Loads of companies don’t have windows servers.
Even a simple “I know how to setup a network-wide ad blocker on docker by using my own image” can get you far, so yep.
Thats oddly specific. I think “I have experience with Linux” would be better
This is a IT-related question – of course being “oddly specific” is a great idea. Even if the job in question does not use anything docker related.
The word “Linux” doesn’t even appear in that though
On a resume you might format this like “Skilled in setting up networked Docker images”. Absolutely a valued skill and worth mentioning.
You didn’t even mention the word linux
