Hire QA
QA for the release, not a leftover pass.
A test plan, API checks, and automation on the tools they claim, before you call a build done.
What this developer does for you
They protect a change your team is about to ship. The seat is an add-on beside an engineer seat, or a QA seat on its own. The seat is quoted with the role.
What to test
A written plan for the change: the path that matters, and the path that usually breaks.
API checks
Requests against the API the change touches, including the error the client will see.
Automation they can defend
Automation on the tools they claim. The exercise is how they test, not a feature demo.
A result the team can read
What ran, what failed, and what they did not cover. English is part of the standard.
What does the QA exercise look like?
A timed practical task on how they test the stack they claim, then a live interview and a paid task. It is not a certificate and it is not a feature-coding test with the name swapped.