5 ms·

I would say that interviewing for engineering knowledge (coding, algorithms, software engineering) is pretty straight forward, but interviewing to figure out if

by cdibona 16y ago

I would say that interviewing for engineering knowledge (coding, algorithms, software engineering) is pretty straight forward, but interviewing to figure out if a candiate can get 'real' work done is very difficult. I don't know of any magic way of testing for that. There are some good signals, of course, such as: 1) pre-interview open source reputation and release. 2) References from people you trust and respect. 3) Publications with significant content written by the candidate. But I've seen each of these fail, even in combination, in predicting the ability to execute. That said, it's better than nothing. (disclaimer, I work for Google, and am also waiting for the part about Google in the OP)

kls 16y ago
It is actually pretty easy, you look for developers that understand minimum viable product and can explain their development methodology to produce software in such a manner.
rjett 16y ago
There is a way to test to see if someone can get stuff done, but that usually entails hiring someone for a predetermined time (6 mos, a year, 2 years) and then evaluating whether they meet your standards at the end of that time period. If they do, they stay on. If someone really wants to work for your organization, I can guarantee that they'll do everything in their power to get stuff done during this time period.
- cdibona 16y ago
  Oh, sure, but some of the best people won't work on a contract basis.
  - rjett 16y ago
    Yes, I totally agree, but I was assuming we were talking about evaluating people who were for the most part unproven in the work world. Many investment banks and consulting firms hire fresh undergrads on contract.
writetoalok 16y ago
>and am also waiting for the part about Google in the OP) One good reason not to work for already big companies like Google and Microsoft, is that your growth potential is limited. Case in point, video.google.com and www.youtubue.com. Nobody needs to wonder about which of the two developers among these projects struck it rich. Why shovel for someone else's palace when you can build your own?

by cdibona 16y ago

kls 16y ago

It is actually pretty easy, you look for developers that understand minimum viable product and can explain their development methodology to produce software in such a manner.

rjett 16y ago

There is a way to test to see if someone can get stuff done, but that usually entails hiring someone for a predetermined time (6 mos, a year, 2 years) and then evaluating whether they meet your standards at the end of that time period. If they do, they stay on. If someone really wants to work for your organization, I can guarantee that they'll do everything in their power to get stuff done during this time period.

cdibona 16y ago
Oh, sure, but some of the best people won't work on a contract basis.
- rjett 16y ago
  Yes, I totally agree, but I was assuming we were talking about evaluating people who were for the most part unproven in the work world. Many investment banks and consulting firms hire fresh undergrads on contract.

writetoalok 16y ago

>and am also waiting for the part about Google in the OP) One good reason not to work for already big companies like Google and Microsoft, is that your growth potential is limited. Case in point, video.google.com and www.youtubue.com. Nobody needs to wonder about which of the two developers among these projects struck it rich. Why shovel for someone else's palace when you can build your own?