I just want to say, I've noticed the same issue with myself lately. My personal solution has been to go get a PhD in applied math but that's me. I'll still prob

I just want to say, I've noticed the same issue with myself lately. My personal solution has been to go get a PhD in applied math but that's me. I'll still probably have the same problem after a I get a PhD but I'll burn that bridge when I get there. If I were staying in software, then I think my strategy would be to identify what 'boxes' there are and try to fit my experience into those 'boxes' for the different jobs I apply to. It gets really grueling having to make multiple resumes, and some of them can get a little thin, but maybe take this as a first approach. As an example of 'boxes' I mean - Web developer - Embedded firmware developer - Devops engineer - Data scientist/data engineer You know your experience best so modify as appropriate, but also maybe try to lean into the box where you "fit" the best. I know it might be a little depressing to try to reduce yourself to "web developer" box, but I see the goal as trying to stick to a career path/industry with the goal of building a network and building off opportunities. Not sure if that makes sense, good luck.