They key is that you can’t just stop doing what you hate but you have to be able to lean into what gives you some satisfaction.
Example: I made a trade from a key role to a dev role in one job change. In dev role I was working with a technology I had significant experience with in my prior "key" role. In the new role, when the topic came up, I suggested we avoid certain vendors since in my prior role I was responsible for the technology vetting and I determined the chosen vendor was not forthcoming with some important limitations. My feedback (constructively and succintly presented) was completely ignored since I was "just a developer" and I ended up having to make the sub-par technology actually work.
It was frustrating and painful, not because of ego, but going into the task knowing it would suck since the wrong decision was made and now I was the guy having to make broken pieces meet some demanding requirements because "a developer" couldn't possibly know more than an "architect".
I don't know about other developers & engineers but I've already learned quite a few lessons the hard way and don't need to burn my evenings and weekends knowingly doing something the wrong way.
You might say "That's OK, that's what they're paying you for" but if you've been in this situation, usually someone less knowledgable, bordering on clueless will draft a schedule and you'll be the guy to make it happen. So a bad technical decision turns into a pressure cooker which then turns into more stress. Which is similar to another poster who said (I'm paraphrasing) "each job will suck in different ways".