News for hackers. Stuff that matters.
Re:How Google Hires by bengali3 on Tuesday April 07, 2015 @10:33PM (#9338499)
actually, that brings up a really great point. This could be an interesting article. Considering how much the web focuses on 'conversion of web leads' and making the entire process seamless, you'd think you could quantify the candidates lost (and put a dollar figure on it) simply because the interface wasn't friendly and turned away candidates. However, all too often i feel that the goal for everyone involved but the hiring manager, is a seat filled.

Anecdotally, I was prompted 'Zip code required' on a multinational company talent portal. Tried to fix and submit for at least 60 seconds before finally had to modify the CSS to show the input so I could put in a value, as Zip input was set to display:none. I figured at least there would be less competition for the role.

Re:How Google Hires by dennisgorelik on Wednesday April 08, 2015 @04:30AM (#9339352)
It's possible that your application was the only one... in months... so nobody was even looking at these applications.

You did not get reply in the end, right?

Re:How Google Hires by bengali3 on Wednesday April 08, 2015 @12:11PM (#9341798)
not a peep :)
Re:How Google Hires by grrowl on Wednesday April 08, 2015 @03:33AM (#9339209)
That's a killer idea for a front-end developer test.
Re:How Google Hires by dennisgorelik on Wednesday April 08, 2015 @03:14PM (#9343125)
Front-end developer may not want to work in the place that makes such silly mistakes.
Re:How Google Hires by QuercusMax on Wednesday April 08, 2015 @07:21PM (#9344823)
If you deliberately made it that way and told your candidates, it might work well. If you're a web dev and can't figure out how to un-hide a field, then you don't deserve an interview.
Re:How Google Hires by grrowl on Wednesday April 08, 2015 @07:46PM (#9344935)
Definitely intentionally, more of a gauge of problem solving ability. Fix the bugs, submit the test, get interview.