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

> 2 - Can you really ferret out cheating? I had a grad school classmate who paid someone to do his (non-programming) take-home homework for a job interview, and he got the job. He only lasted 6 or 7 months, but it was enough to be awful for all parties involved. I don't have a great counter-solution other than ask for someone to come in to the office to do the work, and even then you can't tell if they have remote support.

Personally, I think this is where the skill of the interviewer comes in. A skilled interviewer can bust through bullshit fairly quickly. A big problem in interviewing and hiring right now is that most of the interviewers are not skilled. Thus, companies try to come up with processes and metrics that (theoretically) remove the interviewer skill from the equation. Unfortunately, this seems to be done in a horribly unscientific manner.



If only we had some sort of take-home exercise for interviewers.


I hear you on unskilled interviews.

I guess the challenge in this situation is that the whole reason for take-home work is that introverted interviewees get flustered in person. Won't this happen when the review happens?

This still seems like a better idea than "Tell me about yourself" and "How many golf balls fit in a 747?"


"Won't this happen when the review happens?"

At that point, the candidate should not be hired.

If the candidate can't communicate while writing code, and can't communicate about code already written, at some point you have to be afraid the candidate just can't communicate.

If this is a person who can communicate in any situation except an interview situation, then it's a Catch 22 where their ability to communicate in a work environment just can't be verified.

(Unless you secretly record them communicating in some other work context? Probably not a scalable approach.)




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

Search: