That's not how economics works.
If consumers have to pay less, that's a Good Thing.
The Chinese are trying to help, but Americans like tariffs more than they hate climate change. (At least that's the preference that their political system expresses.)
I've found that talking through projects is a weak indicator of competence. It's much easier to memorize talking points than to produce working code.
-> GPA can be gamed, as laid out.
-> Take Home assessments can mostly be gamed, I want to assess how you think, now which tools you use.
-> Personality tests favor the outgoing/extroverts
-> On-location tests/leet code are a crapshoot.
What should be best practice here? Ideally something that controls for first-time interviewer jitters.
If, hypothetically, there's two candidates, one who is more knowledgeable but has no personal projects versus someone who has less knowledge but has worked on different side projects in various languages/domains, I'm always going to pick the latter candidate since they clearly have a passion, and that passion will drive them to pick up the knowledge more than someone who's just doing it for a paycheck and could care less about expanding their own knowledge.
To go one step forward, you can ask them to go into detail about their side project, interesting problems they faced, how they overcame them, etc. Even introverts who are generally worse at small talk are on a much more balanced playing field when talking about something they're passionate about.
And then imagine where you will be in 5 more years.
If it can almost get a complex problem right now, I'm dead sure it will get it correct within 5 years