We did look very unfavorably at candidates who had an unrealistically high opinion of themselves. But we didn't ask dick C++ questions. Like list all 200 ways

We did look very unfavorably at candidates who had an unrealistically high opinion of themselves. But we didn't ask dick C++ questions. Like list all 200 ways you can initialize a variable in C++. And, once somebody has told you they are 4/10 in C++, you can't ding them if they don't know your favorite C++ feature, or if they haven't memorized the next version of the standard. IMHO, interview questions should not be about what the candidate knows. At all. When I went to Intel, I knew nothing about chip design or EDA software. Which was OK, because chip design methodologies were all obsoleted by Moores law, and the techniques needed to fix it hadn't even been invented yet. What is important is what you can learn and how fast can you learn it.