It's a tough call to make because I'm opinionated enough about how testing should be done that I also don't want to end up working as a software engineer in a company that treats QA like drones either.
It's a tough call to make because I'm opinionated enough about how testing should be done that I also don't want to end up working as a software engineer in a company that treats QA like drones either.
Developers’ jobs, on average, are more difficult and more valuable. It’s easier to take a median developer and turn them into a good tester than it is to take a median tester and turn them into a good developer. Similarly, if we consider a bright college graduate, it would take them less time to become competitive as a tester than as a developer. Secondly, the difference in business impact of a “good enough” tester versus a “world class” tester is negligible (rarely more than 1-5 FTE), while the difference between a “good enough” developer and a “world class” developer is uncapped. The economic treatment of these two groups, and therefore their relative power in the workplace, merely reflects the expected replaceability and value of these professionals.
So I've begun to recently think about how I could "brand" my skillset regardless of my ACTUAL title. Since employers almost never give a shit what your exact title was.
Happy to hear counterpoints, but my experience is that you could definitely re-frame your experience with different / compound titles in order to get better looks from other companies.