Hacker News new | past | comments | ask | show | jobs | submit login

So in the realm of infinite knowledge and experience candidates may have, the signal you want is based purely on the specific contrived questions of your choice.

You should be aware this is not unbiased, it's just biased towards those who happen to have worked on similar problems to what you think is important.

Google can probably get away with this due to the size of applicant pool, but when I see other companies cargo-culting this approach I can't help but see a huge talent arbitrage opportunity.




It's biased toward people who have taken a few weeks to prep on the standard Google interview curriculum that has been widely advertised for a decade.


It's hiring committee's job to read the resume, not the interviewer's.


What is the interviewer's job?


The interviewer's job should be to determine whether, and how, the candidate would succeed in the organization.


No, that's the job of whoever is making the hiring decision. The interviewer is providing signal for that person / people.


in my opinion that disenfranchises the rank and file who should, and usually do, have as much interest and voice in the organization's future as the hiring managers


Ask a technical question or two and assess the candidate based on their reply.


How can you assess this when divorced from the resume, or is this technical Q&A purely "people skills" and how is that possible?




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

Search: