Exactly. One negative productivity technical tornado can cause more damage than 10 people who lied about their coding ability.

What engineering interviewing process catches things like this?

Most coding interviews are accompanied by work experience discussions which CAN identify stuff like this, although obviously people can BS.

Work experience discussions are the best I’ve come up with.

What I’m suggesting is hire experienced people based on that and resume verification and behavior interviews like nearly every other job on the planet.

And if someone lies about their ability to actually code, fire them quickly.