I've seen software testing work at scale when there's a company-wide mindset to quality, as opposed to 'quality is the job of one person/department':
- Shift left testing: quality can be implemented at all stages of the development process, from requirements gathering to deployment. Issues are easier and cheaper to fix the earlier they are discovered, and it does not necessarily take a software tester to discover these, although testers can advocate for a mindset of quality
- Quality as a shared mindset/goal, not just one team's job: every team member seeks to quality control their bit of work, this inevitably involves developers doing a basic level of sanity testing on their code. When done right this should reduce the long feedback loop to discovering issues when a team completes a piece of work, hands it over to QA, then context switches over to another piece of work.
- Shift left testing: quality can be implemented at all stages of the development process, from requirements gathering to deployment. Issues are easier and cheaper to fix the earlier they are discovered, and it does not necessarily take a software tester to discover these, although testers can advocate for a mindset of quality - Quality as a shared mindset/goal, not just one team's job: every team member seeks to quality control their bit of work, this inevitably involves developers doing a basic level of sanity testing on their code. When done right this should reduce the long feedback loop to discovering issues when a team completes a piece of work, hands it over to QA, then context switches over to another piece of work.