Earlier quoted context omitted.
> If you can build me a tool ... I'd like to start a company with you and we can make a lot of money together. If you can't tell how good a programmer is by his resume, then....why the hell does everybody use resumes to try to do it??? The kicker is you can't sort good programmers from bad programmers by keyword filtering. Asking for specific languages, or specific frameworks, is a particularly egregious sin. If one…
> If you can't tell how good a programmer is by his resume, then....why the does everybody use resumes to try to do it??? I'm wondering at this point if you've ever hired for an engineering position before... Lots of assumptions here, but we don't use keyword filtering. > you'll filter out all geniuses who decided that 4 years at Amazon is enough for anybody and wants to make a move. Geniuses with 4 years of experien…
Well, I'm not a mindreader, so perhaps you are right. Can you at least help me clear up the bad assumptions, and tell me, if resume's are not giving you the information you need, why are you using resumes?
> we don't use keyword filtering.
If your policy is to reject anybody without nodejs experience, you are using keyword filtering. It is what it is man.
> filter out more good ones.
I have sympathy here; its not clear exactly how to improve the filter, but if you reviewed 1,000 applications and found nobody, its impossible to filter out more good ones :-) There's no change you could make which would filter out more good people.
> You have to prioritize time
I have sympathy here too :-( Honestly, I can give you guesses as to how to improve, but I have no clue. Its one of the reasons I didn't go into management: I didn't see any way of doing it any better than it was already being done. You wonder if I've ever hired for an engineering position: no, I haven't, because I didn't think I'd be able to do a good job of it.
But one thing I do know, is that if a system isn't working, it needs to change, whether you know exactly how it should be changed or not.