2 ms·
I have seen this used two ways: 1) As a recruiter-level screening question. A recruiter can't evaluate your answers to a coding problem, but they can reject al
by doe_eyes 2y ago
I have seen this used two ways:
1) As a recruiter-level screening question. A recruiter can't evaluate your answers to a coding problem, but they can reject all candidates who select less than "7" on a slider. It's basically a cheap way to go from 1,000 resumes to a more manageable number that's actually shown to the hiring manager.
2) As a "gotcha" on technical interviews: oh, you selected "9" on C++? Well, here's my favorite IOCCC entry, figure it out! You can't? "No hire, the candidate lied." It's counterproductive, but many engineering organizations approach interviewing this way (also see: "brain teaser" questions).
Between #1 and #2, the safest answer is always "8".