> Not a single interviewee has even had a good guess in 2 years of open job recs.
Unless a good explanation is an insta-offer, why do you still ask a question you've gotten zero signal from?
Unless a good explanation is an insta-offer, why do you still ask a question you've gotten zero signal from?
Interview questions aren’t just for comparing candidates with each other. It’s also useful to know how a candidate’s knowledge compares to the knowledge of the team. The best of a bad bunch might still be unhirable. It’s often better to leave a role vacant than fill it with someone mediocre.
If the GP can’t find anyone in the hiring pool who knows C++ well, that’s a valuable insight. Maybe they need to expect less C++ from candidates and plan for more on the job training.
Or change languages.
How someone handles that inevitable "I don't know" moment is an important data point.