Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There are two things driving policies like this.

First, personal interviews can be poor predictors of future hire performance. People will often hire someone who resonates on a personal level, or who is otherwise charismatic, rather than for the right skillset. Standardized tests, administered correctly, are one way of reducing the variability.

And variability is pain. Your HR and hiring people are likely being judged just the way everyone else is. Hiring, or forcing dev teams to interview, a lot of low-quality candidates without an effective screen is a good way to find yourself being replaced.

The second is that, as people are fond of saying, the standard you walk past is the standard you accept. This is the source of a lot of foolish "musts"––candidates must have a certain GPA, or only go to a certain school, or they have to hit a certain percentage on some tests. Having standards is all well and good until you find a case that doesn't fit your profile and you either get flexible or look foolish.

Being flexible means that other hires complain that you're lowering your standards, and no one likes hearing that either.

The test in this case wasn't correctly administered, as columbo pointed out elsewhere, and I agree that hiring managers shouldn't have a veto over technical hires. But this is the sort of human-dynamics problem that can't be solved by firing entire departments. If you don't address the problem head-on it'll just come back next year in a different form.



Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: