I've been experimenting with Ubuntu, Fedora, and Arch at home to broaden my IT skills. I originally used Ubuntu for Jellyfin, then moved the setup to Fedora, and I recently installed Arch on a separate partition while gradually moving away from Windows. My professional workplace is almost entirely Windows-based, with only a couple of Macs, so I haven't managed Linux systems professionally or worked with Linux deployment, hardening, or security controls. I'm not applying for Linux administrator roles, but many general IT job descriptions now list Linux familiarity as a requirement. Should I include my home Linux experience on my resume, and what practical projects or topics should I learn first so I can discuss it honestly in an interview?
4 Answers
You can also bring it up naturally when asked about interests or professional development. I would avoid presenting home use as professional Linux administration, because that can lead to interview questions beyond your experience. A phrase such as “hands-on Linux home lab experience with Ubuntu, Fedora, and Arch, including service hosting, SSH, scripting, and basic system security” is accurate if you build those skills and can discuss them comfortably.
A small, well-documented project is more valuable than installing several distributions. For example, host Jellyfin, Home Assistant, or a simple web service; manage the system remotely over SSH; create separate service accounts; configure storage and backups; apply updates; restrict network access; and write a short setup guide or automation script. You can list it as a personal lab project and explain exactly what you administered. Certifications such as the Linux Foundation entry-level certification or RHCSA may help if you eventually want Linux-focused roles, but they aren’t necessary just to show general familiarity.
It’s fine to mention Linux familiarity, but be specific and honest about the level. Running different desktop distributions by itself doesn’t demonstrate much corporate administration experience. A stronger home lab would include deploying a service, managing it from the command line, configuring SSH keys, setting up DNS, creating users and permissions, enabling a firewall, and documenting or automating the build with Bash or a configuration tool. Then you can describe the actual projects rather than simply listing “Linux.”
For a general IT position, Linux is usually a bonus rather than something they expect at administrator level. Be prepared for basic questions such as how to install packages, what sudo does, how users and permissions work, how to configure a static address, how storage is mounted, and what the firewall or security framework does. You don’t need deep enterprise experience unless the job specifically requires Linux administration, but you should be able to explain anything you put on the resume.
I’d also pay attention to the wording in each job posting. If Linux is listed as a core responsibility, basic desktop use probably won’t meet the requirement. If it’s just one item among many, a clearly labeled home-lab skill can still show initiative.
That makes sense. I’ve used Bash and SSH in the past, but not consistently for several years, so I’ll focus on building something practical and documenting what I learn.