I spent time working in a QA team, and I still struggle with the term “Quality Assurance.”
It implies a level of certainty that simply does not exist in real-world systems. No team can truly assure quality.
What that function actually does is far more valuable: designing processes, building tooling, exposing risk, and improving systems continuously. That is engineering work.
Many organizations have already recognized this and moved toward “Quality Engineering.” It is a more accurate name and a better model.
It acknowledges that quality is not something guaranteed at the end, but something built into the product from the start, with the authority to enforce standards and stop releases when needed.
Quality is engineered, not assured.