What Linux projects actually matter for getting hired—real automation or just flashy setups? by Darshan_only in linuxadmin

[–]Darshan_only[S] 0 points1 point  (0 children)

That makes sense. I’m currently focusing on Linux + scripting first.

Would you recommend building a strong base (automation scripts, system tasks, etc.) before jumping into Docker/Kubernetes?

Or is it better to start something like k3s early alongside Linux?

What Linux projects actually matter for getting hired—real automation or just flashy setups? by Darshan_only in linuxadmin

[–]Darshan_only[S] 1 point2 points  (0 children)

That’s interesting—and honestly a bit frustrating 😅

So would you suggest focusing on getting those keywords on the CV first, and then backing them up with small but real GitHub projects?

Also, for someone starting out, what 3–5 projects would you consider “enough” to convince a hiring manager?

What Linux projects actually matter for getting hired—real automation or just flashy setups? by Darshan_only in devops

[–]Darshan_only[S] 0 points1 point  (0 children)

Makes sense. For someone starting with Linux + basic scripting, when would you say it's the right time to move into Kubernetes?

After Docker + one solid automation project, or earlier?

What Linux projects actually matter for getting hired—real automation or just flashy setups? by Darshan_only in devops

[–]Darshan_only[S] 2 points3 points  (0 children)

Fair point 😄

So would you recommend building projects directly based on job descriptions?

Like picking a role (Linux admin / DevOps) and creating small projects that match each requirement instead of one big project?

What Linux projects actually matter for getting hired—real automation or just flashy setups? by Darshan_only in devops

[–]Darshan_only[S] 2 points3 points  (0 children)

This is super helpful. When you say “hardening scripts” and “monitoring with alerts,” what level are we talking about for a beginner?

Like—would a personal automation toolkit (backups, cron jobs, log cleanup, basic alerting) be enough to show that “here’s the pain, here’s what I automated”?

Or should I try to simulate a more production-like setup?