You’re the one who suggested the idea, that the question is a way to tell if a candidate is lying about their experience.
Many people lie about their experience. Usually it’s glaringly obvious.
my point is that assuming everyone is lying, biases you to the extent you want the outcome to be that the person is lying such that you can pat yourself on the back for a good job done rather than coming to the awkward conclusion you were wrong. and that is a real problem in interviewing because it means you discard top candidates.
lol
> if you worked on something for 10-15 years chances are you cannot answer some random specific question
Again, the "random specific question" we're discussing is "Tell me about a project you worked on." So, again, if you can't answer "Tell me about a project you worked on", if you're claiming to have worked on that project for 10-15 years...I suspect there's something larger at play than just an inability to communicate about one's experience.
> so that does not mean you are lying about having built the thing.
I can and do routinely answer these types of questions about my work without issue. So nope.
> my point is that assuming everyone is lying,
Is verifying that someone isn't lying the same as assuming they are? (Hint: no).
> and that is a real problem in interviewing because it means you discard top candidates.
I would guess fewer than .1% of "top candidates" fail interviews at the "Tell me about a project you worked on" stage.
"why did you choose to order the members of this struct in your C code the way you did" is one.
