3 ms·
The interview questions don't sound particularly rigorous, but asking someone to pick a programming language and do something simple with it sounds like a good
by troupe 9y ago
The interview questions don't sound particularly rigorous, but asking someone to pick a programming language and do something simple with it sounds like a good way to make sure that they at least have actually done programmed before. If the job involved any type of programming, this would seem to strongly correlate with success. What do you think would be better?
- WhitneyLand 9y agoIt sounds like a good way? Yes, I agree intuitively it sounds reasonable, but that alone is not considered a best practice. Why do we all work so hard to go by good data in our real work, but when it comes to interviewing someone we’re encouraged to just wing it, or use our best judgement? Careers can be affected with this stuff, and bad hiring decisions in either direction can hurt an organization. There is research done on hiring but the learnings are slow to benefit the practice. General intelligence is one of the strongest indicators, but not gotcha trick puzzle questions. Work samples are predictive, but again, approach is everything. Track record of past success (when that applies) is important. This is not my field so I struggle like everyone else to keep up with what’s right. It just burns me that such litttle rigor is typically applied to something so important. Maybe it’s because interviewing is just one of those topics that seem easy, like, nutrition - most people think they know a lot more about it than they really do.