Earlier quoted context omitted.
> pays well, and the learning curve is a bit lower I've done development and testing, and I would characterize QA as "same job, less pay". In both roles you struggle with vague requirements, lots of edge cases, and unrealistic deadlines. It is surprisingly difficult to get out of the QA pigeonhole. People assume the job is easier, and that you're not as capable as a developer.
QA and dev are not the same job IMO/IME. Simplified: QA is “the system should do this; does it do it?” Dev is “the system should do this; make it do it.” I’m not putting one above the other as both functions are needed for most successful companies. I am saying they’re not the same job.
More seriously there is a lot of differences between the two tracks but a QA person who can write clear and repeatable reproduction steps will save a company a whole bunch of dev hours and doing so usually requires a pretty good understanding of why the system is actually breaking.