4 ms·

I agree, its utter nonsense for the most part, it seems some companies just want you to jump through a bunch of hoops and to make you feel stupid. I think havin

• buss 15y ago
  That would probably be more useful, but it doesn't scale. An interview like that takes up a ton of resources and can leave a bad impression on a candidate. Not only are you paying for devs to help and evaluate the candidate, you are doing this over a much longer period than a traditional interview, and you have to pay the candidate for the work they did, even if you're going to throw it out. Nobody wants to force candidates to jump through hoops or make them feel stupid. That's a recipe for bad word-of-mouth and never hiring good devs. When I conduct interviews, I always try to make people feel like they did an OK job. I don't want them to get off the phone thinking they did really poorly. I try hard to seem impartial, but that's often quite difficult to do. The root problem is that nobody knows what the hell they're doing in interviews. We don't know the best way to evaluate candidates, so we try various things that are ineffective or wasteful. Eventually we'll figure it out.
  • devs1010 15y ago
    if its for web dev, make them do something that has a web UI, give specific contraints and then write an automated integration test for it (such as using selenium), run this on the incoming submissions, only review the ones that pass, this is just a quick idea... there are ways to automate this....