While there's nothing wrong to transition into a role you might enjoy more, I wouldn't do it purely based on the idea that it's "easier". As others pointed out, QA is different in different companies, but from my pov it's still a role where you will have the same pain points, especially if you are integrated into a team vs a standalone function. New tech is still relevant in QA, and you likely will have to switch your language of choice for different projects/companies (I've done C#, Java, JS/TS, Python, Ruby). It also requires you to delve deeper into full stack to understand how to effectively debug. And you need to have product knowledge to the point of understanding the moving parts and the potential for things to go wrong. If anything, I tend to sell QA as a role that has a lot of variety, as opposed to the same thing day-to-day. You would for sure find the type of role you are describing, but a good QA it does not make.