Re:Never fail a technical interview again
by dahart on Monday December 09, 2024 @11:17AM
(#42367568)
If the problem is having to wait for applicants, then you’re right; stopping early will help. In my experience, companies already do what you’re suggesting simply by having a deadline or time window for filling a job. Even if a lot of companies would love it, most job posts don’t get over three thousand applicants per seat available.
In this particular case, MS didn’t have to wait for people to show up, they got 100k candidates before they could have even made a decision on a small subset. And in general, the problem being discussed in this thread isn’t having to wait, it’s how to deal the flood of applications coming in too fast.
The sieve approach does solve the same problems you’re talking about, while not adding noise or being arbitrary or capricious with candidates by having to reject them randomly. The sieve saves effort and time spent evaluating candidates. Don’t forget the idea is that the top of the funnel is criteria that are both low bar and much faster and easier than an interview. In the case of 100k applicants, the top of the funnel should probably be automated and measure things that are as easy to measure and objective as possible like school grades, amount of work experience, maybe test scores, etc. To whatever degree possible, with 100k candidates, you can probably automate whether the application meets some minimum criteria and easily rule out most applications.
Only the bottom of the funnel takes time, and you only use the bottom of the funnel on maybe 2x or 3x the number of job seats you have available. This way you only spend the same amount of time evaluating candidates that you would have use any sampling method.
Regarding noise, the sieve is a better approach than early stopping because the criteria at each layer are not subject to or sensitive to the same amount of noise. Because the bar is a minimum criteria at the top of the funnel, noise in that selection process is far less likely to reject top candidates.
BTW, the Secretary Problem’s 37% rule is only applicable to picking 1 single candidate, so you need some kind of modified algorithm to pick the best 30. Also that solution implies you have to fully evaluate each candidate before evaluating the next candidate. This is potentially much costlier than using the sieve approach, because you have to interview all the candidates that you reject. The benefit of the sieve is based on the observation that we can use extremely easy to measure minimum criteria to partial evaluate candidates for the purpose of culling.
In this particular case, MS didn’t have to wait for people to show up, they got 100k candidates before they could have even made a decision on a small subset. And in general, the problem being discussed in this thread isn’t having to wait, it’s how to deal the flood of applications coming in too fast.
The sieve approach does solve the same problems you’re talking about, while not adding noise or being arbitrary or capricious with candidates by having to reject them randomly. The sieve saves effort and time spent evaluating candidates. Don’t forget the idea is that the top of the funnel is criteria that are both low bar and much faster and easier than an interview. In the case of 100k applicants, the top of the funnel should probably be automated and measure things that are as easy to measure and objective as possible like school grades, amount of work experience, maybe test scores, etc. To whatever degree possible, with 100k candidates, you can probably automate whether the application meets some minimum criteria and easily rule out most applications.
Only the bottom of the funnel takes time, and you only use the bottom of the funnel on maybe 2x or 3x the number of job seats you have available. This way you only spend the same amount of time evaluating candidates that you would have use any sampling method.
Regarding noise, the sieve is a better approach than early stopping because the criteria at each layer are not subject to or sensitive to the same amount of noise. Because the bar is a minimum criteria at the top of the funnel, noise in that selection process is far less likely to reject top candidates.
BTW, the Secretary Problem’s 37% rule is only applicable to picking 1 single candidate, so you need some kind of modified algorithm to pick the best 30. Also that solution implies you have to fully evaluate each candidate before evaluating the next candidate. This is potentially much costlier than using the sieve approach, because you have to interview all the candidates that you reject. The benefit of the sieve is based on the observation that we can use extremely easy to measure minimum criteria to partial evaluate candidates for the purpose of culling.