I'm a computer engineering graduate and previously worked as a support engineer, where I used the Linux command line for more than two years. I also have a career gap and want to become employable as quickly as possible.
I'm interested in junior roles involving Linux servers, CI/CD, containers, Kubernetes, and related infrastructure. I'm not specifically targeting a formal DevOps title, since responsibilities vary widely between companies.
My goal is to make measurable progress every week and begin applying for jobs as soon as possible. I can study about 15 hours per week during the first month, then increase that to roughly 30 hours per week during months two and three.
What skills and projects should I prioritize, and how would you structure a realistic three-month preparation plan?
4 Answers
A good hands-on project is to write a tiny web service that returns a success message, containerize it, and run it locally. Then create a multistage Docker build and a CI workflow that builds the image and publishes it. After that, deploy the image to a local k3d, k3s, or MicroK8s cluster using a Deployment, Service, and Ingress or Gateway route. Add mounted configuration, then manage the Kubernetes manifests with Kustomize or Helm. Work through each layer carefully and use AI as a tutor to explain unfamiliar concepts rather than copying solutions.
You already have a useful foundation, so focus on practical administration rather than memorizing more commands. In the first month, strengthen Linux fundamentals such as users, permissions, networking, services, logs, SSH, and Bash scripting. Use the second month for Git, Docker, Nginx, and basic CI/CD, then cover Kubernetes fundamentals, monitoring, and troubleshooting in the third month. Build something every week—a secured web server, a containerized application, a simple pipeline, or a small home lab. These projects give you concrete examples to discuss in interviews, and you should start applying before you feel completely ready.
Prioritize automation and problem-solving. Whenever you encounter a repetitive task in your lab, write a Bash script or use a tool such as Ansible to improve it. This helps you understand systems more deeply and gives you useful interview stories: what was inefficient, what you changed, and how you verified the result. Make your work accessible in a public project or clear portfolio, and apply for roles while continuing to improve instead of waiting for perfect readiness.
Three months probably won’t make you an expert, but it is enough time to create a credible foundation and start looking for work. Don’t try to master every DevOps tool. Learn how Linux systems behave under normal and faulty conditions, practice troubleshooting, and build a small lab where you can intentionally break and repair services. A project that combines Linux, Docker, CI/CD, and basic Kubernetes will be more valuable than completing a long list of disconnected tutorials.
Would a project like that be enough to demonstrate junior-level ability, or should I build several smaller projects as well?