News for hackers. Stuff that matters.

A comment on Google: 90% of our engineers use the software you wrote (Homebrew), but.... Parent comment

Re:Google: 90% of our engineers use the software you wrote (... by rbanffy on Thursday June 11, 2015 @07:55AM (#9699060)
Running, then cleaning and then having a dataset that still needs interpretation.

I'd take the 30 minute interview route and risk not hiring a clever programmer.

[ Parent | on HN ]
Re:Google: 90% of our engineers use the software you wrote (... by iopq on Friday June 12, 2015 @10:12AM (#9705964)
Aren't we trying to hire clever programmers? Isn't that the point?

If a guy has some kind of a git-mutating program that makes it seem like he writes good stuff, he's probably a good programmer to be able to write such a thing.

[ Parent | on HN ]
Re:Google: 90% of our engineers use the software you wrote (... by JoeAltmaier on Friday June 12, 2015 @10:13AM (#9705967)
...or knows how to download such a thing and run it.
[ Parent | on HN ]
Re:Google: 90% of our engineers use the software you wrote (... by iopq on Friday June 12, 2015 @10:32AM (#9706091)
Such a thing doesn't exist, but besides, why not spend 30 minutes asking about what challenges they dealt with at their job instead?

If they can't talk about what problems they solved, they probably didn't solve any.

[ Parent | on HN ]
Re:Google: 90% of our engineers use the software you wrote (... by JoeAltmaier on Friday June 12, 2015 @11:12AM (#9706362)
I guess everything I do is 'solving problems'. That's pretty open-ended. Maybe 'describe a situation where things didn't work the way they were supposed to/documented to work. How did you resolve it?' or something like that.
[ Parent | on HN ]
Re:Google: 90% of our engineers use the software you wrote (... by iopq on Friday June 12, 2015 @01:06PM (#9707171)
That's what I meant by problems, things like when everything went wrong and you had to fix it.
[ Parent | on HN ]