Hey everyone! I recently set up a Kubernetes environment at home using kubeadm on Multipass virtual machines. My main machine has 2 processors and 4GB of RAM, paired with two smaller nodes, each having 1 processor and 4GB of RAM. I've implemented Argo CD to automate app deployment and use Grafana for monitoring data from Node Exporter on a live dashboard. I've also ensured that my host has a fixed IP via DHCP for stable remote logins. By not using Ubuntu's desktop interface, I've freed up some memory for cluster tasks. My question is: would this kind of project be considered impressive enough to include on my resume for DevOps, Cloud, or Infrastructure roles? If so, how should I label it — as a home project or something else? I'd appreciate any insights on how recruiters view projects like this! Thanks in advance!
5 Answers
It really depends on your background. If you're a junior candidate without extensive work experience, then this setup is gold. If you have many years in the field, focus on your professional experience instead.
I’m on the younger side but have landed positions by sharing details about my homelab. Passion and self-driven learning can showcase your skills and give you an edge in interviews, especially with companies looking for Kubernetes experience.
Without a doubt, yes! I got my first IT job by discussing a simple Windows Server VM I ran at home. When I got into DevOps, I spoke about my mini Kubernetes setup during interviews, which really helped me stand out. Experience counts, even if it’s personal!
Absolutely, drop the term 'homelab' and just describe it in your own words. During my time recruiting DevOps engineers, I had a candidate who didn’t mention his homelab but talked about his experience with Kubernetes. We ended up discussing his setup for 15 minutes, and it made a big impression. He got the job and performed tremendously!
I thought you meant to avoid mentioning it completely, but it makes sense to present it as just part of your learning experience!
DevOps encompasses both development and operations, so any hands-on experience with tools like Kubernetes and APIs is valuable. You might want to mention your GitHub projects, and skill progression through cloud services instead since some companies prefer those.
That’s a great point! When I interviewed for my position, I shared my experience setting up a k3s cluster and got the job mostly because I was able to show my passion for the technology.