A bounce from QA is treated as evidence about the developer. It is almost always evidence about the ticket. The developer built something. The something did not match what QA was checking. The something not matching is a writing failure that happened days earlier.
This reframes quality work in a way most teams resist: the bounce rate of a PM's tickets is a measure of the PM, not of the developers building them. A team with a high bounce rate does not have a building problem. It has an acceptance-criteria problem.
Once you see it that way, the fix is obvious and cheap. Improve the ticket. Send the AC before the work starts. Watch the bounce rate fall. The developers were never the variable.