I have about two years of DevOps experience and left my previous job a few months ago because there was very little meaningful work. I stopped learning and felt stuck, so I assumed finding a more challenging role would be fairly manageable. Three months later, I've applied to roughly 100 positions and received very few responses—mostly automated rejections or complete silence. The current focus on AI, agents, and automation also makes me worry that the industry is moving faster than I can keep up with. I've been building projects, studying new tools, and trying to improve my skills, but it's difficult to feel confident without recent production experience. I also don't have much of a professional network or anyone experienced to guide me. For people who have been through a similar search, how long did it take to find your next role? What helped you stay motivated, and is there anything I should change about my applications, skill development, or job-search strategy?
4 Answers
The lack of replies does not necessarily mean you’re incapable; the market is genuinely crowded, especially for less-senior infrastructure roles. Set a sustainable daily routine rather than judging yourself by application counts: submit targeted applications, spend focused time on hands-on practice, and reserve time for exercise and people outside the search. AI is another tool, not a replacement for understanding systems. Three months can feel enormous when you’re unemployed, but longer searches are common right now, and continuing to build evidence of useful problem-solving will improve your odds.
Two years of experience is a difficult point in the market because junior DevOps openings are limited and attract a lot of applicants. Focus on demonstrating practical ability rather than collecting more tools. Polish one or two projects as if they were production systems: include infrastructure as code, CI/CD, monitoring, documentation, diagrams, security considerations, and an explanation of the tradeoffs. Strong fundamentals—Linux, networking, scripting, cloud services, containers, debugging, and communication—still matter more than chasing every AI headline.
Applications alone can be a slow numbers game. Reconnect with former coworkers, attend technical events, join professional groups, and talk with people who work in infrastructure or cloud roles. Referrals and conversations often produce better results than anonymous applications. Keep your résumé, professional profile, and portfolio current, and prioritize recently posted jobs. If your former employer was generally a good place to work, it may also be worth asking whether they would consider bringing you back; there’s no shame in doing that while continuing your search.
The biggest lesson is to avoid leaving before you have another offer unless you truly have no choice. A quiet job can still provide income and time to learn, build experience, and search while employed. At this point, keep applying, but broaden the titles beyond DevOps: SRE, cloud operations, automation, platform support, systems administration, and infrastructure engineering may all be relevant. Make each application fit the job description instead of sending the same résumé everywhere.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures