Jade Rubick tackles the age‑old debate: should engineering teams keep a separate QA function? Many leaders dismiss QA as an outdated gatekeeper, arguing that engineering should own quality. Critics point to slow cycles, moral hazards, and poor incentives that arise when a third party checks work.

Proponents counter that testing is a distinct skill set. QA specialists uncover deeper issues, and automated tests embedded in pipelines deliver high leverage. In high‑stakes projects, a seasoned QA can prevent costly failures. The rise of AI‑driven verification tools promises to amplify this value today.

Rubick recommends avoiding a handoff. Instead, embed QA on the same sprint cadence, letting them shift left and review pull requests. Engineers should still own unit and integration tests, while QA focuses on end‑to‑end UI checks. A solid testing pyramid keeps fast unit tests at the base and limits slower UI runs.

Ultimately, QA should exist, but only when it adds measurable value. By integrating QA early, automating tests, and treating them as quality experts rather than gatekeepers, teams can maintain velocity while reducing defects. The key takeaway: quality ownership remains with engineers, while QA elevates the overall testing discipline.