[josephschmoe]

Iambob doesn't account for the fact that interviewing candidates falls into a Simpson's Paradox for this instance.

You have two cohorts which comprise a majority of your applicants:

1. Unemployed, X% qualified. Has time.

2. Employed, 100-X% qualified. Does not have time.

X is small. If both candidates are qualified, tests for X also find how qualified they are so they can be compared.

His methods are objectively better, provided that both candidates have the same amount of free time. If you compare two unemployed engineers, you'll pick the right one. If you compare two employed engineers, you'll pick the right one.

If you compare an unemployed engineer vs an employed one, however, you'll probably pick the unemployed engineer, even if the employed one is better. Because he doesn't have as much time for your homework or to maintain a Github profile.

Thus, if you're comparing 30 engineers, half of whom are employed, you'll pick the most qualified unemployed candidate, rather than the objectively most qualified candidate.

That's why, even if the test is slightly worse, with an interview room only test you'll consistently pick the better candidate: a large, large segment of talented candidates are employed.

I would love a statistical analysis of Simpson's Paradox and technical interview methods if anyone's ever done one.

[GregorStocks]

If you're employed, it's generally a lot easier to find the time to do a coding problem at home than it is to actually physically come in during a weekday and talk to people.

[loumf]

Take a sick day -- have a "doctor's appt". It's really not that big a deal. "Hey, I have to come right from work, do you mind if I don't wear a suit so I don't have to go home and change" -- it's a well-understood problem.

[nilkn]

Surely, though, it's easier to just do a coding problem in the evening? No worries about coming up with a lie for your employer, no possibility of suspicion, and some people have to take sick days out of their vacation time sadly.

[loumf]

Some people are tired and not at their best after a full day of coding.

I talk to the applicant and try to work something out. I interview weekends and evenings if that's what they want. First interviews are always on the phone. Eventually, they have to come in, but by then, we are pretty sure it isn't a waste of time.

[danielweber]

Some people are tired and not at their best after a full day of coding.

Especially if their day job sucks, which is one reason people look for new jobs.

Not too long ago I was at a job where management demanded 11½ days. Guess how well the team members could handle an interview at 8pm.

[Crito]

I can't code shit in the evening after work. Some times I take vacation days, intending on doing nothing other than working on personal projects during daylight hours.

[mempko]

This here is the best response people. PEOPLE!