When to hire QA vs fix architecture first
More testers on a brittle system scale pain linearly. Better architecture scales confidence.
Signs you need architecture work first
Releases require heroics. Flaky tests are ignored. Environments do not match production. Defects cluster in the same modules every sprint. Hiring another manual QA will not flatten that curve.
Signs headcount helps
You have stable CI, clear ownership, and exploratory gaps in new domains (mobile, payments, AI). Additional QA engineers extend coverage you already know how to measure.
The 90-day sequence I recommend
Month 1: map critical journeys and stop the bleeding on release gates. Month 2: automate the top ten paths and fix environment parity. Month 3: hire or expand team into a system that can absorb them.
Consulting vs FTE
Short architecture engagements—like my QA architecture practice—often unblock hiring. You get patterns and tooling; your team executes without guessing.