Look for jobs that are outside your comfort zone. Leverage your existing experience to convince a new company you can do X even though you've never done X, but

Look for jobs that are outside your comfort zone. Leverage your existing experience to convince a new company you can do X even though you've never done X, but based on your history of doing Y which is related but not the same. You didn't know Y when you started it either, but you got Y done and know the impact on the business. Look for Systems Engineering(not a title used much anymore TBH), DevOps, Site Reliability Engineering, Platform Engineer, Developer Experience engineer(or whatever). A lot of these roles will be very cross discipline and non-functional. Always be on the lookout for cog-in-machine roles; DevOps can be "The buck stops at you for our companies site reliability" or "you write Chef cookbooks and test kitchen scripts all day". Don't let anyone tell you your skill set doesn't exist. Let's face it, most college grads do the bare minimum of learning for their degree. Most people don't to TOO much more than what they need to keep their career viable. Being a "generalist" is like taking 20 electives you don't need to graduate; it's inconceivable to many people. Mediocre engineers and specialists will rail against the idea to protect their ego. Generalists will rail against specialist value to protect their ego. Don't get too caught up in the BS. Be prepared to be pigeon-holed. Nearly every person you meet at your new employer will see your last job "title" and generalize you. Typically the only exceptions will be the recruiter and maybe, incredibly maybe, the hiring manager. GL/HF