I've been getting more comfortable experimenting with Linux distributions such as Ubuntu, Fedora, and Arch. My professional environment is almost entirely Windows, with only a couple of Macs and no Linux systems, so I haven't used Linux for corporate deployment, security management, or administration. I started building this experience at home to broaden my IT knowledge and eventually move away from Windows as my primary desktop.
I've run Jellyfin on Ubuntu, migrated that setup to Fedora, and recently installed Arch on its own partition. I'm not applying for Linux administrator roles, but I'd like to show potential employers that I'm familiar with Linux when it's relevant. Should I include this on my resume, or would it be better to leave it out until I have more substantial experience? Are there particular projects or home-lab skills I should learn first, and what kinds of basic Linux questions might come up in an interview?
5 Answers
Whether it belongs on the resume depends on the job description. If the role specifically requires Linux, employers may expect professional experience with servers, security, automation, or production systems—not just installing a desktop distribution. For general IT roles, you could list something modest such as “Linux—home lab experience” and include the specific projects or tools you’ve actually used. Don’t label yourself a Linux administrator unless your experience supports that claim.
Only include Linux if you’re comfortable being questioned about it. Saying “familiar with Linux” invites follow-up questions, so be specific about the distributions, services, and tasks you’ve handled. A certification or structured practical course can help if you want to move toward Linux administration, but it isn’t necessary just to show that you’re expanding your skills.
A home lab can be worth mentioning when it has a clear, practical result. Running a service such as Jellyfin, Home Assistant, or a small web application can give you opportunities to practice storage, users, permissions, networking, updates, backups, SSH, and troubleshooting. You can also bring it up when asked what you do outside work, even if you don’t create a separate resume section for it.
Desktop use alone usually doesn’t demonstrate much to an employer. A better home project would be running a web or application stack, hosting something useful, and documenting how you deployed it. Practice SSH keys, DNS, package management, permissions, and perhaps write a small script or configuration playbook to automate the setup. That gives you concrete experience you can discuss instead of simply saying you installed Linux.
For a non-Linux role, Linux is generally a nice bonus rather than a core qualification. If you list it, be prepared for basic questions about repositories and packages, network configuration, sudo, disk and user management, host firewalls, SELinux or an equivalent security system, and simple Bash scripting. You don’t need to claim administrator-level expertise, but your resume should accurately reflect what you can explain and demonstrate.
That makes sense. I’m mainly trying to build useful general IT knowledge, not present myself as a Linux administrator. I’ll focus on the command line, networking, security, and a practical project before making it a prominent skill.