This is in fact one of my two requirements when interviewing: I want to hear the candidate say "I don't know" to a question. The other is that I want to hear them talk passionately about some project they once did. Bullshitting is an immediate fail.

Same. When I'm on a panel interviewing developers (as a developer myself), I don't actually care if you meet the specific listed qualifications directly, I want you to answer in ways that demonstrate how you think to prove to me that you can solve the problems the role needs. I don't want someone who can memorize a study guide, I want someone who can problem solve and think critically.

Each time I've gotten my way it turned out to be a great decision. When I've acquiesce to "but they knew all my java trivia questions" it's been a bad choice.

You sound incisive :)

It's hard in the moment, but we'd do well to appreciate that not passing a myopic screen is likely a blessing.

ho boy, I wish I were interviewed by more people like you. I never know what the hell is going on and it's almost impossible to get me to shut up about my stupid projects.