There's a really important issue with QA which is that you can't just farm it off to a team that doesn't know how to use the product. In my last job, which was

There's a really important issue with QA which is that you can't just farm it off to a team that doesn't know how to use the product. In my last job, which was working on Engineering software, they had a few student interns and a couple of permanent staff that had no training as engineers. So when bugs came in from customers, they had no ability to try and work out what the issue was, it was really dysfunctional - they weren't able to say "this is because the custoemr doesn't understand the physics" for e.g. They eventually moved an application engineer from pre-sales into the team and it made a huge difference in triaging this stuff, because many 'bugs' that came in were things like "my model isn't converging" and the answer was 75% of the time things like "you need to refine your mesh further", whereas previously it got shunted onto the dev team.