I've always had a passion for Linux and wanted to dive directly into Infrastructure or DevOps roles. Unfortunately, every entry-level position I've encountered has been gate-kept by the requirement of 3+ years of experience. Due to financial constraints, I took on a dev role at a service-based company in 2024 and ended up stuck with a two-year bond. The company was outdated, with practices like making server changes via FTP and lacking version control, which made me feel pretty defeated. Instead of giving up, I decided to improve the team's workflow and gain some hands-on experience.
I successfully transitioned the team to using Git, teaching even the lead about pull requests and branching. Eventually, I was assigned a significant project involving automated pipelines for a Hetzner VPS, using Laravel/PHP for backend and React for frontend, alongside crons and long-running processes. I utilized GitHub Actions, Docker, and custom Bash scripts for deployments and rollbacks across branches. It felt great to see everything working well, but I received zero acknowledgment from management. They simply see that things are functioning now.
I'm really fed up with this job, and as my bond is about to expire, I'm left confused about my next steps. I have a solid understanding of Go and I prefer infrastructure work over traditional CRUD development. Now I'm torn between two paths:
1. Should I continue in development and deepen my skills in languages like Go?
2. Or should I focus on Kubernetes and aim for a proper Infrastructure role?
With the current job market and the impact of AI making everything feel crowded, I'm looking for guidance on my dilemma. Thanks!
4 Answers
It sounds like you've already done a lot of the groundwork that would be valuable in DevOps! Your initiative to transition your team to Git and build pipelines demonstrates a readiness for a DevOps role. Just remember, the environment you'll join next can hugely influence your experience, so keep your job search broad. Look for companies with positive cultures rather than just focusing on the specific title. Smaller organizations might be more flexible and appreciate your diverse skill set, which sounds pretty solid already! Good luck out there!
I feel for you, mate. It sounds like you're super capable and have already made significant impacts at your current role. Given your journey, I'd recommend targeting positions that blend Dev and Infra skills, especially in companies that are building internal tools or platforms. And yes, keep working on your Go skills while you learn Kubernetes—it's a powerful combination for the kind of work that you'll enjoy. You'll land something that fits you just right!
Honestly, you might already be doing the work of a DevOps engineer without the title! Since you have Linux and scripting down, I'd suggest diving deeper into Kubernetes. Many jobs expect some level of understanding of container orchestration like K8s, and with your existing experience, you are well-prepared to tackle that. Transitioning into the Infra role could suit you perfectly, especially since you enjoy it more than dev work. Trust that your experiences will guide you in the right direction!
Don't worry too much about the "gatekeeping" in the DevOps realm. From what you've described, it seems like you already possess the required experience. If you enjoy automation and infrastructure, I'd recommend focusing on Kubernetes first. Get comfortable with it and then look for positions branded around DevOps or Platform Engineering. Highlight your past achievements in your resume to show potential employers what you can bring to the table!
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically