A typical conversation with a new recruiter...

NB: "Why won't you do a coding test?"
Me: "Do you believe I can't code after 30 years of coding?"

NB: "Well, no but they want to see how you code."   
Me: "Then there's several projects in my github."

That's when stuttering and stammering begin.   

NB: "Well, uh, maybe you didn't write that code".
Me: "If my resume and code are fake, why are we even talking?"

Why do I want to deal with this level of paranoia right from the start?

The coding exercise is a variation of the trick question, like the brainteasers that Google promoted for years.  They have no predictive value about writing software.   It's an alpha geek domination / gatekeeper technique.  The gatekeepers refined a contrived problem over several days and I'm supposed to solve it in an hour.  But usually I don't see their contrived issue or it's wrapped in twisted nutball phrasing to hide the contrive, so I get the condescending reply,

"Wellllll, you did okaaaaayyyy but you missed some stuff".

Why do I want to screw around with pretentious paranoia? I don't.

I'm happy to let them play their gatekeeper game and discard me, it saves me time and annoyance.

Likewise, I don't do group interviews anymore.  There's always one or two people who resent my resume or fear I'll take their position or paranoid that I'm not online or I didn't smile enough.    The job revolves around their mental issues instead of delivering a product.  I'm not a baby sitter.  So I spend 5 or 6 or 7 hours on being annoyed.  

I manage my annoyance because they can't figure out that they aren't hiring for software development.   They're hiring for ego gratification or socialization or virtual signaling  or  joining their church or whatever and I'm not interested in deciphering whatever it is.  In earlier times most jobs were still about delivering a product instead socializing, paranoia and conformity.