Sorry to hear about it...just as an idea since you mentioned that you're an introvert, I'd look at heavily weighting aspects of introversion: 1. Tight boundari

Sorry to hear about it...just as an idea since you mentioned that you're an introvert, I'd look at heavily weighting aspects of introversion: 1. Tight boundaries around relational and physical circumstances taking up your time and space: Environments without so many meetings, but probably also low-dopamine work environments in general, i.e. build your ideal space starting from the typical closet-with-locking-door configuration 2. "My ideas, my goals, my ways of doing things." Environments where you are the sole keeper of the job's tech domain knowledge. Total permission to go not-invented-here. For example, say there's an IT team but you are the only software engineer and there's a solid boundary there. 3. Time not of the essence: Introversion is at its best when time is not an overriding concern. It could still be a very important job, but the work product value is measured in qualitative improvements that create and maintain a sustainable business environment over time, for example. I've seen these conditions matched in a lot of different domains, but tech within tech is a difficult match. The most common one that comes to mind would be academia, for example there was a popular bay area performing arts department within an academic institution, which had a very complex and rare web application stack and a tech person looking to retire. Good luck, I hope this can be somewhat helpful.